Lumberjack terminating kills LogStash
Description
Gliffy Diagrams
Activity
Show:
Jordan Sissel December 28, 2012 at 7:25 AM
confirmed in 1.1.5, cannot reproduce in master. Assuming fixed (There was a bunch of improvements recently)
I'm betting lumberjack commit 1fae69cf6bc657612df267e6b358d0d1552b9089 fixed this.
Fixed
Details
Details
Assignee
Reporter

Labels
Fix versions
Affects versions
Created December 24, 2012 at 5:36 AM
Updated April 19, 2013 at 8:19 PM
Resolved December 28, 2012 at 7:25 AM
When I terminate lumberjack on a remote machine it kills my LogStash agent process on the other end:
IOError: Connection reset by peer
sysread at org/jruby/ext/openssl/SSLSocket.java:583
fill_rbuff at jar:file:/opt/logstash/logstash.jar!/META-INF/jruby.home/lib/ruby/1.9/openssl/buffering.rb:53
read at jar:file:/opt/logstash/logstash.jar!/META-INF/jruby.home/lib/ruby/1.9/openssl/buffering.rb:94
read at jar:file:/opt/logstash/logstash.jar!/gems/jls-lumberjack-0.0.4/lib/lumberjack/server.rb:127
each_event at jar:file:/opt/logstash/logstash.jar!/gems/jls-lumberjack-0.0.4/lib/lumberjack/server.rb:72
run at jar:file:/opt/logstash/logstash.jar!/gems/jls-lumberjack-0.0.4/lib/lumberjack/server.rb:64
run at jar:file:/opt/logstash/logstash.jar!/gems/jls-lumberjack-0.0.4/lib/lumberjack/server.rb:49