# Failed to send join request to master, no known master node

**URL:** <https://discuss.elastic.co/t/failed-to-send-join-request-to-master-no-known-master-node/60003>\
**Category:** Elasticsearch\
**Created:** [September 7, 2016, 3:20pm UTC](https://discuss.elastic.co/t/failed-to-send-join-request-to-master-no-known-master-node/60003 "2016-09-07T15:20:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stefanocog](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@stefanocog](https://discuss.elastic.co/u/stefanocog)\
**Post date:** [September 7, 2016, 3:20pm UTC](https://discuss.elastic.co/t/failed-to-send-join-request-to-master-no-known-master-node/60003/1 "2016-09-07T15:20:44Z")

</div>

Hi i have a cluster with 3 nodes and work perfectly since 3 months, today i have found the node 3 disconnect, i have restart elasticsearch without effect, the error is:

```
[2016-09-07 14:38:59,297][INFO][node] [es-node3] starting ...
[2016-09-07 14:38:59,393][INFO][transport] [es-node3] publish_address {ec2-52-208-xxx-11.eu-west-1.compute.amazonaws.com/10.1.200.190:9300}, bound_addresses {[::]:9300}
[2016-09-07 14:38:59,398][INFO][discovery] [es-node3] myz-es-cluster/RSBMKUfLQiCDo8zWLFDmWQ
[2016-09-07 14:39:29,401][WARN][discovery] [es-node3] waited for 30s and no initial state was set by the discovery
[2016-09-07 14:39:29,417][INFO][http] [es-node3] publish_address {ec2-52-208-xxx-11.eu-west-1.compute.amazonaws.com/10.1.200.190:9200}, bound_addresses {[::]:9200}
[2016-09-07 14:39:29,418][INFO][node] [es-node3] started
[2016-09-07 14:39:35,084][DEBUG][action.admin.indices.create] [es-node3] no known master node, scheduling a retry
[2016-09-07 14:39:35,135][DEBUG][action.admin.indices.create] [es-node3] no known master node, scheduling a retry
[2016-09-07 14:40:02,448][INFO][discovery.zen] [es-node3] failed to send join request to master [{es-node2}{1aFV4V3DRd65BMJJ_BhU1Q}{10.1.200.10}{10.1.200.10:9300}{master=true}], reason [ElasticsearchTimeoutException[Timeout waiting for task.]]
[2016-09-07 14:40:09,390][DEBUG][action.admin.indices.create] [es-node3] no known master node, scheduling a retry
[2016-09-07 14:40:09,390][DEBUG][action.admin.indices.create] [es-node3] no known master node, scheduling a retry

```

Node 1 and node 2 work, actually node 2 is a master, the config file of node 3 is:

```
cluster.name: es-cluster
node.name: es-node3
bootstrap.mlockall: true
discovery.zen.ping.unicast.hosts: ["ec2-52-208-xxx-11.eu-west-1.compute.amazonaws.com", "ec2-52-51-160-xxx.eu-west-1.compute.amazonaws.com", "ec2-52-208-xxx-163.eu-west-1.compute.amazonaws.com"]
discovery.zen.minimum_master_nodes: 2
discovery.zen.ping.multicast.enabled: false
node.master: true
node.data: true
network.bind_host: 0.0.0.0
network.publish_host: ec2-52-208-xxx-11.eu-west-1.compute.amazonaws.com

```

This config is the same for all nodes, only "network.publish\_host" is different, all node is in the same lan without firewall

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 9, 2016, 11:07am UTC](https://discuss.elastic.co/t/failed-to-send-join-request-to-master-no-known-master-node/60003/2 "2016-09-09T11:07:03Z")

</div>

Hey,

without more information, this looks more like a network/firewall problem. Can you reach the other nodes on port 9300 from that node (e.g. using `telnet` or `netcat`)? If that does not work, it is more likely a configuration issue.

--Alex

---

<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:** [July 5, 2017, 10:21pm UTC](https://discuss.elastic.co/t/failed-to-send-join-request-to-master-no-known-master-node/60003/3 "2017-07-05T22:21:36Z")

</div>