# SIGPIPE is not honoured consistently **URL:** \ **Category:** Logstash\ **Created:** [November 30, 2017, 9:25am UTC](https://discuss.elastic.co/t/sigpipe-is-not-honoured-consistently/109719 "2017-11-30T09:25:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![amitavmohanty01](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amitavmohanty01/32/58017_2.png) [@amitavmohanty01](https://discuss.elastic.co/u/amitavmohanty01)\ **Post date:** [November 30, 2017, 9:25am UTC](https://discuss.elastic.co/t/sigpipe-is-not-honoured-consistently/109719/1 "2017-11-30T09:25:46Z")
While running logstash on a remote server from the command line not as a service, I found that when there is a broken pipe, sometimes logstash process is killed and in other cases, the process keeps running on the server. Broken pipe signal is sent when SSH session is broken while the process is still running. Expectation: define the behaviour for SIGPIPE and honour it consistently and gracefully. "consistently" here means: if the behaviour chosen is killing of process, the process should be always killed. Otherwise, if the behaviour of process being intact is chosen, it should always be the behaviour. Version:5.6.4 Operating System: CentOS 6 ES is configured to listen to LS over network from a box on same subnet and LS in turn gets traffic over network from another box on the same subnet. Corresponding issue: [https://github.com/elastic/logstash/issues/8723](https://github.com/elastic/logstash/issues/8723) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 28, 2017, 9:25am UTC](https://discuss.elastic.co/t/sigpipe-is-not-honoured-consistently/109719/2 "2017-12-28T09:25:59Z")
Closed on December 28, 2017, 9:25am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.