# Why Elasticsearch still complains about bootstrap checks failed

**URL:** <https://discuss.elastic.co/t/why-elasticsearch-still-complains-about-bootstrap-checks-failed/194690>\
**Category:** Elasticsearch\
**Created:** [August 10, 2019, 4:19am UTC](https://discuss.elastic.co/t/why-elasticsearch-still-complains-about-bootstrap-checks-failed/194690 "2019-08-10T04:19:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hobby](https://avatars.discourse-cdn.com/v4/letter/h/e274bd/32.png) [@hobby](https://discuss.elastic.co/u/hobby)\
**Post date:** [August 10, 2019, 4:19am UTC](https://discuss.elastic.co/t/why-elasticsearch-still-complains-about-bootstrap-checks-failed/194690/1 "2019-08-10T04:19:29Z")

</div>

Installed ES 7.3.0 on Ubuntu 18.04. Was able to start it in development mode. Now I want to connect to ES remotely from another machine, so I changed the configuration in elasticsearch.yml and tried to start it in production mode (although there's still only one ES machine). Below is my elasticsearch.yml file:

 ![Screenshot%20from%202019-08-10%2011-53-48](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c7984cc662da8e50fecff516673a23c0c9c341f5.png)

However, everytime after I run the 'sudo systemctl start elasticsearch.service' command, the elasticsearch gave me this warning "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".

 ![Screenshot%20from%202019-08-10%2011-52-35](https://us1.discourse-cdn.com/elastic/original/3X/8/3/838c535ebe1d8e4422ce36466479d3126c5ac475.png)

As you can see in the first image, I do configure the cluster.initial\_master\_nodes correctly. So what did I miss here?

---Updates------------------------------------------------------------------------------------------------------------------------  
I just realized that no matter how many times I tried to restart the elasticsearch service, for some reason it is not updating the log file. As you can see the timestamp for the last log is 2019-08-10, which is yesterday. I am pretty sure I restarted the service this morning several times and today is 2019-08-11. P.S. I am in UTC-8 timezone.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [August 12, 2019, 3:39pm UTC](https://discuss.elastic.co/t/why-elasticsearch-still-complains-about-bootstrap-checks-failed/194690/3 "2019-08-12T15:39:11Z")

</div>

please do not post images, but only text - as this image is barely readable on bigger monitors.

try stopping the service first or run restart and then check if the logfile shows any new entries.

---

<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:** [September 9, 2019, 3:39pm UTC](https://discuss.elastic.co/t/why-elasticsearch-still-complains-about-bootstrap-checks-failed/194690/4 "2019-09-09T15:39:14Z")

</div>

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