Elastic port is getting changed after starting of services

(TheRebel) #1

Hi All,
I am getting issue of not enough master discovered during pinging. Here I am not able to understand that although Elastic is binding to 9500 port after start ("publish_address {}, bound_addresses {[::]:9500}") later it is getting changed to 9400 which is being used for http port ("publish_address {}, bound_addresses {[::]:9400}"). Please see the console snapshot given below and please help me because since long I am struggling with this issue not able to figure out what is the root cause or am I missing something.

[2018-09-10T14:56:25,142][INFO ][o.e.n.Node ] [linsee1] starting ...
[2018-09-10T14:56:25,277][INFO ][o.e.t.TransportService ] [linsee1] publish_address {}, bound_addresses {[::]:9500}
[2018-09-10T14:56:55,304][WARN ][o.e.n.Node ] [linsee1] timed out while waiting for initial discovery state - timeout: 30s
[2018-09-10T14:56:55,322][INFO ][o.e.x.s.t.n.SecurityNetty4HttpServerTransport] [linsee1] publish_address {}, bound_addresses {[::]:9400}
[2018-09-10T14:56:55,323][INFO ][o.e.n.Node ] [linsee1] started
[2018-09-10T14:57:13,334][WARN ][o.e.d.z.ZenDiscovery ] [linsee1] failed to connect to master [{master}{OcBKCmBZQy2nZvFoaG7p7A}{9l6b5DlVRPm-3FlKP0ZNAA}{}{}{ml.machine_memory=25284042752, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true}], retrying...
org.elasticsearch.transport.ConnectTransportException: [master][] connect_timeout[30s]

(Ryan Ernst) #2

9400 here is the port for secure transport (used for inter node communication), 9500 here is the port for https (rest api).

(system) #3

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