# Elasticsearch fails to start on Ubuntu nodes, other issues

**URL:** <https://discuss.elastic.co/t/elasticsearch-fails-to-start-on-ubuntu-nodes-other-issues/278599>\
**Category:** Elasticsearch\
**Created:** [July 14, 2021, 12:01am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-on-ubuntu-nodes-other-issues/278599 "2021-07-14T00:01:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bigheadred](https://avatars.discourse-cdn.com/v4/letter/b/65b543/32.png) [@bigheadred](https://discuss.elastic.co/u/bigheadred)\
**Post date:** [July 14, 2021, 12:01am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-on-ubuntu-nodes-other-issues/278599/1 "2021-07-14T00:01:02Z")

</div>

Hi,  
I've got a 3 node Elastic stack (each VM runs Elasticsearch and Logstash, one runs Elasticsearch, Logstash, and Kibana) set up on Microsoft Azure VM's, using Ubuntu 20.04.  
Recently, my elasticsearch cluster has been ignoring the network settings in elasticsearch.yml. The logs show it attempting to set the publish address to 127.0.0.1, no matter what I put in the network.host setting in elasticsearch.yml. This happens when the service is starting, and the log says that my cluster settings aren't suitable for production because the cluster settings haven't been configured, but they have and my cluster functioned with these exact settings. The service then fails to start.  
Any ideas on what's happening? It's elasticsearch 7.10.2  
I'm dealing with

---

<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:** [July 14, 2021, 8:45am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-on-ubuntu-nodes-other-issues/278599/2 "2021-07-14T08:45:33Z")

</div>

Sharing some logs output in a pastebin/gist would be great!

---

<div class="post-metadata">

**Author:** ![bigheadred](https://avatars.discourse-cdn.com/v4/letter/b/65b543/32.png) [@bigheadred](https://discuss.elastic.co/u/bigheadred)\
**Post date:** [July 14, 2021, 10:31pm UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-on-ubuntu-nodes-other-issues/278599/3 "2021-07-14T22:31:41Z")

</div>

sure thing! this is the chunk of log that shows it trying to use the wrong address

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/f/6fdff8ce2252c4e7f2f3a176843189d235e1fc2c.png)

same log, but here's elasticsearch shutting itself down

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/5/259212c5e6c6785d08c0adf6e057bf4dc90f29c3.png)

here's my network and discovery settings in elasticsearch.yml

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/7/876228ee84ee720afacc3bc5d134c1043c072d67.png)

each of the nodes uses that config, with the network.host being the IP address of the respective nodes

---

<div class="post-metadata">

**Author:** ![bigheadred](https://avatars.discourse-cdn.com/v4/letter/b/65b543/32.png) [@bigheadred](https://discuss.elastic.co/u/bigheadred)\
**Post date:** [July 16, 2021, 1:45am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-on-ubuntu-nodes-other-issues/278599/4 "2021-07-16T01:45:33Z")

</div>

Bump!

---

<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:** [August 13, 2021, 1:45am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-on-ubuntu-nodes-other-issues/278599/5 "2021-08-13T01:45:51Z")

</div>

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