# Stalled Logstash Pipeline and Centralized Pipeline Management

**URL:** <https://discuss.elastic.co/t/stalled-logstash-pipeline-and-centralized-pipeline-management/272815>\
**Category:** Logstash\
**Created:** [May 12, 2021, 1:30pm UTC](https://discuss.elastic.co/t/stalled-logstash-pipeline-and-centralized-pipeline-management/272815 "2021-05-12T13:30:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![e.sharshenaliev](https://avatars.discourse-cdn.com/v4/letter/e/779978/32.png) [@e.sharshenaliev](https://discuss.elastic.co/u/e.sharshenaliev)\
**Post date:** [May 12, 2021, 1:30pm UTC](https://discuss.elastic.co/t/stalled-logstash-pipeline-and-centralized-pipeline-management/272815/1 "2021-05-12T13:30:03Z")

</div>

We are using one instance of Logstash (running on Debian VM via "systemctl start logstash") with x-pack Centralized Pipeline Management (CPM).

We've encountered the following problem: if for whatever reason pipelines is stalled, then:

1. Logstash stops picking-up changes from CPM
2. It is impossible to stop logstash service since no "unsafe shutdown" option in CPM

Is there any way to either forcefully stop logstash service or enable unsafe shutdown?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 9, 2021, 1:30pm UTC](https://discuss.elastic.co/t/stalled-logstash-pipeline-and-centralized-pipeline-management/272815/2 "2021-06-09T13:30:45Z")

</div>

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