# Issues with starting elasticsearch
**URL:** https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913
**Category:** Elasticsearch
**Created:** [March 17, 2020, 11:22am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913 "2020-03-17T11:22:16Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@ankitagarwal10k](https://discuss.elastic.co/u/ankitagarwal10k)
#### Post date: [March 17, 2020, 11:22am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/1 "2020-03-17T11:22:16Z")
When I am trying to start the elasticsearch, i am getting the below logs:
> [2020-03-17T16:41:33,633][WARN][i.n.u.i.MacAddressUtil] [elasticsearch-node-1] Failed to find a usable hardware address from the network interfaces; using random bytes: c2:36:b4:29:40:e3:5a:d9
> [2020-03-17T16:41:33,684][INFO][o.e.t.TransportService] [elasticsearch-node-1] publish\_address {127.0.0.1:9300}, bound\_addresses {127.0.0.1:9300}
> [2020-03-17T16:41:44,281][WARN][o.e.c.c.ClusterFormationFailureHelper] [elasticsearch-node-1] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial\_master\_nodes] is empty on this node: have discovered [{elasticsearch-node-1}{1g6-SPfbTHi0eRfjXuLYLg}{pPs6OInqSP-igVsXUSnOIw}{127.0.0.1}{127.0.0.1:9300}{dilm}{ml.machine\_memory=16723513344, xpack.installed=true, ml.max\_open\_jobs=20}]; discovery will continue using from hosts providers and [{elasticsearch-node-1}{1g6-SPfbTHi0eRfjXuLYLg}{pPs6OInqSP-igVsXUSnOIw}{127.0.0.1}{127.0.0.1:9300}{dilm}{ml.machine\_memory=16723513344, xpack.installed=true, ml.max\_open\_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
> [2020-03-17T16:41:54,284][WARN][o.e.c.c.ClusterFormationFailureHelper] [elasticsearch-node-1] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial\_master\_nodes] is empty on this node: have discovered [{elasticsearch-node-1}{1g6-SPfbTHi0eRfjXuLYLg}{pPs6OInqSP-igVsXUSnOIw}{127.0.0.1}{127.0.0.1:9300}{dilm}{ml.machine\_memory=16723513344, xpack.installed=true, ml.max\_open\_jobs=20}]; discovery will continue using from hosts providers and [{elasticsearch-node-1}{1g6-SPfbTHi0eRfjXuLYLg}{pPs6OInqSP-igVsXUSnOIw}{127.0.0.1}{127.0.0.1:9300}{dilm}{ml.machine\_memory=16723513344, xpack.installed=true, ml.max\_open\_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
> [2020-03-17T16:42:04,286][WARN][o.e.n.Node] [elasticsearch-node-1] timed out while waiting for initial discovery state - timeout: 30s
> [2020-03-17T16:42:04,288][WARN][o.e.c.c.ClusterFormationFailureHelper] [elasticsearch-node-1] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial\_master\_nodes] is empty on this node: have discovered [{elasticsearch-node-1}{1g6-SPfbTHi0eRfjXuLYLg}{pPs6OInqSP-igVsXUSnOIw}{127.0.0.1}{127.0.0.1:9300}{dilm}{ml.machine\_memory=16723513344, xpack.installed=true, ml.max\_open\_jobs=20}]; discovery will continue using from hosts providers and [{elasticsearch-node-1}{1g6-SPfbTHi0eRfjXuLYLg}{pPs6OInqSP-igVsXUSnOIw}{127.0.0.1}{127.0.0.1:9300}{dilm}{ml.machine\_memory=16723513344, xpack.installed=true, ml.max\_open\_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
> [2020-03-17T16:42:04,487][INFO][o.e.h.AbstractHttpServerTransport] [elasticsearch-node-1] publish\_address {127.0.0.1:9200}, bound\_addresses {127.0.0.1:9200}
> [2020-03-17T16:42:04,488][INFO][o.e.n.Node] [elasticsearch-node-1] started
> [2020-03-17T16:42:06,109][DEBUG][o.e.a.s.m.TransportMasterNodeAction] [elasticsearch-node-1] no known master node, scheduling a retry
> [2020-03-17T16:42:06,962][DEBUG][o.e.a.s.m.TransportMasterNodeAction] [elasticsearch-node-1] no known master node, scheduling a retry
> [2020-03-17T16:42:06,963][DEBUG][o.e.a.s.m.TransportMasterNodeAction] [elasticsearch-node-1] no known master node, scheduling a retry
My elasticsearch.yml has the below mentioned data:
> cluster.name: elk-ISSI
> node.name: elasticsearch-node-1
> network.host: 127.0.0.1
> discovery.zen.ping.unicast.hosts: 127.0.0.1
Can anyone please help me with the fix?
---
### Author:  [@AshokBachchan](https://discuss.elastic.co/u/AshokBachchan)
#### Post date: [March 17, 2020, 11:28am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/2 "2020-03-17T11:28:41Z")
**Hello Ankit,**
How many nodes you have for the cluster??
can you share **elasticsearch.yml** parameters from all nodes. so that I can help you on this.
---
### Author:  [@ankitagarwal10k](https://discuss.elastic.co/u/ankitagarwal10k)
#### Post date: [March 17, 2020, 11:30am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/3 "2020-03-17T11:30:57Z")
I am running this locally on my Ubuntu machine and i have no idea of the number of nodes its considering.
Where can I find any info about it?
I have mentioned the data inside elasticsearch.yml file in the post
---
### Author:  [@AshokBachchan](https://discuss.elastic.co/u/AshokBachchan)
#### Post date: [March 17, 2020, 11:37am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/4 "2020-03-17T11:37:33Z")
Hello Ankit,
Try to add below parameters in **elasticsearch.yml**
cluster.name: "ELK Cluster"
node.name: "DATA-NODE\_1"
node.master: true
node.data: true
discovery.zen.ping.unicast.hosts: ["YOUR IP ADDRESS"]
discovery.zen.minimum\_master\_nodes: 1
path.data: "ANY PATH" **(ex: /opt/esdata/data)**
path.logs: "ANY PATH" **(ex: /opt/esdata/logs)**
network.host: YOUR IP ADDRESS
http.port: 9200
bootstrap.system\_call\_filter: false
---
### Author:  [@AshokBachchan](https://discuss.elastic.co/u/AshokBachchan)
#### Post date: [March 17, 2020, 11:39am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/5 "2020-03-17T11:39:10Z")
Hi,
Your not mentioned master node for this cluster, that's why your getting that errors.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [March 17, 2020, 11:48am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/6 "2020-03-17T11:48:40Z")
@AshokBachchan this is not good advice, sorry. You're recommending setting quite a few irrelevant and/or deprecated settings, and yet what you suggest will not fix the problem.
@ankitagarwal10k you should remove `network.host` and `discovery.zen.ping.unicast.hosts` from your `elasticsearch.yml` file so that it only contains:
```auto
cluster.name: elk-ISSI
node.name: elasticsearch-node-1
```
---
### Author:  [@ankitagarwal10k](https://discuss.elastic.co/u/ankitagarwal10k)
#### Post date: [March 17, 2020, 11:51am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/7 "2020-03-17T11:51:38Z")
So, out of all the settings which Ashok has mentioned, I should be removing the rest and only keeping the ones you have mentioned ?
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [March 17, 2020, 11:52am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/8 "2020-03-17T11:52:55Z")
> [@ankitagarwal10k](#):
>
> So, out of all the settings which Ashok has mentioned, I should be removing the rest and only keeping the ones you have mentioned ?
That's correct. Your original `elasticsearch.yml` file was almost good, except for those two extra settings.
---
### Author:  [@ankitagarwal10k](https://discuss.elastic.co/u/ankitagarwal10k)
#### Post date: [March 17, 2020, 11:52am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/9 "2020-03-17T11:52:57Z")
I tried with the below details and still facing the same issue:
cluster.name: "elk-ISSI"
node.name: "elasticsearch-node-1"
node.master: true
node.data: true
network.host: 127.0.0.1
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]
discovery.zen.minimum\_master\_nodes: 1
http.port: 9200
bootstrap.system\_call\_filter: false
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
---
### Author:  [@ankitagarwal10k](https://discuss.elastic.co/u/ankitagarwal10k)
#### Post date: [March 17, 2020, 11:54am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/10 "2020-03-17T11:54:35Z")
for the latest details which I have posted, please let me know the fields which I have to keep !!
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [March 17, 2020, 11:55am UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/11 "2020-03-17T11:55:39Z")
Your `elasticsearch.yml` file should **only** contain this:
```auto
cluster.name: elk-ISSI
node.name: elasticsearch-node-1
```
---
### Author:  [@ankitagarwal10k](https://discuss.elastic.co/u/ankitagarwal10k)
#### Post date: [March 17, 2020, 12:01pm UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/12 "2020-03-17T12:01:46Z")
Thanks David 🙂
it worked now..
the elasticsearch is working now but sadly the filebeat is not getting started now !
---
### Author:  [@AshokBachchan](https://discuss.elastic.co/u/AshokBachchan)
#### Post date: [March 17, 2020, 12:05pm UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/13 "2020-03-17T12:05:13Z")
Thanks David,
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [March 17, 2020, 12:19pm UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/14 "2020-03-17T12:19:10Z")
Probably best to open another thread in the [Beats forum](https://discuss.elastic.co/c/beats/28) for your Filebeat question.
---
### Author:  [@ankitagarwal10k](https://discuss.elastic.co/u/ankitagarwal10k)
#### Post date: [March 17, 2020, 12:30pm UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/15 "2020-03-17T12:30:57Z")
I figured it out..
There were some config issues in the filebeat.yml
fixed it and its working now
thanks again 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 14, 2020, 12:30pm UTC](https://discuss.elastic.co/t/issues-with-starting-elasticsearch/223913/16 "2020-04-14T12:30:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.