# Elasticsearch does not start because of a graylog-server error

**URL:** <https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495>\
**Category:** Elasticsearch\
**Created:** [June 17, 2020, 3:06pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495 "2020-06-17T15:06:50Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![uek](https://avatars.discourse-cdn.com/v4/letter/u/df788c/32.png) [@uek](https://discuss.elastic.co/u/uek)\
**Post date:** [June 17, 2020, 3:06pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/1 "2020-06-17T15:06:50Z")

</div>

Hello there,

my elasticsearch-oss I would like to use in combination with prometheus and grafana does not start on my centos8 machine because of theese errors :  
_Automatic restarting of the unit graylog-server.service has been scheduled, as the result for_

- -- the configured Restart= setting for the unit.\*
- Jun 17 16:55:21 keyhole systemd[1]: Stopped Graylog server.\*
- -- Subject: Unit graylog-server.service has finished shutting down\*
- -- Defined-By: systemd\*
- -- Support: [https://access.redhat.com/support\*](https://access.redhat.com/support*)
- -- \*
- -- Unit graylog-server.service has finished shutting down.\*
- Jun 17 16:55:21 keyhole systemd[1]: Started Graylog server.\*
- -- Subject: Unit graylog-server.service has finished start-up\*
- -- Defined-By: systemd\*
- -- Support: [https://access.redhat.com/support\*](https://access.redhat.com/support*)
- -- \*
- -- Unit graylog-server.service has finished starting up.\*
- -- \*
- -- The start-up result is done.\*
- Jun 17 16:55:25 keyhole systemd[1]: graylog-server.service: Main process exited, code=exited, status=1/FAILURE\*
- Jun 17 16:55:25 keyhole systemd[1]: graylog-server.service: Failed with result 'exit-code'.\*

I already removed /var/lib/elasticsearch/nodes/0/node.lock  
to abvoid an Exception

_`Caused by: java.io.IOException: failed to obtain lock on /var/lib/elasticsearch/nodes/0`_

, but without success elaticsearch does not start.  
Please find my logfile here: [https://pastebin.com/mkxiTDQm](https://pastebin.com/mkxiTDQm)

the elasticsearch.yml here: [https://pastebin.com/xWuDxJhk](https://pastebin.com/xWuDxJhk)

If anyone has an idea or solution , please let me know.

Many thanks in advance

Uli

---

<div class="post-metadata">

**Author:** ![Vinayak\_Sapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinayak_sapre/32/45939_2.png) [@Vinayak\_Sapre](https://discuss.elastic.co/u/Vinayak_Sapre)\
**Post date:** [June 18, 2020, 2:04am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/2 "2020-06-18T02:04:12Z")

</div>

This may be directory permission issue. For ex. if _`/var/lib/elasticsearch`_ is owned by root and service is running as elasticsearch user.

Everything under _`/var/lib/elasticsearch`_ should be owned / writable by the user running elasticsearch service.

---

<div class="post-metadata">

**Author:** ![uek](https://avatars.discourse-cdn.com/v4/letter/u/df788c/32.png) [@uek](https://discuss.elastic.co/u/uek)\
**Post date:** [June 18, 2020, 9:55am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/3 "2020-06-18T09:55:39Z")

</div>

Hello Vinayak,

Thanks for your advice. I changed the permissions  
**`chmod 777 -R elasticsearch:elasticsearch /var/lib/elasticsearch`**

but without success

---

<div class="post-metadata">

**Author:** ![uek1967](https://avatars.discourse-cdn.com/v4/letter/u/7feea3/32.png) [@uek1967](https://discuss.elastic.co/u/uek1967)\
**Post date:** [June 18, 2020, 12:58pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/4 "2020-06-18T12:58:56Z")

</div>

it now looks like: _cd /var/lib/elasticsearch/_

- [root@keyhole elasticsearch]# ls -la\*
- total 4\*
- drwxrwsrwx. 3 elasticsearch elasticsearch 19 May 28 18:37 .\*
- drwxr-xr-x. 67 root root 4096 Jun 15 22:34 ..\*
- drwxrwsrwx. 3 elasticsearch elasticsearch 15 Jun 12 19:13 nodes\*

but no change and nothing in elasticsearch.log

Any Advice is appreciated

Thanks in advance

Uli

---

<div class="post-metadata">

**Author:** ![Vinayak\_Sapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinayak_sapre/32/45939_2.png) [@Vinayak\_Sapre](https://discuss.elastic.co/u/Vinayak_Sapre)\
**Post date:** [June 19, 2020, 7:17am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/5 "2020-06-19T07:17:23Z")

</div>

Hi Uli

I found `Caused by: java.nio.file.NoSuchFileException: /var/lib/elasticsearch/nodes/0/node.lock` in the logs.

Can you check if the file `/var/lib/elasticsearch/nodes/0/node.lock` exists?

If not try `sudo touch /var/lib/elasticsearch/nodes/0/node.lock` This will create a zero byte file.. Then change ownership of this file to elasticsearch and permissions to 644.

---

<div class="post-metadata">

**Author:** ![uek1967](https://avatars.discourse-cdn.com/v4/letter/u/7feea3/32.png) [@uek1967](https://discuss.elastic.co/u/uek1967)\
**Post date:** [June 19, 2020, 12:54pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/6 "2020-06-19T12:54:01Z")

</div>

Hi Vinayak,

I deleted that file following another advice und cerated ist now as you said:

touch /var/lib/elasticsearch/nodes/0/node.lock

and set permissions to 644  
chmod 644 /var/lib/elasticsearch/nodes/0/node.lock

but it doesn't start

_`systemctl start elasticsearch.service`_  
Job for elasticsearch.service failed because the control process exited with error code.  
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.

Here I have the last 50 lines of the logfile ,

```
*tail -50 /var/log/elasticsearch/elasticsearch.log *
* at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:227) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:227) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393) [elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) [elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) [elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) [elasticsearch-cli-7.7.1.jar:7.7.1]*
* at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) [elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) [elasticsearch-7.7.1.jar:7.7.1]*
*[2020-06-19T14:32:13,293][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [keyhole] uncaught exception in thread [main]*
*org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [nsport.host] please check that any required plugins are installed, or check the breaking changes documentation for removed settings*
*	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:174) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) ~[elasticsearch-cli-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.7.1.jar:7.7.1]*
*Caused by: java.lang.IllegalArgumentException: unknown setting [nsport.host] please check that any required plugins are installed, or check the breaking changes documentation for removed settings*
*	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:544) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:489) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:460) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:431) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:149) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.node.Node.<init>(Node.java:365) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.node.Node.<init>(Node.java:264) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:227) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:227) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) ~[elasticsearch-7.7.1.jar:7.7.1]*
*	... 6 more*
*	Suppressed: java.lang.IllegalArgumentException: unknown setting [xpack.ml.enabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings*
* at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:544) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:489) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:460) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:431) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:149) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.node.Node.<init>(Node.java:365) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.node.Node.<init>(Node.java:264) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:227) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:227) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) ~[elasticsearch-cli-7.7.1.jar:7.7.1]*
* at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) ~[elasticsearch-7.7.1.jar:7.7.1]*
* at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.7.1.jar:7.7.1]*

```

I found this:  
_uncaught exception in thread [main]_  
_org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [nsport.host] please check that any required plugins are installed, or check the breaking changes documentation for removed settings_

and this:  
_`llegalArgumentException: unknown setting [nsport.host] please check that any required plugins are installed, or check the breaking changes documentation for removed settings`_

futher this:

_`Suppressed: java.lang.IllegalArgumentException: unknown setting [xpack.ml.enabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings`_

I changed elasticsearch.yml section like this:

```
*# Set the bind address to a specific IP (IPv4 or IPv6):*
*#*
*network.host: 127.0.0.1*
*#*
*# Set a custom port for HTTP:*
*#*
*http.port: 9200*

*#transsport.host: localhost *

*#transport.tcp.port: 9300 *

*xpack.ml.enabled: false*

```

but all this didn't help to start elasticsearch

I'm pretty much at the end of my rope. Any thoughts on what I might try?

Many thanks in advance

Uli

---

<div class="post-metadata">

**Author:** ![Vinayak\_Sapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinayak_sapre/32/45939_2.png) [@Vinayak\_Sapre](https://discuss.elastic.co/u/Vinayak_Sapre)\
**Post date:** [June 19, 2020, 2:27pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/7 "2020-06-19T14:27:18Z")

</div>

Hi Uli  
Looks like you have moved past the "lock" issue.

elasticsearch.yml you posted in your first post `transport.host` was misspelled as `nsport.host`. In the latest post, it is misspelled again `transsport.host:`.

Is \* present as the first character on each line? If yes, that's an issue too.

Setting transport.host to localhost means you cannot expand the cluster as no other node will be able to reach this node on 9300. Comment out the line `nsport.host`. Also, if you may want to use special values for network.host as describe [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html)

```auto
network.host: 192.168.10.3
#
# Set a custom port for HTTP:
#
http.port: 9200

#transport.host: localhost

transport.tcp.port: 9300

xpack.ml.enabled: false 

```

---

<div class="post-metadata">

**Author:** ![uek1967](https://avatars.discourse-cdn.com/v4/letter/u/7feea3/32.png) [@uek1967](https://discuss.elastic.co/u/uek1967)\
**Post date:** [June 19, 2020, 5:05pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/8 "2020-06-19T17:05:37Z")

</div>

Hello Vinayak,

I am am terribly to inform you that the modifications in elasticsearch.ym didn't change anything. Same error as before.

I am trying to find a solution for this:

_`Caused by: java.lang.IllegalArgumentException: unknown setting [xpack.ml.enabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings`_

If you maybe have another proposal please feel free to tell me.

Many thanks in advance

Uli

---

<div class="post-metadata">

**Author:** ![Vinayak\_Sapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinayak_sapre/32/45939_2.png) [@Vinayak\_Sapre](https://discuss.elastic.co/u/Vinayak_Sapre)\
**Post date:** [June 19, 2020, 5:22pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/9 "2020-06-19T17:22:31Z")

</div>

Uli,  
If your setup has multiple issues it will take iterations to solve them one by one.

I just noticed in your first post you mentioned elasticsearch-oss. This version does not include x-pack plugin. So delete _`xpack.ml.enabled`_ line from yaml.

---

<div class="post-metadata">

**Author:** ![uek1967](https://avatars.discourse-cdn.com/v4/letter/u/7feea3/32.png) [@uek1967](https://discuss.elastic.co/u/uek1967)\
**Post date:** [June 19, 2020, 9:05pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/10 "2020-06-19T21:05:14Z")

</div>

Hello Vinayak,

Thanks again; I removed xmlpack from the elasticsearch.yml  
, but elasticstearch still does not start.  
Here is a plot of the logfile:  
\*tail -20 /var/log/elasticsearch/elasticsearch.log \*  
_[2020-06-19T22:35:24,278][INFO][o.e.p.PluginsService] [keyhole] loaded module [percolator]_  
_[2020-06-19T22:35:24,280][INFO][o.e.p.PluginsService] [keyhole] loaded module [rank-eval]_  
_[2020-06-19T22:35:24,281][INFO][o.e.p.PluginsService] [keyhole] loaded module [reindex]_  
_[2020-06-19T22:35:24,282][INFO][o.e.p.PluginsService] [keyhole] loaded module [repository-url]_  
_[2020-06-19T22:35:24,284][INFO][o.e.p.PluginsService] [keyhole] loaded module [systemd]_  
_[2020-06-19T22:35:24,285][INFO][o.e.p.PluginsService] [keyhole] loaded module [tasks]_  
_[2020-06-19T22:35:24,286][INFO][o.e.p.PluginsService] [keyhole] loaded module [transport-netty4]_  
_[2020-06-19T22:35:24,291][INFO][o.e.p.PluginsService] [keyhole] no plugins loaded_  
_[2020-06-19T22:35:39,195][INFO][o.e.d.DiscoveryModule] [keyhole] using discovery type [zen] and seed hosts providers [settings]_  
_[2020-06-19T22:35:41,276][INFO][o.e.n.Node] [keyhole] initialized_  
_[2020-06-19T22:35:41,277][INFO][o.e.n.Node] [keyhole] starting ..._  
_[2020-06-19T22:35:41,858][INFO][o.e.t.TransportService] [keyhole] publish\_address {192.168.10.3:9300}, bound\_addresses {192.168.10.3:9300}_  
_[2020-06-19T22:35:43,301][INFO][o.e.b.BootstrapChecks] [keyhole] bound or publishing to a non-loopback address, enforcing bootstrap checks_  
_[2020-06-19T22:35:43,315][ERROR][o.e.b.Bootstrap] [keyhole] node validation exception_  
_[1] bootstrap checks failed_  
_[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes] must be configured_  
_[2020-06-19T22:35:43,328][INFO][o.e.n.Node] [keyhole] stopping ..._  
_[2020-06-19T22:35:43,390][INFO][o.e.n.Node] [keyhole] stopped_  
_[2020-06-19T22:35:43,396][INFO][o.e.n.Node] [keyhole] closing ..._  
_[2020-06-19T22:35:43,482][INFO][o.e.n.Node] [keyhole] closed_

Might it be this, that prevents elastisearch from starting:

```
*1] bootstrap checks failed*
*[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured*

```

Thanks in advance,

Uli

---

<div class="post-metadata">

**Author:** ![Vinayak\_Sapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinayak_sapre/32/45939_2.png) [@Vinayak\_Sapre](https://discuss.elastic.co/u/Vinayak_Sapre)\
**Post date:** [June 19, 2020, 10:23pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/11 "2020-06-19T22:23:29Z")

</div>

I am assuming

- This is your local development environment. Before setting up a shared or a production cluster you must read [https://www.elastic.co/guide/en/elasticsearch/reference/7.8/setup.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/setup.html).

- You are not planning to add more nodes to the ES cluster. If you are, then you need to read setup guide.

- You want this ES to be accessible from a host other than 192.168.10.3. If the application accessing ES is running on the same host (192.168.10.3), this is typical in a development environment, just comment the network.host line. Then other application can access it as [http://localhost:9200](http://localhost:9200)

If these 3 assumptions are valid add following line to elasticsearch.yml  
`discovery.seed_hosts: 192.168.10.3`

Then the other application will be able access it using [http://192.168.10.3:9200](http://192.168.10.3:9200)

**Must read**  
[https://www.elastic.co/guide/en/elasticsearch/reference/7.8/network.host.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/network.host.html)  
[https://www.elastic.co/guide/en/elasticsearch/reference/7.8/discovery-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/discovery-settings.html)  
[https://www.elastic.co/guide/en/elasticsearch/reference/7.8/modules-network.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/modules-network.html)

---

<div class="post-metadata">

**Author:** ![uek1967](https://avatars.discourse-cdn.com/v4/letter/u/7feea3/32.png) [@uek1967](https://discuss.elastic.co/u/uek1967)\
**Post date:** [June 23, 2020, 1:41pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/12 "2020-06-23T13:41:33Z")

</div>

Hello Vinayak,

Many thanks again for your help. Following your advice I got elasticsearch and logstash running now. Neither filebeat nor metricbeat I was able to get running and instead of Kibana I will use prometheus and grafana. (bothe are running yet). What I didn't found out yet is how I have to edtit the .yml files so that my elasticsearch host monitors all devices in my network and waht is the logstash index that grafana asks for.

Best regards,

Uli

---

<div class="post-metadata">

**Author:** ![Vinayak\_Sapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinayak_sapre/32/45939_2.png) [@Vinayak\_Sapre](https://discuss.elastic.co/u/Vinayak_Sapre)\
**Post date:** [June 29, 2020, 12:04am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/13 "2020-06-29T00:04:18Z")

</div>

Hi Uli,  
If your original issues is solved, then you can mark this solved and open another topic.

---

<div class="post-metadata">

**Author:** ![uek1967](https://avatars.discourse-cdn.com/v4/letter/u/7feea3/32.png) [@uek1967](https://discuss.elastic.co/u/uek1967)\
**Post date:** [June 29, 2020, 12:05pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/14 "2020-06-29T12:05:13Z")

</div>

Problem solved!

Many thanks

---

<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:** [July 27, 2020, 12:05pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-start-because-of-a-graylog-server-error/237495/15 "2020-07-27T12:05:14Z")

</div>

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