# Brand new master doesn't join cluster bootstrap error **URL:** \ **Category:** Elasticsearch\ **Created:** [January 5, 2023, 5:07pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567 "2023-01-05T17:07:32Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\ **Post date:** [January 5, 2023, 5:07pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/1 "2023-01-05T17:07:32Z")
Hi, We have a 7.10.2 cluster with multiple data-only nodes and 3 master-only nodes. We wiped one of the 3 masters clean (reinstall), and now it refuses to join the cluster: ```auto 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 [{node0008.example.com}{8ITgJeCmTCOqah6b_kxMDQ}{aGmuukVWTx6PzBlxPp0oaA}{10.10.239.8}{10.10.239.8:9300}{m}]; discovery will continue using [127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, 127.0.0.1:9305, [::1]:9300, [::1]:9301, [::1]:9302, [::1]:9303, [::1]:9304, [::1]:9305, [2010:660:5009:84:10:10:239:8]:9300, 10.10.239.53:9300, [2010:660:5009:84:10:10:239:53]:9300, 10.10.234.11:9300, [2010:660:5009:304:10:10:234:11]:9300, 10.10.235.58:9300, [2010:660:5009:304:10:10:235:58]:9300, 10.10.239.135:9300, [2010:660:5009:84:10:10:239:153]:9300, 10.10.234.4:9300, [2010:660:5009:304:10:10:234:4]:9300, 10.10.234.23:9300, [2010:660:5009:304:10:10:234:23]:9300, 10.10.234.115:9300, [2010:660:5009:304:10:10:234:115]:9300, 10.10.234.114:9300, [2010:660:5009:304:10:10:234:114]:9300, 10.10.234.129:9300, [2010:660:5009:304:10:10:234:129]:9300] from hosts providers and [{node0008.example.com}{8ITgJeCmTCOqah6b_kxMDQ}{aGmuukVWTx6PzBlxPp0oaA}{10.10.239.8}{10.10.239.8:9300}{m}] from last-known cluster state; node term 0, last-accepted version 0 in term 0 ``` I tried with and without the `cluster.initial_master_nodes` setting (specifying all 3 master nodes). ---
**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:** [January 5, 2023, 5:22pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/2 "2023-01-05T17:22:33Z")
Looks like a [discovery problem](https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-troubleshooting.html), but 7.10.2 is very old (long past [EOL](https://www.elastic.co/support/eol)) and newer versions have much better support for troubleshooting this kind of thing so I recommend you upgrade ASAP. ---
**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\ **Post date:** [January 5, 2023, 5:33pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/3 "2023-01-05T17:33:50Z")
Yes, of course. But I'd rather not upgrade anything until I'm out of the water. What do you suggest doing using 7.10.2 ? ---
**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:** [January 5, 2023, 5:55pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/4 "2023-01-05T17:55:22Z")
I don't remember exactly how 7.10.2 behaves in this situation, but hopefully there's something in the logs to help. Also double-check your discovery config and inter-node connectivity. ---
**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\ **Post date:** [January 5, 2023, 6:26pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/5 "2023-01-05T18:26:27Z")
I'm using `discovery.seed_providers: file` and the file `unicast_hosts.txt` contains a list of all data and master nodes ---
**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\ **Post date:** [January 5, 2023, 6:27pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/6 "2023-01-05T18:27:36Z")
There is no other message in the node's logfile ---
**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:** [January 5, 2023, 8:06pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/7 "2023-01-05T20:06:40Z")
Sharing your logs and config would be helpful, as otherwise we are just guessing. ---
**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\ **Post date:** [January 6, 2023, 8:23am UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/8 "2023-01-06T08:23:58Z")
The only other log entries I get are: ```auto Exception during establishing a SSL connection: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure exception caught on transport layer [Netty4TcpChannel{localAddress=0.0.0.0/0.0.0.0:42374, remoteAddress=null}], closing connection ``` Here's our config: ```auto action: destructive_requires_name: true bootstrap: memory_lock: true cluster: remote: connect: false network: host: - 10.10.239.8 - 127.0.0.1 path: repo: - /var/lib/elasticsearch-backup discovery.seed_providers: file cluster.name: foo node.name: node0008.example.com path.logs: /var/log/elasticsearch path.data: /var/lib/elasticsearch node.data: False node.master: True node.ingest: False cluster.initial_master_nodes: - node0008.example.com - node0053.example.com - node0311.example.com network.publish_host: 10.10.239.8 ``` The `unicast_hosts.txt` file: ```auto node0008.example.com node0053.example.com node0311.example.com node0614.example.com node0135.example.com node0304.example.com node0323.example.com node0415.example.com node0414.example.com node0429.example.com ``` ---
**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\ **Post date:** [January 6, 2023, 8:25am UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/9 "2023-01-06T08:25:27Z")
I just tried adding another master node (the fourth one), and that one joined the cluster with no issues. Is it possible the one that got reinstalled has got some stale config in the cluster ? ---
**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:** [January 6, 2023, 10:27pm UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/10 "2023-01-06T22:27:31Z")
Please share your logs, not just an excerpt. ---
**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\ **Post date:** [January 9, 2023, 9:48am UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/11 "2023-01-09T09:48:36Z")
Thanks for trying to help and requesting I share the full logs. While there is no other clue therein than the ones I already published, it did trigger me to pursue the root cause of the SSL Exceptions, which turned out to be the reason the node refused to join the cluster. The root cause was unmatched X509 certificate and key. Thanks again for your help ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 6, 2023, 9:49am UTC](https://discuss.elastic.co/t/brand-new-master-doesnt-join-cluster-bootstrap-error/322567/12 "2023-02-06T09:49:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.