# Elasticsearch not working after Elasticsearch upgrade from 6.7 to 7.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 2, 2019, 9:21am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322 "2019-05-02T09:21:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\ **Post date:** [May 2, 2019, 9:21am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/1 "2019-05-02T09:21:59Z")
Hi Guys, After i upgraded from 6.7 to 7.0, i'm having the issues to startup my elasticsearch and cluster, Anyone can assist me? I don't know what's wrong. Is it syntax errors? Below are my config and error logs, elasticsearch.yml [node 1] ``` path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch xpack.security.enabled: false bootstrap.memory_lock: true cluster.name: z3-elk.stack node.name: z3elk-01 network.host: 10.3.3.41 http.port: 9200 node.master: true node.data: true discovery.zen.ping.unicast.hosts: ["10.3.3.41", "10.3.3.42"] discovery.zen.minimum_master_nodes: 1 ``` elasticsearch.yml [node 2] ``` path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch xpack.security.enabled: false bootstrap.memory_lock: true cluster.name: z3-elk.stack node.name: z3elk-02 network.host: 10.3.3.42 http.port: 9200 node.master: false node.data: true discovery.zen.ping.unicast.hosts: ["10.3.3.41", "10.3.3.42"] ``` elasticsearch cluster logs, ``` [2019-05-02T16:45:37,606][INFO][o.e.b.BootstrapChecks] [z3elk-01] bound or publishing to a non-loopback address, enforcing bootstrap checks [2019-05-02T16:45:47,623][WARN][o.e.c.c.ClusterFormationFailureHelper] [z3elk-01] 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 []; discovery will continue using [10.3.3.42:9300] from hosts providers and [{z3elk-01}{n-fNTnCQS_eTLm_W4P5Rag}{x-h4DWxCS_ePNiEwdnPnbg}{10.3.3.41}{10.3.3.41:9300}{ml.machine_memory=8203431936, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0 [2019-05-02T16:45:57,625][WARN][o.e.c.c.ClusterFormationFailureHelper] [z3elk-01] 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 []; discovery will continue using [10.3.3.42:9300] from hosts providers and [{z3elk-01}{n-fNTnCQS_eTLm_W4P5Rag}{x-h4DWxCS_ePNiEwdnPnbg}{10.3.3.41}{10.3.3.41:9300}{ml.machine_memory=8203431936, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0 [2019-05-02T16:46:07,626][WARN][o.e.c.c.ClusterFormationFailureHelper] [z3elk-01] 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 []; discovery will continue using [10.3.3.42:9300] from hosts providers and [{z3elk-01}{n-fNTnCQS_eTLm_W4P5Rag}{x-h4DWxCS_ePNiEwdnPnbg}{10.3.3.41}{10.3.3.41:9300}{ml.machine_memory=8203431936, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0 [2019-05-02T16:46:07,642][WARN][o.e.n.Node] [z3elk-01] timed out while waiting for initial discovery state - timeout: 30s [2019-05-02T16:46:07,648][INFO][o.e.h.AbstractHttpServerTransport] [z3elk-01] publish_address {10.3.3.41:9200}, bound_addresses {10.3.3.41:9200} [2019-05-02T16:46:07,649][INFO][o.e.n.Node] [z3elk-01] started [2019-05-02T16:50:47,560][DEBUG][o.e.a.a.i.t.g.TransportGetIndexTemplatesAction] [z3elk-01] no known master node, scheduling a retry [2019-05-02T16:50:47,659][WARN][o.e.c.c.ClusterFormationFailureHelper] [z3elk-01] 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 []; discovery will continue using [10.3.3.42:9300] from hosts providers and [{z3elk-01}{n-fNTnCQS_eTLm_W4P5Rag}{x-h4DWxCS_ePNiEwdnPnbg}{10.3.3.41}{10.3.3.41:9300}{ml.machine_memory=8203431936, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0 [2019-05-02T16:50:57,660][WARN][o.e.c.c.ClusterFormationFailureHelper] [z3elk-01] 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 []; discovery will continue using [10.3.3.42:9300] from hosts providers and [{z3elk-01}{n-fNTnCQS_eTLm_W4P5Rag}{x-h4DWxCS_ePNiEwdnPnbg}{10.3.3.41}{10.3.3.41:9300}{ml.machine_memory=8203431936, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0 [2019-05-02T16:51:07,661][WARN][o.e.c.c.ClusterFormationFailureHelper] [z3elk-01] 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 []; discovery will continue using [10.3.3.42:9300] from hosts providers and [{z3elk-01}{n-fNTnCQS_eTLm_W4P5Rag}{x-h4DWxCS_ePNiEwdnPnbg}{10.3.3.41}{10.3.3.41:9300}{ml.machine_memory=8203431936, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0 ``` ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 2, 2019, 10:35am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/2 "2019-05-02T10:35:34Z")
From the [docs on upgrades](https://www.elastic.co/guide/en/elasticsearch/reference/current/restart-upgrade.html): > If upgrading from a 6.x cluster, you must [configure cluster bootstrapping](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-bootstrap-cluster.html) by setting the `cluster.initial_master_nodes` setting. It looks like you have not done so: > [@wcpoon](#): > > `[cluster.initial_master_nodes] is empty on this node` ---
**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\ **Post date:** [May 3, 2019, 4:00am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/3 "2019-05-03T04:00:15Z")
Hi David, Is it i need to configure the cluster.initial\_master\_nodes in elasticsearch.yml? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 3, 2019, 4:17am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/4 "2019-05-03T04:17:22Z")
Yes, that'd solve it. ---
**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\ **Post date:** [May 3, 2019, 4:29am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/5 "2019-05-03T04:29:16Z")
Is running fine now.. I follow this link > **[elasticsearch .yml Changes (7.0)](https://linuxacademy.com/community/posts/show/topic/36639-elasticsearch-yml-changes-70)** > > So I've been following along with Myles in the Elastic Stack Essentials course videos, and if anyone else has been also, a minor head's up: In the "Create a Multi-Node Cluster" video, Myles is using Elasticsearch 6.7 and when editing the first data... ---
**Author:** ![wcpoon](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@wcpoon](https://discuss.elastic.co/u/wcpoon)\ **Post date:** [May 3, 2019, 5:56am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/6 "2019-05-03T05:56:20Z")
Hi, in elasticsearch 7.0, still need this configuration? ``` discovery.zen.ping.unicast.hosts: ["10.3.3.41", "10.3.3.42"] discovery.zen.minimum_master_nodes: 1 ``` ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 3, 2019, 6:28am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/7 "2019-05-03T06:28:33Z")
In 7.0, you should use `discovery.seed_hosts` instead of `discovery.zen.ping.unicast.hosts`. `discovery.zen.minimum_master_nodes` can be removed in 7.0. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 31, 2019, 6:28am UTC](https://discuss.elastic.co/t/elasticsearch-not-working-after-elasticsearch-upgrade-from-6-7-to-7-0/179322/8 "2019-05-31T06:28:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.