Issues with starting elasticsearch

Elastic Stack Elasticsearch
1

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?

2

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.

3

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

4

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

5

Hi,

Your not mentioned master node for this cluster, that's why your getting that errors.

6

@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:

cluster.name: elk-ISSI
node.name: elasticsearch-node-1
7

So, out of all the settings which Ashok has mentioned, I should be removing the rest and only keeping the ones you have mentioned ?

8

That's correct. Your original elasticsearch.yml file was almost good, except for those two extra settings.

9

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

10

for the latest details which I have posted, please let me know the fields which I have to keep !!

11

Your elasticsearch.yml file should only contain this:

cluster.name: elk-ISSI
node.name: elasticsearch-node-1
12

Thanks David :slight_smile:

it worked now..
the elasticsearch is working now but sadly the filebeat is not getting started now !

13

Thanks David,

14

Probably best to open another thread in the Beats forum for your Filebeat question.

15

I figured it out..
There were some config issues in the filebeat.yml
fixed it and its working now

thanks again :slight_smile:

1 Like
16

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