# One pipeline fail restarts Logstash, disrupting all other pipelines defined in pipelines.yml

**URL:** <https://discuss.elastic.co/t/one-pipeline-fail-restarts-logstash-disrupting-all-other-pipelines-defined-in-pipelines-yml/241845>\
**Category:** Logstash\
**Created:** [July 20, 2020, 6:46am UTC](https://discuss.elastic.co/t/one-pipeline-fail-restarts-logstash-disrupting-all-other-pipelines-defined-in-pipelines-yml/241845 "2020-07-20T06:46:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![saif3r](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@saif3r](https://discuss.elastic.co/u/saif3r)\
**Post date:** [July 20, 2020, 6:46am UTC](https://discuss.elastic.co/t/one-pipeline-fail-restarts-logstash-disrupting-all-other-pipelines-defined-in-pipelines-yml/241845/1 "2020-07-20T06:46:50Z")

</div>

Hello,

We have around 20 different pipelines defined in our pipelines.yml. One of them is outputing elastic query result to a file in a dedicated folder. Last weekend the owner of this folder changed to root, making Logstash unable to write there. This caused our pipeline to fail. Unfortunately, due to this error, the entire Logstash service kept restarting until we filxed folder ownership. Is there a way to avoid such situation, making sure that if one pipeline will fail, other will keep running?

---

<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:** [August 17, 2020, 6:46am UTC](https://discuss.elastic.co/t/one-pipeline-fail-restarts-logstash-disrupting-all-other-pipelines-defined-in-pipelines-yml/241845/2 "2020-08-17T06:46:51Z")

</div>

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