# Service elasticsearch start but not the ports

**URL:** <https://discuss.elastic.co/t/service-elasticsearch-start-but-not-the-ports/261292>\
**Category:** Elasticsearch\
**Created:** [January 15, 2021, 7:29pm UTC](https://discuss.elastic.co/t/service-elasticsearch-start-but-not-the-ports/261292 "2021-01-15T19:29:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Emiliano\_Baum](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emiliano_baum/32/5186_2.png) [@Emiliano\_Baum](https://discuss.elastic.co/u/Emiliano_Baum)\
**Post date:** [January 15, 2021, 7:29pm UTC](https://discuss.elastic.co/t/service-elasticsearch-start-but-not-the-ports/261292/1 "2021-01-15T19:29:09Z")

</div>

Hi ,  
I am struggling with a rare problem, the elasticsearch service starts but not the ports.  
I have been running a maintenance routine on my cluster and in two nodes I have the same problem, the elastic search service is running but I do not see ports 9200 and 9300. In one of them I had to reinstall because it had been poorly balanced, but now I want to find the root of the problem. This cluster has been working for about 3-4 years, and this is the first time I have had this problem.  
When i had not responses to my queries i run a netstat -ptan and indeed, the ports are neither listening nor waiting.  
In the syslog I only found the start and stop of the service, and in the elastic log only the information log.  
It looks like it's still initializing, but it's never taken this long.

 ![imagen](https://us1.discourse-cdn.com/elastic/original/3X/5/2/528a4ee59e63c076483938e8674a5c01a688a7bd.png) ![imagen](https://us1.discourse-cdn.com/elastic/original/3X/5/2/528a4ee59e63c076483938e8674a5c01a688a7bd.png)

 ![imagen](https://us1.discourse-cdn.com/elastic/original/3X/3/b/3b413bbcee32034f0414b3b3f3e528930b013294.png)

 ![imagen](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e88bed86faf43e6c38e3d229d4b13316b843676d.png)

My version of Elastic is 6.6.0, and all this work is to upgrade to 7.

Thanks in advance, emiliano

---

<div class="post-metadata">

**Author:** ![Emiliano\_Baum](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emiliano_baum/32/5186_2.png) [@Emiliano\_Baum](https://discuss.elastic.co/u/Emiliano_Baum)\
**Post date:** [January 16, 2021, 1:46pm UTC](https://discuss.elastic.co/t/service-elasticsearch-start-but-not-the-ports/261292/2 "2021-01-16T13:46:51Z")

</div>

Eventually the node starts fine and joined the cluster without issues, but I don't understand why it took so long.  
The only warning found is the GC mapping error, but I understand that it is normal ...

---

<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:** [January 16, 2021, 11:17pm UTC](https://discuss.elastic.co/t/service-elasticsearch-start-but-not-the-ports/261292/3 "2021-01-16T23:17:36Z")

</div>

Please don't post pictures of text, they are difficult to read, impossible to search and replicate (if it's code), and some people may not be even able to see them 🙂

---

<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:** [February 13, 2021, 11:17pm UTC](https://discuss.elastic.co/t/service-elasticsearch-start-but-not-the-ports/261292/4 "2021-02-13T23:17:48Z")

</div>

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