# Custom logstash image fails with java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

**URL:** <https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318>\
**Category:** Logstash\
**Created:** [April 24, 2019, 7:17pm UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318 "2019-04-24T19:17:56Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pouria\_Fewzee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pouria_fewzee/32/44763_2.png) [@Pouria\_Fewzee](https://discuss.elastic.co/u/Pouria_Fewzee)\
**Post date:** [April 24, 2019, 7:17pm UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/1 "2019-04-24T19:17:57Z")

</div>

Hi, the following is my logstash.conf and logstash.yml files:

logstash.conf

```
input { beats { port => 5044 } }
filter {}
output { http {
    http_mehod => "post"
    url => "https://dydx.ngrok.io"
} }

```

logstash.yml

```
http.post: "0.0.0.0"
xpack.monitoring.enabled: false

```

I'm replacing the logstash.conf and logstash.yml in /usr/share/logstash/pipeline and config directories with the files above. The docker image used is 7.0.0.

Docker is built fine, however, upon running I get the following:

java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 24, 2019, 8:49pm UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/2 "2019-04-24T20:49:21Z")

</div>

I would expect there to be additional error messages preceding that.

---

<div class="post-metadata">

**Author:** ![Pouria\_Fewzee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pouria_fewzee/32/44763_2.png) [@Pouria\_Fewzee](https://discuss.elastic.co/u/Pouria_Fewzee)\
**Post date:** [April 24, 2019, 9:24pm UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/3 "2019-04-24T21:24:21Z")

</div>

Here's what comes before it:

```
Sending Logstash logs to /usr/share/logstash/logs which is now configured via log4j2.properties
[2019-04-24T21:22:35,161][FATAL][logstash.runner] An unexpected error occurred! {:error=>#<ArgumentError: Setting "http.post" hasn't been registered>, :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/settings.rb:36:in `get_setting'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:69:in `set_value'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:88:in `block in merge'", "org/jruby/RubyHash.java:1419:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:88:in `merge'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:137:in `validate_all'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:278: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 `<main>'"]}
[2019-04-24T21:22:35,191][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit
```

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 24, 2019, 9:30pm UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/4 "2019-04-24T21:30:52Z")

</div>

> [@Pouria\_Fewzee](#):
>
> Setting "http.post" hasn't been registered

You have an entry for http.post in your logstash.yml, but there is no code in logstash that is set up to consume that. The fix is most likely to comment out that line.

What were you trying to achieve by adding it?

---

<div class="post-metadata">

**Author:** ![Pouria\_Fewzee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pouria_fewzee/32/44763_2.png) [@Pouria\_Fewzee](https://discuss.elastic.co/u/Pouria_Fewzee)\
**Post date:** [April 24, 2019, 9:40pm UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/5 "2019-04-24T21:40:01Z")

</div>

It gets added by the entrypoint, and [here](https://www.elastic.co/guide/en/logstash/current/docker-config.html#_docker_defaults) it says the defaults are to be kept, in case the yml file is to be replaced. I would like to turn off x-pack, as it complains about [http://elasticsearch:9200](http://elasticsearch:9200) not existing. If I understand correctly, that value is set by the yml file, and is populated by the entrypoint script.

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 24, 2019, 9:45pm UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/6 "2019-04-24T21:45:11Z")

</div>

It should be http.host, with an h, not http.post.

---

<div class="post-metadata">

**Author:** ![Pouria\_Fewzee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pouria_fewzee/32/44763_2.png) [@Pouria\_Fewzee](https://discuss.elastic.co/u/Pouria_Fewzee)\
**Post date:** [April 25, 2019, 12:59am UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/7 "2019-04-25T00:59:20Z")

</div>

Unbelievable. Thank you for bringing that to my attention Badger.

---

<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:** [May 23, 2019, 12:59am UTC](https://discuss.elastic.co/t/custom-logstash-image-fails-with-java-lang-illegalstateexception-logstash-stopped-processing-because-of-an-error-systemexit-exit/178318/8 "2019-05-23T00:59:23Z")

</div>

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