# \[WARN \]\[o.e.c.c.ClusterFormationFailureHelper\] \[node1\] master not discovered yet, this node has not previously joined a bootstrapped cluster

**URL:** <https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267>\
**Category:** Elasticsearch\
**Created:** [April 4, 2023, 3:47am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267 "2023-04-04T03:47:55Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raghulvishal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raghulvishal/32/117550_2.png) [@Raghulvishal](https://discuss.elastic.co/u/Raghulvishal)\
**Post date:** [April 4, 2023, 3:47am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/1 "2023-04-04T03:47:55Z")

</div>

Hi Team,  
I am using ES 8.6 version and configured 3 nodes,while starting the node i'am getting master not discovered yet exception.  
This is my elastic .yml given below.

```auto
cluster.name: es-8_6
node.name: node1
path.data: /home/raghul/8.6/w1/data
path.logs: /home/raghul/8.6/w1/logs
network.host: 
cluster.initial_master_nodes: ["node1", "node2", "node3"]
discovery.seed_hosts: ["",""]
node.roles: [data, master]
http.port: 
readiness.port: 
xpack.security.enabled: false
xpack.security.transport.ssl.enabled: false

```

---

<div class="post-metadata">

**Author:** ![Raghulvishal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raghulvishal/32/117550_2.png) [@Raghulvishal](https://discuss.elastic.co/u/Raghulvishal)\
**Post date:** [April 4, 2023, 3:48am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/2 "2023-04-04T03:48:40Z")

</div>

can you give a solution for this exception.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 4, 2023, 3:49am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/3 "2023-04-04T03:49:02Z")

</div>

What do your logs show?

Also please format your code/logs/config using the `</>` button, or markdown style back ticks. It helps to make things easy to read which helps us help you 🙂

---

<div class="post-metadata">

**Author:** ![Raghulvishal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raghulvishal/32/117550_2.png) [@Raghulvishal](https://discuss.elastic.co/u/Raghulvishal)\
**Post date:** [April 4, 2023, 4:02am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/4 "2023-04-04T04:02:09Z")

</div>

```auto
[2023-04-04T08:58:52,078][INFO][o.e.t.n.NettyAllocator] [node1] creating NettyAllocator with the following configs: [name=unpooled, suggested_max_allocation_size=1mb, factors={es.unsafe.use_unpooled_allocator=null, g1gc_enabled=true, g1gc_region_size=4mb, heap_size=512mb}]
[2023-04-04T08:58:52,097][INFO][o.e.i.r.RecoverySettings] [node1] using rate limit [40mb] with [default=40mb, read=0b, write=0b, max=0b]
[2023-04-04T08:58:52,132][INFO][o.e.d.DiscoveryModule] [node1] using discovery type [multi-node] and seed hosts providers [settings]
[2023-04-04T08:58:53,129][INFO][o.e.n.Node] [node1] initialized
[2023-04-04T08:58:53,130][INFO][o.e.n.Node] [node1] starting ...
[2023-04-04T08:58:53,154][INFO][o.e.x.s.c.f.PersistentCache] [node1] persistent cache index loaded
[2023-04-04T08:58:53,156][INFO][o.e.x.d.l.DeprecationIndexingComponent] [node1] deprecation component started
[2023-04-04T08:58:53,251][INFO][o.e.t.TransportService] [node1] publish_address {<ip>:9300}, bound_addresses {<ip>:9300}
[2023-04-04T08:58:53,405][INFO][o.e.b.BootstrapChecks] [node1] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2023-04-04T08:58:53,408][INFO][o.e.c.c.ClusterBootstrapService] [node1] this node has not joined a bootstrapped cluster yet; [cluster.initial_master_nodes] is set to [node1, node2, node3]
[2023-04-04T08:59:03,419][WARN][o.e.c.c.ClusterFormationFailureHelper] [node1] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [node1, node2, node3] to bootstrap a cluster: have discovered [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}]; discovery will continue using [<ip>:9271, <ip>:9272] from hosts providers and [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2023-04-04T08:59:13,423][WARN][o.e.c.c.ClusterFormationFailureHelper] [node1] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [node1, node2, node3] to bootstrap a cluster: have discovered [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}]; discovery will continue using [<ip>:9271, <ip>:9272] from hosts providers and [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2023-04-04T08:59:23,420][WARN][o.e.n.Node] [node1] timed out while waiting for initial discovery state - timeout: 30s
[2023-04-04T08:59:23,424][WARN][o.e.c.c.ClusterFormationFailureHelper] [node1] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [node1, node2, node3] to bootstrap a cluster: have discovered [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}]; discovery will continue using [<ip>:9271, <ip>:9272] from hosts providers and [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2023-04-04T08:59:23,425][INFO][o.e.h.AbstractHttpServerTransport] [node1] publish_address {<ip>:9230}, bound_addresses {<ip>:9230}
[2023-04-04T08:59:23,426][INFO][o.e.n.Node] [node1] started {node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}{xpack.installed=true}
[2023-04-04T08:59:28,878][INFO][o.e.x.m.p.NativeController] [node1] Native controller process has stopped - no new native processes can be started
[2023-04-04T08:59:28,879][INFO][o.e.n.Node] [node1] stopping ...
[2023-04-04T08:59:28,883][INFO][o.e.r.ReadinessService] [node1] stopping readiness service on channel None
[2023-04-04T08:59:28,884][INFO][o.e.r.ReadinessService] [node1] readiness service stopped
[2023-04-04T08:59:28,886][INFO][o.e.x.w.WatcherService] [node1] stopping watch service, reason [shutdown initiated]
[2023-04-04T08:59:28,887][INFO][o.e.x.w.WatcherLifeCycleService] [node1] watcher has stopped and shutdown
[2023-04-04T08:59:29,391][INFO][o.e.n.Node] [node1] stopped
[2023-04-04T08:59:29,392][INFO][o.e.n.Node] [node1] closing ...
[2023-04-04T08:59:29,403][INFO][o.e.n.Node] [node1] closed

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 4, 2023, 4:05am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/5 "2023-04-04T04:05:44Z")

</div>

Can you curl the master node from that one to check connectivity?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 4, 2023, 4:11am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/6 "2023-04-04T04:11:28Z")

</div>

> [@Raghulvishal](#):
>
> `discovery will continue using [<ip>:9271, <ip>:9272]`

These port numbers look strange. How have you configured `discovery.seed_hosts`?

Are there any settings you have left out from what you posted earlier?

---

<div class="post-metadata">

**Author:** ![Raghulvishal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raghulvishal/32/117550_2.png) [@Raghulvishal](https://discuss.elastic.co/u/Raghulvishal)\
**Post date:** [April 4, 2023, 4:20am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/7 "2023-04-04T04:20:11Z")

</div>

but,I have same yml configuration in 7.17, it's working.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 4, 2023, 5:02am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/8 "2023-04-04T05:02:58Z")

</div>

Elasticsearch communicates internally over port `9300`, not `9200`. It looks like you may be using custom HTTP port numbers and I am wondering if you may have incorrectly configured these in `discovery.seed_hosts` as ports in the `9200`-`9299` range are showing up in discovery..

Please share the full config.

---

<div class="post-metadata">

**Author:** ![Raghulvishal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raghulvishal/32/117550_2.png) [@Raghulvishal](https://discuss.elastic.co/u/Raghulvishal)\
**Post date:** [April 4, 2023, 7:24am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/9 "2023-04-04T07:24:25Z")

</div>

For discovery.seed\_hosts i have used 9300, it show's again same error.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 4, 2023, 7:56am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/10 "2023-04-04T07:56:16Z")

</div>

Why do the ports i mentioned then show up in the logs you posted?

If you can not share real logs and config I do not think i can help much.

---

<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:** [May 2, 2023, 7:56am UTC](https://discuss.elastic.co/t/warn-o-e-c-c-clusterformationfailurehelper-node1-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-cluster/329267/11 "2023-05-02T07:56:33Z")

</div>

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