"Unable to process message" warnings after upgrading to 3.2

Graylog Central (peer support)
1

I upgraded from 3.1.4-1 on Debian systems. Immediately after I restarted the service I started seeing messages like:
2020-02-03T21:05:21.257Z WARN [ProcessBufferProcessor] Unable to process message <e381a771-46c8-11ea-aa42-52540038ef24>: java.lang.ClassCastException: Cannot cast java.lang.String to org.joda.time.DateTime
I also noticed that the in/out counter in the web ui went from being basically balanced to showing way more inbound messages. I saw another message theorizing it’s a problem with JSON extraction, but I continued to see these messages after I deleted my JSON extractor. I don’t have time to remove each of my other 22 extractors one by one to see if one may be the exact source of this issue.

Any other ways I could debug this situation?

2

Hi @reshippie,

sorry for the inconvenience. A bug has made it to the release and an issue was created for that: https://github.com/Graylog2/graylog2-server/issues/7364

The issue includes a possible workaround.

A bug fix release should be coming soon.

Thanks for your input!

Best regards,
Konrad

3

I installed 3.2.1 and that resolved things. Thanks for the help.

1 Like
4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.