You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My logstash.log is full of error lines like below:
{:timestamp=>"2015-05-22T09:09:28.649000-0500", :message=>"Gelfd failed to parse a message skipping", :exception=>#<Gelfd::UnknownHeaderError: Could not find parser for header: [100, 101]>, :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/gelfd-0.2.0/lib/gelfd/parser.rb:14:in parse'", "/opt/logstash/lib/logstash/inputs/gelf.rb:83:inudp_listener'", "/opt/logstash/lib/logstash/inputs/gelf.rb:60:in run'", "/opt/logstash/lib/logstash/pipeline.rb:163:ininputworker'", "/opt/logstash/lib/logstash/pipeline.rb:157:in `start_input'"], :level=>:warn}
How am I supposed to find out what message is causing this error message (logstash is receiving thousands of messages every second from thousads of different hosts so manual check is not an option).
It would be great if you include the failed message in the log. Also, can you think of an another way to catch the message?
The text was updated successfully, but these errors were encountered:
Hello,
My logstash.log is full of error lines like below:
{:timestamp=>"2015-05-22T09:09:28.649000-0500", :message=>"Gelfd failed to parse a message skipping", :exception=>#<Gelfd::UnknownHeaderError: Could not find parser for header: [100, 101]>, :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/gelfd-0.2.0/lib/gelfd/parser.rb:14:in
parse'", "/opt/logstash/lib/logstash/inputs/gelf.rb:83:in
udp_listener'", "/opt/logstash/lib/logstash/inputs/gelf.rb:60:inrun'", "/opt/logstash/lib/logstash/pipeline.rb:163:in
inputworker'", "/opt/logstash/lib/logstash/pipeline.rb:157:in `start_input'"], :level=>:warn}How am I supposed to find out what message is causing this error message (logstash is receiving thousands of messages every second from thousads of different hosts so manual check is not an option).
It would be great if you include the failed message in the log. Also, can you think of an another way to catch the message?
The text was updated successfully, but these errors were encountered: