# Could not active ES 6.3 on transport host

**URL:** <https://discuss.elastic.co/t/could-not-active-es-6-3-on-transport-host/144320>\
**Category:** Elasticsearch\
**Created:** [August 14, 2018, 10:15am UTC](https://discuss.elastic.co/t/could-not-active-es-6-3-on-transport-host/144320 "2018-08-14T10:15:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mahendra\_Shinde](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Mahendra\_Shinde](https://discuss.elastic.co/u/Mahendra_Shinde)\
**Post date:** [August 14, 2018, 10:15am UTC](https://discuss.elastic.co/t/could-not-active-es-6-3-on-transport-host/144320/1 "2018-08-14T10:15:25Z")

</div>

My elasticsearch.yml contains

```auto
network.host: 172.16.0.238
transport.host: 172.16.0.238
discovery.zen.ping.unicast.hosts: ["172.16.0.238"]
discovery.zen.minimum_master_nodes: 2
http.port: 9200
transport.tcp.port: 9300

```

I have X-pack activated and user id password set for elastic user.  
Same setup was working with localhost.  
But error after starting ES with host addresses

[2018-08-14T15:43:49,912][INFO][o.e.x.s.a.AuthenticationService] [0ct1zNX] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]  
[2018-08-14T15:43:49,917][INFO][o.e.x.s.a.AuthenticationService] [0ct1zNX] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]  
[2018-08-14T15:43:49,943][INFO][o.e.x.s.a.AuthenticationService] [0ct1zNX] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]  
[2018-08-14T15:43:51,118][WARN][o.e.d.z.ZenDiscovery] [0ct1zNX] not enough master nodes discovered during pinging (found [[Candidate{node={0ct1zNX}{0ct1zNX6RnyAU1MjWbQHFg}{gKBn1RDdT\_6f\_rnPzfiRjg}{172.16.0.238}{172.16.0.238:9300}{ml.machine\_memory=16717053952, xpack.installed=true, ml.max\_open\_jobs=20, ml.enabled=true}, clusterStateVersion=-1}]], but needed [2]), pinging again  
[2018-08-14T15:43:51,899][INFO][o.e.x.s.a.AuthenticationService] [0ct1zNX] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]  
[2018-08-14T15:43:54,119][WARN][o.e.d.z.ZenDiscovery] [0ct1zNX] not enough master nodes discovered during pinging (found [[Candidate{node={0ct1zNX}{0ct1zNX6RnyAU1MjWbQHFg}{gKBn1RDdT\_6f\_rnPzfiRjg}{172.16.0.2

---

<div class="post-metadata">

**Author:** ![Mahendra\_Shinde](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Mahendra\_Shinde](https://discuss.elastic.co/u/Mahendra_Shinde)\
**Post date:** [August 14, 2018, 10:53am UTC](https://discuss.elastic.co/t/could-not-active-es-6-3-on-transport-host/144320/2 "2018-08-14T10:53:55Z")

</div>

Working with below settings

```auto
network.host: 172.16.0.238
transport.host: 172.16.0.238
discovery.zen.ping.unicast.hosts: ["172.16.0.238"]
discovery.zen.minimum_master_nodes: 1
http.port: 9200
transport.tcp.port: 9300

```

---

<div class="post-metadata">

**Author:** ![Jymit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jymit/32/45777_2.png) [@Jymit](https://discuss.elastic.co/u/Jymit)\
**Post date:** [August 16, 2018, 1:56am UTC](https://discuss.elastic.co/t/could-not-active-es-6-3-on-transport-host/144320/3 "2018-08-16T01:56:59Z")

</div>

`[o.e.d.z.ZenDiscovery] [0ct1zNX] not enough master nodes discovered during pinging`  
So the solution was that you had minimum\_master\_nodes set to 2 when it should of been 1. 👍

---

<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:** [September 13, 2018, 2:11am UTC](https://discuss.elastic.co/t/could-not-active-es-6-3-on-transport-host/144320/4 "2018-09-13T02:11:34Z")

</div>

Closed on September 13, 2018, 2:11am UTC

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