# Logstash stopped processing because of an error: (SystemExit) exit **URL:** \ **Category:** Logstash\ **Created:** [August 15, 2019, 8:52pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393 "2019-08-15T20:52:40Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [August 15, 2019, 8:52pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393/1 "2019-08-15T20:52:40Z")
Hello World! I'm [Running Logstash on Docker | Logstash Reference [6.8] | Elastic](https://www.elastic.co/guide/en/logstash/6.8/docker.html) and getting following error: ``` logstash | Sending Logstash logs to /usr/share/logstash/logs which is now configured via log4j2.properties logstash | [2019-08-15T20:50:25,185][INFO][logstash.configmanagement.bootstrapcheck] Using Elasticsearch as config store {:pipeline_id=>["gelf", "nre", "upsertDome", "upsertMaid", "upsertMinion"], :poll_interval=>"5000000000ns"} logstash | [2019-08-15T20:50:26,012][INFO][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[https://elastic:xxxxxx@localhost:9200/]}} logstash | [2019-08-15T20:50:26,323][WARN][logstash.licensechecker.licensereader] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"https://elastic:xxxxxx@localhost:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [https://elastic:xxxxxx@localhost:9200/][Manticore::SocketException] Connection refused (Connection refused)"} logstash | [2019-08-15T20:50:26,385][WARN][logstash.licensechecker.licensereader] Marking url as dead. Last error: [LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError] Elasticsearch Unreachable: [https://elastic:xxxxxx@localhost:9200/][Manticore::SocketException] Connection refused (Connection refused) {:url=>https://elastic:xxxxxx@localhost:9200/, :error_message=>"Elasticsearch Unreachable: [https://elastic:xxxxxx@localhost:9200/][Manticore::SocketException] Connection refused (Connection refused)", :error_class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError"} logstash | [2019-08-15T20:50:26,398][ERROR][logstash.licensechecker.licensereader] Unable to retrieve license information from license server {:message=>"Elasticsearch Unreachable: [https://elastic:xxxxxx@localhost:9200/][Manticore::SocketException] Connection refused (Connection refused)"} logstash | [2019-08-15T20:50:26,585][ERROR][logstash.configmanagement.elasticsearchsource] Failed to fetch X-Pack information from Elasticsearch. This is likely due to failure to reach a live Elasticsearch cluster. logstash | [2019-08-15T20:50:26,598][FATAL][logstash.runner] An unexpected error occurred! {:error=>#, :backtrace=>["/usr/share/logstash/x-pack/lib/license_checker/licensed.rb:67:in `with_license_check'", "/usr/share/logstash/x-pack/lib/config_management/elasticsearch_source.rb:46:in `initialize'", "/usr/share/logstash/x-pack/lib/config_management/hooks.rb:41:in `after_bootstrap_checks'", "org/logstash/execution/EventDispatcherExt.java:71:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:304:in `execute'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:237:in `run'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-0.6.5/lib/clamp/command.rb:132:in `run'", "/usr/share/logstash/lib/bootstrap/environment.rb:73:in `
'"]} logstash | [2019-08-15T20:50:26,612][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit ``` there is no error if I'm using logstash 6.8.0 (w/ same configuration), yet error seems to appear _only_ if I use logstash 6.8.1 or 6.8.2. Please advise. ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [September 7, 2019, 3:37pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393/2 "2019-09-07T15:37:38Z")
> [@ERROR: Unable to retrieve license information from license server](https://discuss.elastic.co/t/error-unable-to-retrieve-license-information-from-license-server/198514): > > Hello World! I'm [Running Logstash on Docker | Logstash Reference [6.8] | Elastic](https://www.elastic.co/guide/en/logstash/6.8/docker.html), yet running into following error: logstash | [2019-09-07T15:15:06,686][INFO][logstash.configmanagement.bootstrapcheck] Using Elasticsearch as config store {:pipeline\_id=\>["gelf", "nre", "upsertDome", "upsertMaid", "upsertMinion"], :poll\_interval=\>"5000000000ns"} logstash | [2019-09-07T15:15:07,936][INFO][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=\>{:removed=\>[], :adde… ---
**Author:** ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)\ **Post date:** [September 9, 2019, 5:43am UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393/3 "2019-09-09T05:43:36Z")
> [@alexus](#): > > @alexus, > > logstash | [2019-08-15T20:50:26,398][ERROR][logstash.licensechecker.licensereader] Unable to retrieve license information from license server {:message=\>"Elasticsearch Unreachable: [[https://elastic:xxxxxx@localhost:9200/](https://elastic:xxxxxx@localhost:9200/)][Manticore::SocketException] Connection refused (Connection refused)"} From the above error its seems that your logstash server is unable to communicate with elasticsearch server over port 9200. Please try to `telnet elasticsearch_machine_ip 9200` from logstash machine. If unable to telnet then open the required firewall rule. Thanks. ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [September 9, 2019, 4:35pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393/4 "2019-09-09T16:35:48Z")
as soon as I roll back to `6.8.0` logstash is able to communicate with rest of cluster, it's only with 6.8.1+ it is unable to communicate, so the issue is not on my end, it is with logstash 6.8.1+, same thing I mentioned with my previous topic ... ---
**Author:** ![Tek\_Chand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tek_chand/32/34318_2.png) [@Tek\_Chand](https://discuss.elastic.co/u/Tek_Chand)\ **Post date:** [September 10, 2019, 4:48am UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393/5 "2019-09-10T04:48:31Z")
@alexus, May be some issue with logstash 6.8.1+, Please check at your end again some things like are you using same version of logstash, Elasticsearch, firewall rule etc. I have tested logstash 6.4.0 and logstash 7.2.0. Thanks. ---
**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\ **Post date:** [September 11, 2019, 4:07am UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393/6 "2019-09-11T04:07:10Z")
there is definitely looks like an issue w/ logstash 6.8.1+ elasticsearch cluster is running latest 6.8.3 version, yet logstash exits w/ any version (from 6 branch) higher than 6.8.0, "firewall rules" are okay, as logstash works w/ 6.8.0. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 9, 2019, 4:07am UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/195393/7 "2019-10-09T04:07:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.