# Logstash not pushing flush onto pipeline

**URL:** <https://discuss.elastic.co/t/logstash-not-pushing-flush-onto-pipeline/124817>\
**Category:** Logstash\
**Created:** [March 20, 2018, 4:24pm UTC](https://discuss.elastic.co/t/logstash-not-pushing-flush-onto-pipeline/124817 "2018-03-20T16:24:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![smbullet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/smbullet/32/27833_2.png) [@smbullet](https://discuss.elastic.co/u/smbullet)\
**Post date:** [March 20, 2018, 4:24pm UTC](https://discuss.elastic.co/t/logstash-not-pushing-flush-onto-pipeline/124817/1 "2018-03-20T16:24:37Z")

</div>

I'm trying to debug one of my logstash machines that doesn't seem to be processing incoming syslog. I was reading this ([https://www.elastic.co/guide/en/logstash/2.4/pipeline.html#\_fault\_tolerance](https://www.elastic.co/guide/en/logstash/2.4/pipeline.html#_fault_tolerance)) and noticed that my working logstash machine will produce this log message every 5 seconds but the one that isn't working does not.

[2018-03-20T12:18:51,027][DEBUG][logstash.pipeline] Pushing flush onto pipeline

Debug is enabled on both these machines and everything else about them should be identical. I'm assuming that means one of my plugins is broken and blocking the pipeline and I just haven't caught it on the working machine yet. Is this a decent assumption?

Also does anyone have any suggestions on debugging a stuck output or filter?

---

<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:** [April 17, 2018, 4:24pm UTC](https://discuss.elastic.co/t/logstash-not-pushing-flush-onto-pipeline/124817/2 "2018-04-17T16:24:43Z")

</div>

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