Invalid GELF header in message: Could not extract sequence count

Question

Invalid GELF header in message: Could not extract sequence count

chrisferry opened this issue 13 years ago · comments

Sending multiline java stacktraces to graylog server from logstash causes this error.
Gems:
addressable (2.2.5)
amqp (0.6.7)
async_sinatra (0.5.0)
backports (2.1.0)
bson (1.3.0)
daemons (1.1.2)
em-websocket (0.2.1)
escape_utils (0.2.3)
eventmachine (0.12.10)
eventmachine-tail (0.6.1)
ffi (1.0.7, 0.6.3)
gelf (1.1.3)
haml (3.0.25)
jls-grok (0.4.6)
json (1.5.1)
logstash (0.2.20110405105154)
minstrel (0.2.20110428124038)
mongo (1.3.0)
msgpack (0.4.4)
rack (1.1.0)
rack-test (0.4.0)
rake (0.8.7)
rbtrace (0.3.13)
sinatra (1.0)
stomp (1.1.8)
thin (1.2.11)
trollop (1.16.2)
uuidtools (2.1.2)

Also see this error after the sequence count:
Exception caught while handling GELF message: For input string: "-101-22"

What additional information can I provide?

Alexey Palazhchenko · Answer 1 · Fri Apr 29 2011 23:59:18 GMT+0800 (China Standard Time)

Thanks for the report, but it's probably a bug in server, not in this gem. Please contact us in mail list: http://groups.google.com/group/graylog2?hl=en

Chris Ferry · Answer 2 · Sat Apr 30 2011 00:03:44 GMT+0800 (China Standard Time)

I mentioned it in the graylog2 IRC room and _lennart says it was a gelf-rb issue.
I'll post this to the graylog2 group.

Thanks

Chris

On Apr 29, 2011, at 11:59 AM, AlekSi wrote:

Thanks for the report, but it's probably a bug in server, not in this gem. Please contact us in mail list: http://groups.google.com/group/graylog2?hl=en

Reply to this email directly or view it on GitHub:
#6 (comment)

Alexey Palazhchenko · Answer 3 · Sat Apr 30 2011 00:08:29 GMT+0800 (China Standard Time)

Chris, please mention your original java stacktraces in mail. Thank you.

Lennart Koopmann · Answer 4 · Sat Apr 30 2011 02:02:01 GMT+0800 (China Standard Time)

There is a specification problem for GELF. The gelf-rb gem is setting different header sizes than the server expects. I'll think about the best solution and update the ticket. This will most likely result in a patched graylog2-server release.

Chris Ferry · Answer 5 · Fri May 13 2011 05:43:58 GMT+0800 (China Standard Time)

Here's the stack trace: http://pastie.org/1894746
If there's a patch I can apply please let me know. Would love to get this work ASAP.

Lennart Koopmann · Answer 6 · Fri May 13 2011 05:54:18 GMT+0800 (China Standard Time)

Thanks! I am planning a patchlevel release for the next days that will include a fix for this.

Moved this bug report to JIRA:http://jira.graylog2.org/browse/SERVER-25

(This issue tracker will be closed soon)