I did some searching first, apologies if this has been already covered but I couldn't find it. Running Logstash v2.2.2, on Ubuntu 14.04.3 LT, m3.medium in EC2. When I try to stop or restart, I get:
Killing logstash (pid 23531) with SIGTERM
Waiting logstash (pid 23531) to die...
Waiting logstash (pid 23531) to die...
Waiting logstash (pid 23531) to die...
Waiting logstash (pid 23531) to die...
Waiting logstash (pid 23531) to die...
logstash stop failed; still running.
If it's a restart, I end up with two logstash processes running. Any ideas how to resolve this? Thanks!
They've added an option to allow Logstash to receive a SIGKILL if it reaches a timeout period. I think depending on the system you are using and how you install Logstash will determine how to add this option. I installed mine through an RPM in CentOS so the file I would edit is /etc/sysconfig/logstash. The very last line has a variable named KILL_ON_STOP_TIMEOUT. Setting that variable to 1 sets it so that Logstash will receive a SIGKILL after a timeout period. You might be able to edit the service file directly to add that value to the variable as well.
The only issue with this is that it can result in loss of data just be aware of that.
Hi, But is this something that logstash latest support is providing loss of data? I love logstash, But i am not java developer for logstash, LOGSTASH TEAM Could you please solve this issue ASAP? I am in big telecom company, and using it. Same once we start instance it does not stop, and we loss data. Also it is able start n number of instances even if configuration file does not exits, it starts instance. I am talking about logstash 5.2.1 , LATEST LOGSTASH VERSION. Please help us.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.