# Master not found on ES Alpha5

**URL:** <https://discuss.elastic.co/t/master-not-found-on-es-alpha5/60913>\
**Category:** Elasticsearch\
**Created:** [September 19, 2016, 4:15pm UTC](https://discuss.elastic.co/t/master-not-found-on-es-alpha5/60913 "2016-09-19T16:15:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mad\_min](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mad_min/32/5964_2.png) [@mad\_min](https://discuss.elastic.co/u/mad_min)\
**Post date:** [September 19, 2016, 4:15pm UTC](https://discuss.elastic.co/t/master-not-found-on-es-alpha5/60913/1 "2016-09-19T16:15:42Z")

</div>

Hi List,

I am trying to bring up a prototype cluster using ES5Alpha5. The node config in config/elasticsearch.yml is (pretty much ported from my prod ES2 config except where I was asked to remove stuff when ES5 was coming up):

```
cluster.name: <name>
node.name: bxb-sln-vm140
path.data: /home/xxx/elastic-data
path.logs: /home/xxx/elastic-logs

node.data: true
node.master: true
http.enabled: true

discovery.zen.ping.unicast.hosts: ["10.86.207.26:9300", "10.86.206.22:9300", "10.86.196.235:9300"]
discovery.zen.minimum_master_nodes: 2
discovery.zen.fd.ping_timeout: 30s

```

This is the output I am seeing on the logs:

```
[2016-09-15 11:00:13,854][INFO][transport] [bxb-sln-vm140] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}
[2016-09-15 11:00:43,880][WARN][node] [bxb-sln-vm140] timed out while waiting for initial discovery state - timeout: 30s
[2016-09-15 11:00:43,895][INFO][http] [bxb-sln-vm140] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200}
[2016-09-15 11:00:43,895][INFO][node] [bxb-sln-vm140] started

```

This is the other output I see:

```
curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'
{
  "error" : {
    "root_cause" : [
      {
        "type" : "master_not_discovered_exception",
        "reason" : null
      }
    ],
    "type" : "master_not_discovered_exception",
    "reason" : null
  },
  "status" : 503
}

```

Other FYI: I am kind of trying to move over my existing prod cluster to ES5 once its out of Alpha/Beta, is there any place that tracks all points to keep in mind when making the move? I already saw that I cannot specify shards and replicas on the .yml but instead through a POST (like!)

Thanks

---

<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:** [September 20, 2016, 1:44am UTC](https://discuss.elastic.co/t/master-not-found-on-es-alpha5/60913/2 "2016-09-20T01:44:10Z")

</div>

You need to set `network.host` - [https://www.elastic.co/guide/en/elasticsearch/reference/2.4/setup-configuration.html#settings](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/setup-configuration.html#settings)

---

<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:18pm UTC](https://discuss.elastic.co/t/master-not-found-on-es-alpha5/60913/3 "2017-07-05T22:18:57Z")

</div>