Gracefully stopping the logstash


(MJay) #1

When I do the CTRL+C I do the following message and logstash is not exiting. I have stopped the filebeat as well which send the data to the logstash pipeline.

D:\elastic-5.4.3\logstash-5.4.3\bin>[2017-08-03T12:44:57,316][WARN ][logstash.runner ] SIGINT received. Shutting down the agent.
[2017-08-03T12:44:59,382][WARN ][logstash.agent ] stopping pipeline {:id=>".monitoring-logstash"}
[2017-08-03T12:45:02,459][WARN ][logstash.agent ] stopping pipeline {:id=>"main"}
[2017-08-03T12:45:03,663][WARN ][logstash.runner ] Received shutdown signal, but pipeline is still waiting for in-flight events
to be processed. Sending another ^C will force quit Logstash, but this may cause
data loss.
[2017-08-03T12:45:07,629][WARN ][logstash.shutdownwatcher ] {"inflight_count"=>0, "stalling_thread_info"=>{"other"=>[{"thread_id"=>117, "name"=>"[main]<beats", "current_call"=>"[...]/vendor/bundle/jruby/1.9/gems/logstash-input-beats-3.1.18-java/lib/logstash/inputs/beats.rb:206:in run'"}, {"thread_id"=>115, "name"=>"[main]>worker2", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:136:insynchronize'"}], ["LogStash::Filters::GeoIP", {"source"=>"clientip", "id"=>"56670bb9e4242cfb321ed6a2c926f7107e9a754b-3"}]=>[{"thread_id"=>113, "name"=>"[main]>worker0", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:136:in synchronize'"}, {"thread_id"=>114, "name"=>"[main]>worker1", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:118:insynchronize'"}, {"thread_id"=>116, "name"=>"[main]>worker3", "current_call"=>"[...]/logstash-core/lib/logstash/util/wrapped_synchronous_queue.rb:136:in `synchronize'"}]}}
[2017-08-03T12:45:07,668][ERROR][logstash.shutdownwatcher ] The shutdown process appears to be stalled due to busy or blocked plugins. Check the logs for more information.


(MJay) #2

I can see the same statements in the logstash-plain.log as well.


(system) #3

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