I have logstash installed as a service on a machine with Logstash+Kibana+Elastic.
My logstash was updated, so its seems that doesn't shutdown properly and now show an error with a pipeline:
Jan 26 10:19:56 esearch logstash[29197]: [2024-01-26T10:19:56,748][INFO ][logstash.outputs.elasticsearch][pipeline][dec4e13358daa92f56dcbdf7685e6d1c745c7be9f58d718cb6dda6176d841907] Aborting the batch due to shutdown request while waiting for connections to become live
Jan 26 10:19:56 esearch logstash[29197]: [2024-01-26T10:19:56,758][INFO ][org.logstash.execution.WorkerLoop][pipeline] Received signal to abort processing current batch. Terminating pipeline worker [pipeline]>worker5
I only want that pipeline start and ingest data. How can I solve it?
I'm suggest to check ES, reason: [logstash.outputs.elasticsearch][pipeline][dec4e13358daa92f56dcbdf7685e6d1c745c7be9f58d718cb6dda6176d841907] Aborting the batch due to shutdown request while waiting for connections to become live
If he had restarted LS, should be normally terminated. However it's good to check what Ritikapawar suggested.
systemctl stop logstash
ps aux | grep logstash
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.