# Error ArgumentError Setting "xpack.monitoring.elasticsearch.hosts" hasn't been registered

**URL:** <https://discuss.elastic.co/t/error-argumenterror-setting-xpack-monitoring-elasticsearch-hosts-hasnt-been-registered/172418>\
**Category:** Logstash\
**Created:** [March 14, 2019, 9:04pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-xpack-monitoring-elasticsearch-hosts-hasnt-been-registered/172418 "2019-03-14T21:04:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adrian\_Hove](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrian_hove/32/42038_2.png) [@Adrian\_Hove](https://discuss.elastic.co/u/Adrian_Hove)\
**Post date:** [March 14, 2019, 9:04pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-xpack-monitoring-elasticsearch-hosts-hasnt-been-registered/172418/1 "2019-03-14T21:04:37Z")

</div>

I get the error below:

```
root@b48c5173f995:/var/www# /usr/share/logstash/bin/logstash -e 'input { stdin { } } output { stdout {} }' 

Sending Logstash logs to /usr/share/logstash/logs which is now configured via log4j2.properties [2019-03-14T22:05:37,889][FATAL][logstash.runner] An unexpected error occurred! {:error=>#<ArgumentError: Setting "xpack.monitoring.elasticsearch.hosts" 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:1343: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.3.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.3.0/gems/clamp-0.6.5/lib/clamp/command.rb:132:in `run'", "/usr/share/logstash/lib/bootstrap/environment.rb:73:in `<main>'"]} [2019-03-14T22:05:38,228][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

```

This is whats in my logstash.yml

```
http: 
  host: "0.0.0.0"
node: 
  name: logstash
xpack: 
  monitoring: 
    elasticsearch: 
      hosts: 
        - "http://elasticsearch:9200"
```

---

<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:** [March 14, 2019, 9:43pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-xpack-monitoring-elasticsearch-hosts-hasnt-been-registered/172418/2 "2019-03-14T21:43:39Z")

</div>

> [@Adrian\_Hove](#):
>
> xpack.monitoring.elasticsearch.hosts" hasn't been registered

I've seen that when xpack is not installed.

---

<div class="post-metadata">

**Author:** ![Adrian\_Hove](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrian_hove/32/42038_2.png) [@Adrian\_Hove](https://discuss.elastic.co/u/Adrian_Hove)\
**Post date:** [March 14, 2019, 9:57pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-xpack-monitoring-elasticsearch-hosts-hasnt-been-registered/172418/3 "2019-03-14T21:57:06Z")

</div>

I tried to install X-Pack

```
root@b48c5173f995:/var/www# /usr/share/logstash/bin/logstash-plugin install x-pack
Logstash now contains X-Pack by default, there is no longer any need to install
it as it is already present.
```

---

<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:** [April 11, 2019, 9:57pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-xpack-monitoring-elasticsearch-hosts-hasnt-been-registered/172418/4 "2019-04-11T21:57:07Z")

</div>

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