Logstash go down


(piter) #1

I have a file periodically updated but when logstash reach the end of file it stops. How can I maintain the process active?

this is the logstash-plain.log file:

[2018-05-13T06:00:11,220][WARN ][logstash.outputs.tcp ] tcp output exception {:host=>"listener.logz.io", :port=>5050, :exception=>#<EOFError: End of file re ached>, :backtrace=>["org/jruby/RubyIO.java:2965:in sysread", "/usr/share/logs tash/vendor/bundle/jruby/2.3.0/gems/logstash-output-tcp-5.0.3/lib/logstash/outpu ts/tcp.rb:156:in block in register", "/usr/share/logstash/vendor/bundle/jruby/ 2.3.0/gems/logstash-codec-json_lines-3.0.6/lib/logstash/codecs/json_lines.rb:48: in encode", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-outpu t-tcp-5.0.3/lib/logstash/outputs/tcp.rb:201:in receive", "/usr/share/logstash/ logstash-core/lib/logstash/outputs/base.rb:92:in block in multi_receive", "org /jruby/RubyArray.java:1734:in each", "/usr/share/logstash/logstash-core/lib/lo gstash/outputs/base.rb:92:in multi_receive", "/usr/share/logstash/logstash-cor e/lib/logstash/output_delegator_strategies/single.rb:15:in block in multi_recei ve", "org/jruby/ext/thread/Mutex.java:148:in synchronize", "/usr/share/logsta sh/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in multi _receive", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator.rb: 49:in multi_receive", "/usr/share/logstash/logstash-core/lib/logstash/pipeline .rb:477:in block in output_batch", "org/jruby/RubyHash.java:1343:in each", " /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:476:in output_batch ", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:428:in worker_lo op", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:386:in block in start_workers"]}


#2

I think this means whatever is at the receiving end of the tcp output has closed the connection. logstash cannot control that.


(piter) #3

Ok. But logstash process should stay in standby until my input file has updated or not?


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.