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


(Rhealitycheck) #1

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:insetup_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:insetup_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:inbuild_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:inregister'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator.rb:37:in register'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:instart_workers'", "org/jruby/RubyArray.java:1613:in each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:instart_workers'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:183:in run'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:292:instart_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:insetup_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:insetup_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:inbuild_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:inregister'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator.rb:37:in register'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:instart_workers'", "org/jruby/RubyArray.java:1613:in each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:229:instart_workers'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:183:in run'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:292:instart_pipeline'"]}

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


(Rhealitycheck) #2

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.


(system) #3

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