# Unable to start Elasticsearch after clean installation (CentOS or Ubuntu)

**URL:** <https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-clean-installation-centos-or-ubuntu/208181>\
**Category:** Elasticsearch\
**Created:** [November 16, 2019, 7:08pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-clean-installation-centos-or-ubuntu/208181 "2019-11-16T19:08:01Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![MiTschMR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mitschmr/32/48254_2.png) [@MiTschMR](https://discuss.elastic.co/u/MiTschMR)\
**Post date:** [November 18, 2019, 12:04pm UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-clean-installation-centos-or-ubuntu/208181/21 "2019-11-18T12:04:40Z")

</div>

Hi @theo1

It looks like your cluster is configured with only one node. Because you specified `network.host` your cluster is going through the bootstrap checks, take a look [here](https://www.elastic.co/guide/en/elasticsearch/reference/7.4/bootstrap-checks.html).

On the same page you also find an option to set for single-discovery. Please try it with this setting.

---

<div class="post-metadata">

**Author:** ![theo1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theo1/32/57733_2.png) [@theo1](https://discuss.elastic.co/u/theo1)\
**Post date:** [November 19, 2019, 1:52am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-clean-installation-centos-or-ubuntu/208181/22 "2019-11-19T01:52:37Z")

</div>

Thanks ikakavas and MiTschMR.

It's working now. Here's a diff between the original file and the current file so you can see what's changed:

```
[tedl@localhost ~]$ sudo diff /etc/elasticsearch/elasticsearch.yml /etc/elasticsearch/elasticsearch.yml.0
17c17
< cluster.name: wazuh-el-log
---
> #cluster.name: my-application
23c23
< node.name: wazuh-el-node1
---
> node.name: node-1
59c59
< http.port: 9200
---
> #http.port: 9200
72c72
< cluster.initial_master_nodes: ["wazuh-el-node1"]
---
> cluster.initial_master_nodes: ["node-1"]
89,92d88
< #
< # Adding entry to get past error
< #
< xpack.ml.enabled: false

```

The xpack.ml.enabled:false disables Machine Learning. I'm using a very old processor and it seemed to be causing issues with Machine Learning started.

I'm going to try the installation process on a newer system to see if I can have Machine Learning enabled.

Many thanks for all the help!

Ted

---

<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:** [December 17, 2019, 1:52am UTC](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-clean-installation-centos-or-ubuntu/208181/23 "2019-12-17T01:52:40Z")

</div>

Closed on December 17, 2019, 1:52am UTC

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

[Previous page](https://discuss.elastic.co/t/unable-to-start-elasticsearch-after-clean-installation-centos-or-ubuntu/208181.md?page=1)
