# Elastic port is getting changed after starting of services

**URL:** <https://discuss.elastic.co/t/elastic-port-is-getting-changed-after-starting-of-services/147932>\
**Category:** Elasticsearch\
**Created:** [September 10, 2018, 9:47am UTC](https://discuss.elastic.co/t/elastic-port-is-getting-changed-after-starting-of-services/147932 "2018-09-10T09:47:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dhananjay88](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@dhananjay88](https://discuss.elastic.co/u/dhananjay88)\
**Post date:** [September 10, 2018, 9:47am UTC](https://discuss.elastic.co/t/elastic-port-is-getting-changed-after-starting-of-services/147932/1 "2018-09-10T09:47:27Z")

</div>

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 {10.159.252.99:9500}, bound\_addresses {[::]:9500}") later it is getting changed to 9400 which is being used for http port ("publish\_address {10.159.252.99:9400}, 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 {10.159.252.99:9500}, 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 {10.159.252.99:9400}, 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}{192.168.0.48}{192.168.0.48:9500}{ml.machine\_memory=25284042752, ml.max\_open\_jobs=20, xpack.installed=true, ml.enabled=true}], retrying...  
org.elasticsearch.transport.ConnectTransportException: [master][192.168.0.48:9500] connect\_timeout[30s]

---

<div class="post-metadata">

**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\
**Post date:** [September 14, 2018, 12:05am UTC](https://discuss.elastic.co/t/elastic-port-is-getting-changed-after-starting-of-services/147932/2 "2018-09-14T00:05:59Z")

</div>

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

---

<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:** [October 12, 2018, 12:06am UTC](https://discuss.elastic.co/t/elastic-port-is-getting-changed-after-starting-of-services/147932/3 "2018-10-12T00:06:01Z")

</div>

Closed on October 12, 2018, 12:06am UTC

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