# Logstash stops pipeline after exception

**URL:** <https://discuss.elastic.co/t/logstash-stops-pipeline-after-exception/64321>\
**Category:** Logstash\
**Created:** [October 28, 2016, 6:53pm UTC](https://discuss.elastic.co/t/logstash-stops-pipeline-after-exception/64321 "2016-10-28T18:53:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Akshaykapoor](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@Akshaykapoor](https://discuss.elastic.co/u/Akshaykapoor)\
**Post date:** [October 28, 2016, 6:53pm UTC](https://discuss.elastic.co/t/logstash-stops-pipeline-after-exception/64321/1 "2016-10-28T18:53:35Z")

</div>

I get this issue time and again, and the only way to get it to work again is to restart logstash.

This is what i see in my logs,

```
> {:timestamp=>"2016-10-28T18:44:24.951000+0000", :message=>"CircuitBreaker::rescuing exceptions", :name=>"Beats input", :exception=>LogStash::Inputs::Beats::InsertingToQueueTakeTooLong, :level=>:warn}
> {:timestamp=>"2016-10-28T18:44:24.951000+0000", :message=>"Beats input: The circuit breaker has detected a slowdown or stall in the pipeline, the input is closing the current connection and rejecting new connection until the pipeline recover.", :exception=>LogStash::Inputs::BeatsSupport::CircuitBreaker::HalfOpenBreaker, :level=>:warn}
> {:timestamp=>"2016-10-28T18:44:24.994000+0000", :message=>"CircuitBreaker::rescuing exceptions", :name=>"Beats input", :exception=>LogStash::Inputs::Beats::InsertingToQueueTakeTooLong, :level=>:warn}
> {:timestamp=>"2016-10-28T18:44:24.995000+0000", :message=>"Beats input: The circuit breaker has detected a slowdown or stall in the pipeline, the input is closing the current connection and rejecting new connection until the pipeline recover.", :exception=>LogStash::Inputs::BeatsSupport::CircuitBreaker::HalfOpenBreaker, :level=>:warn}
> {:timestamp=>"2016-10-28T18:44:25.479000+0000", :message=>"MarchHare::ChannelAlreadyClosed", :exception=>MarchHare::ChannelAlreadyClosed, :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/march_hare-2.15.0-java/lib/march_hare/exceptions.rb:121:in `convert_and_reraise'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/march_hare-2.15.0-java/lib/march_hare/channel.rb:976:in `converting_rjc_exceptions_to_ruby'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/march_hare-2.15.0-java/lib/march_hare/channel.rb:974:in `converting_rjc_exceptions_to_ruby'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/march_hare-2.15.0-java/lib/march_hare/channel.rb:606:in `basic_publish'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/march_hare-2.15.0-java/lib/march_hare/exchange.rb:77:in `publish'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-rabbitmq-3.0.9-java/lib/logstash/outputs/rabbitmq.rb:54:in `publish'", "org/jruby/RubyProc.java:281:in `call'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-codec-json-2.1.3/lib/logstash/codecs/json.rb:42:in `encode'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-rabbitmq-3.0.9-java/lib/logstash/outputs/rabbitmq.rb:47:in `receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/outputs/base.rb:83:in `multi_receive'", "org/jruby/RubyArray.java:1613:in `each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/outputs/base.rb:83:in `multi_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/output_delegator.rb:130:in `worker_multi_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/output_delegator.rb:129:in `worker_multi_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/output_delegator.rb:114:in `multi_receive'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/pipeline.rb:301:in `output_batch'", "org/jruby/RubyHash.java:1342:in `each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/pipeline.rb:301:in `output_batch'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/pipeline.rb:232:in `worker_loop'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/pipeline.rb:201:in `start_workers'"], :level=>:error}

```

The log file contains only these logs; there is nothing in elasticsearch or beats specific to this problem.

I see people having similar issues but probably because of some other plugins/reasons.

Can anybody help me with a solution to this. This keeps happening on our production system as well.

Akshay

---

<div class="post-metadata">

**Author:** ![Akshaykapoor](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@Akshaykapoor](https://discuss.elastic.co/u/Akshaykapoor)\
**Post date:** [November 10, 2016, 7:20pm UTC](https://discuss.elastic.co/t/logstash-stops-pipeline-after-exception/64321/2 "2016-11-10T19:20:56Z")

</div>

Guys anybody who's facing this issue and can provide a solution.

This is similar to the issue mentioned on github. [https://github.com/logstash-plugins/logstash-output-rabbitmq/issues/10](https://github.com/logstash-plugins/logstash-output-rabbitmq/issues/10)

---

<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:** [July 6, 2017, 4:30am UTC](https://discuss.elastic.co/t/logstash-stops-pipeline-after-exception/64321/3 "2017-07-06T04:30:38Z")

</div>