Syslog UDP listener dies and won't restart
Description
Gliffy Diagrams
Activity
Show:
Jordan Sissel July 1, 2011 at 4:32 AM
I'm planning on having 1.0.13 released tonight;
I have one more feature i want to get into grok, but if I can't finish it soon I'll bump it to the next release.
Mach Technology July 1, 2011 at 4:17 AM
That's fantastic, thanks so much.
I'm really excited, when can I expect the new build? If it's still going to be a few days, do you have build instructions somewhere so I can build my own jar and give it a go?
Jordan Sissel July 1, 2011 at 3:08 AM
The specific bug was related to well-formed syslog messages coming in over UDP causing some URI parsing error (ruby sucks)
Jordan Sissel July 1, 2011 at 2:59 AM
Tentatively marking resolve as with new code on master what was previously failing is now working.
Logstash 1.0.13 is coming shortly with these and more fixes.
Mach Technology July 1, 2011 at 2:08 AM
Fantastic! Well done.
I have a bunch of boxes sending UDP syslog to the logstash instance and very shortly after starting logstash I start seeing this in the logs:
I, [2011-06-22T15:55:26.318000 #23300] INFO – file:/opt/logstash/logstash-1.0.12-monolithic.jar!/logstash/inputs/syslog.rb#71: Starting syslog udp listener on 0.0.0.0:514
W, [2011-06-22T15:55:26.320000 #23300] WARN – file:/opt/logstash/logstash-1.0.12-monolithic.jar!/logstash/inputs/syslog.rb#48: syslog udp listener died: Protocol not available - Protocol not available
W, [2011-06-22T15:55:26.320000 #23300] WARN – file:/opt/logstash/logstash-1.0.12-monolithic.jar!/logstash/inputs/syslog.rb#48: syslog udp listener died: Protocol not available - Protocol not available
D, [2011-06-22T15:55:26.367000 #23300] DEBUG – file:/opt/logstash/logstash-1.0.12-monolithic.jar!/logstash/inputs/syslog.rb#49: [
[0] "Backtrace",
[1] [
[0] "file:/opt/logstash/logstash-1.0.12-monolithic.jar!/logstash/inputs/syslog.rb:87:in `udp_listener'",
[1] "file:/opt/logstash/logstash-1.0.12-monolithic.jar!/logstash/inputs/syslog.rb:46:in `run'",
[2] "org/jruby/RubyProc.java:268:in `call'",
[3] "org/jruby/RubyProc.java:232:in `call'"
]
]
Even with -vvv and 'debug => true' on my syslog input I can't see where it dies - I'm probably missing an earlier exception. Any ideas how I can keep the UDP listener running for more than a few minutes?