Zabbix plugin crash

Description

This has occurred three times during the past several days.

It appears to be related to the Zabbix plugin, but I could be totally wrong.

Failed to flush outgoing items {:outgoing_count=>69, :exception=>#<NoMethodError: undefined method `tv_sec' for #<Array:0x102ef0fb>>, :backtrace=>["file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logsta
sh/event.rb:238:in `sprintf'", "org/jruby/RubyString.java:3065:in `gsub'", "file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/event.rb:224:in `sprintf'", "/home/lsapp/logstash/build/ruby/logstash
/outputs/elasticsearch_http.rb:76:in `flush'", "org/jruby/RubyArray.java:2408:in `collect'", "/home/lsapp/logstash/build/ruby/logstash/outputs/elasticsearch_http.rb:75:in `flush'", "file:/home/lsapp/
logstash-1.3.2-flatjar.jar!/stud/buffer.rb:219:in `buffer_flush'", "org/jruby/RubyHash.java:1338:in `each'", "file:/home/lsapp/logstash-1.3.2-flatjar.jar!/stud/buffer.rb:216:in `buffer_flush'", "file
:/home/lsapp/logstash-1.3.2-flatjar.jar!/stud/buffer.rb:193:in `buffer_flush'", "file:/home/lsapp/logstash-1.3.2-flatjar.jar!/stud/buffer.rb:112:in `buffer_initialize'", "org/jruby/RubyKernel.java:15
19:in `loop'", "file:/home/lsapp/logstash-1.3.2-flatjar.jar!/stud/buffer.rb:110:in `buffer_initialize'"], :level=>:warn, :file=>"/home/lsapp/logstash-1.3.2-flatjar.jar!/stud/buffer.rb", :line=>"231"}
Exception in thread "LogStash::Runner" org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `gsub' for #<Array:0x529c4004>
at LogStash::Outputs::Zabbix.receive(/home/lsapp/logstash/build/ruby/logstash/outputs/zabbix.rb:91)
at LogStash::Outputs::Base.handle(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/outputs/base.rb:86)
at RUBY.initialize((eval):219)
at org.jruby.RubyProc.call(org/jruby/RubyProc.java:271)
at LogStash:ipeline.output(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/pipeline.rb:259)
at RUBY.outputworker(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/pipeline.rb:218)
at RUBY.start_outputs(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/pipeline.rb:145)

Activity

Show:
Zachary Buckholz
July 21, 2014, 10:08 PM

It ran pretty well for several days, but just recently crashed.

Not sure what to make of this

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-219"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-279"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-318"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-342"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-426"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-489"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-783"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-828"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-873"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-909"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-936"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-963"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-978"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-996"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1113"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1116"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1125"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1227"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1293"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1344"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1347"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1389"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1395"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1542"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1635"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1668"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1680"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1683"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1686"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1695"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1698"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1713"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1773"

Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thread "Thread-1788"
Grok regexp threw exception {:exception=>"undefined method `match' for false:FalseClass", :level=>:warn}
Grok regexp threw exception {:exception=>"wrong number of arguments calling `match` (1 for 0)", :level=>:warn}
Grok regexp threw exception {:exception=>"undefined method `match' for false:FalseClass", :level=>:warn}
Grok regexp threw exception {:exception=>"undefined method `match' for false:FalseClass", :level=>:warn}
Grok regexp threw exception {:exception=>"undefined method `match' for false:FalseClass", :level=>:warn}
Exception in thread "LogStash::Runner" org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `gsub' for #<Array:0x4964e09f>
at LogStash::Outputs::Zabbix.receive(/home/lsapp/logstash/build/ruby/logstash/outputs/zabbix.rb:91)
at LogStash::Outputs::Base.handle(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/outputs/base.rb:86)
at RUBY.initialize((eval):219)
at org.jruby.RubyProc.call(org/jruby/RubyProc.java:271)
at LogStash:ipeline.output(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/pipeline.rb:259)
at RUBY.outputworker(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/pipeline.rb:218)
at RUBY.start_outputs(file:/home/lsapp/logstash-1.3.2-flatjar.jar!/logstash/pipeline.rb:145)

Philippe Weber
March 16, 2015, 5:44 AM

There is two bug report in this issue

1. tv_sec was due to @timestamp becoming an array, mostly due to multiline filter, this is fixed
2. gsub error was in zabbix output, but the current version of the plugin has evolved a lot, so this issue will not occur anymore https://github.com/logstash-plugins/logstash-output-zabbix/

Assignee

Logstash Developers

Reporter

Zachary Buckholz

Labels

None

Fix versions

Affects versions

Configure