# Logstash is throwing an error message and unable to stay up, keeps stopping and starting the pipeline

**URL:** <https://discuss.elastic.co/t/logstash-is-throwing-an-error-message-and-unable-to-stay-up-keeps-stopping-and-starting-the-pipeline/85487>\
**Category:** Logstash\
**Created:** [May 11, 2017, 9:42pm UTC](https://discuss.elastic.co/t/logstash-is-throwing-an-error-message-and-unable-to-stay-up-keeps-stopping-and-starting-the-pipeline/85487 "2017-05-11T21:42:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhealitycheck](https://avatars.discourse-cdn.com/v4/letter/r/3d9bf3/32.png) [@rhealitycheck](https://discuss.elastic.co/u/rhealitycheck)\
**Post date:** [May 11, 2017, 9:42pm UTC](https://discuss.elastic.co/t/logstash-is-throwing-an-error-message-and-unable-to-stay-up-keeps-stopping-and-starting-the-pipeline/85487/1 "2017-05-11T21:42:19Z")

</div>

I'm running a slightly older version of Logstash 5.1.1 on Amazon Linux 2017.03 with openjdk 1.8.0\_131 (because I'm also running the same version of Elasticsearch and Kibana). It is working in 2 clusters with the same hardware but on this one, it is unable to stay up. It keeps throwing this error:

[2017-05-11T21:05:28,185][ERROR][logstash.agent] Pipeline aborted due to error {:exception=\>#\<NoMethodError: undefined method `start_with?' for #<Array:0x31c79508>>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.4.0-java/lib/logstash/outputs/elasticsearch/http_client_builder.rb:80:in`setup\_ssl'", "org/jruby/RubyEnumerable.java:1459:in `any?'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.4.0-java/lib/logstash/outputs/elasticsearch/http_client_builder.rb:80:in`setup\_ssl'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.4.0-java/lib/logstash/outputs/elasticsearch/http\_client\_builder.rb:33:in `build'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.4.0-java/lib/logstash/outputs/elasticsearch.rb:196:in`build\_client'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.4.0-java/lib/logstash/outputs/elasticsearch/common.rb:13:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator_strategies/shared.rb:8:in`register'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator.rb:37:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:in`start\_workers'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:in`start\_workers'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:183:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:292:in`start\_pipeline'"]}`

So I tried downgrading the logstash-output-elasticsearch but that was clearly a red herring because I'm still getting the error it just now looks like:  
[2017-05-11T21:33:34,708][ERROR][logstash.agent] Pipeline aborted due to error {:exception=\>#\<NoMethodError: undefined method `start_with?' for #<Array:0x571e49e>>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.1.1-java/lib/logstash/outputs/elasticsearch/http_client_builder.rb:76:in`setup\_ssl'", "org/jruby/RubyEnumerable.java:1459:in `any?'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.1.1-java/lib/logstash/outputs/elasticsearch/http_client_builder.rb:76:in`setup\_ssl'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.1.1-java/lib/logstash/outputs/elasticsearch/http\_client\_builder.rb:29:in `build'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.1.1-java/lib/logstash/outputs/elasticsearch.rb:188:in`build\_client'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-5.1.1-java/lib/logstash/outputs/elasticsearch/common.rb:13:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator_strategies/shared.rb:8:in`register'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator.rb:37:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:in`start\_workers'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:in`start\_workers'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:183:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:292:in`start\_pipeline'"]}

Any idea what is causing this error and how I can get logstash running smoothly again?

---

<div class="post-metadata">

**Author:** ![rhealitycheck](https://avatars.discourse-cdn.com/v4/letter/r/3d9bf3/32.png) [@rhealitycheck](https://discuss.elastic.co/u/rhealitycheck)\
**Post date:** [May 12, 2017, 1:53am UTC](https://discuss.elastic.co/t/logstash-is-throwing-an-error-message-and-unable-to-stay-up-keeps-stopping-and-starting-the-pipeline/85487/2 "2017-05-12T01:53:54Z")

</div>

Oy, nevermind, I found an issue with my configs, I'm using chef to deploy my configs and I had double brackets around the elasticsearch ips because of the way they render. I fixed that and now everything is fine.

---

<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, 2017, 2:06am UTC](https://discuss.elastic.co/t/logstash-is-throwing-an-error-message-and-unable-to-stay-up-keeps-stopping-and-starting-the-pipeline/85487/3 "2017-06-09T02:06:29Z")

</div>

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