# Logstash Gone Wrong After force shutdown

**URL:** <https://discuss.elastic.co/t/logstash-gone-wrong-after-force-shutdown/351867>\
**Category:** Logstash\
**Created:** [January 26, 2024, 9:25am UTC](https://discuss.elastic.co/t/logstash-gone-wrong-after-force-shutdown/351867 "2024-01-26T09:25:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [January 26, 2024, 7:19pm UTC](https://discuss.elastic.co/t/logstash-gone-wrong-after-force-shutdown/351867/6 "2024-01-26T19:19:38Z")

</div>

Check this [topic](https://discuss.elastic.co/t/logstash-starts-but-doesn-t-do-anything/291637), maaaaybe data has been locked.

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_

---

_[View the full topic](https://discuss.elastic.co/t/logstash-gone-wrong-after-force-shutdown/351867)._