After upgrading logstash 6.7.0 to 7.0.1 continously restarting

Elastic Stack Logstash
1

Hi Team,
after upgrading logstash 6.7.0 to 7.0.1 unable to start logstash.
we are getting below error.
Hi Team,
after upgrading logstash 6.7.0 to 7.0.1 unable to start logstash.
we are getting below error.
[2019-06-11T10:37:24,771][WARN ][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=>"http://logstash:xxxxxx@localhost:9200/"}
[2019-06-11T10:37:24,777][INFO ][logstash.outputs.elasticsearch] ES Output version determined {:es_version=>7}
[2019-06-11T10:37:24,778][WARN ][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the type event field won't be used to determine the document _type {:es_version=>7}
[2019-06-11T10:37:24,775][FATAL][logstash.runner ] An unexpected error occurred! {:error=>#<LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client/manticore_adapter.rb:80:in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:291:inperform_request_to_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:278:in block in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:373:inwith_connection'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:277:in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:285:inblock in Pool'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client.rb:162:in get'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/http_client.rb:378:inget_xpack_info'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/ilm.rb:57:in ilm_ready?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/ilm.rb:28:inilm_in_use?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.0.2-java/lib/logstash/outputs/elasticsearch/common.rb:51:in block in setup_after_successful_connection'"]} [2019-06-11T10:37:24,789][INFO ][logstash.outputs.elasticsearch] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["http://localhost:9200"]} [2019-06-11T10:37:24,794][INFO ][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://logstash:xxxxxx@XX.XX.XX.XX:9200/]}} [2019-06-11T10:37:24,805][WARN ][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=>"http://logstash:xxxxxx@XX.XX.XX.XX:9200/"} [2019-06-11T10:37:24,829][INFO ][logstash.outputs.elasticsearch] ES Output version determined {:es_version=>7} [2019-06-11T10:37:24,830][WARN ][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: thetype` event field won't be used to determine the document _type {:es_version=>7}
[2019-06-11T10:37:24,882][ERROR][org.logstash.Logstash ] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit
[2019-06-11T10:37:47,772][INFO ][logstash.runner ] Starting Logstash {"logstash.version"=>"7.0.1"}

2

Hi @sharath_1245,

Have you checked the "Breaking Changes" docs before upgrading. There are some configuration/fields which needs to update or change.

Please check breaking changes docs to resolve this problem.

You can get assistant from upgrade assistant. It will show all the warnings and errors.

Br,
Harsh Bajaj

3

Hi Harsh,

Issue got Resolved.
After reading Breaking changes we found logstash neeed full permissions on indices.
After modifiyng logstash ROR permmisions its working fine.

Thanks & Regards,
Sharath Mankala

4

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