Could not active ES 6.3 on transport host

Elastic Stack Elasticsearch
1

My elasticsearch.yml contains

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

2

Working with below settings

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
3

[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. :+1:

4

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