# ES node unable to start again

**URL:** <https://discuss.elastic.co/t/es-node-unable-to-start-again/22437>\
**Category:** Elasticsearch\
**Created:** [February 27, 2015, 6:24pm UTC](https://discuss.elastic.co/t/es-node-unable-to-start-again/22437 "2015-02-27T18:24:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pfigue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pfigue/32/865_2.png) [@pfigue](https://discuss.elastic.co/u/pfigue)\
**Post date:** [February 27, 2015, 6:24pm UTC](https://discuss.elastic.co/t/es-node-unable-to-start-again/22437/1 "2015-02-27T18:24:56Z")

</div>

Hi,

I have a node which is unable to connect to other nodes of the cluster  
(probably because they are running out of file descriptors).

I try to shutdown that node with

# service elasticsearch stop

- Stopping Elasticsearch Server  
...done.

But I can still see the process if I do:

ps aux | grep elast

And actually in the ElasticSearch log there is no log line related to the  
shutdown.

I can wait several minutes, but still the process stays there.

If I kill it, either with SIGTERM or SIGKILL and then I try to run ES  
again, I get:

# /usr/share/elasticsearch/bin/elasticsearch -p /var/run/elasticsearch.pid

--default.config=/etc/elasticsearch/elasticsearch.yml  
--default.path.home=/usr/share/elasticsearch  
--default.path.log/var/log/elasticsearch  
--default.path.data=/var/lib/elasticsearch  
--default.path.work=/tmp/elasticsearch  
--default.path.conf=/etc/elasticsearch -Des.max-open-files=true  
log4j:WARN No such property [datePattern] in  
org.apache.log4j.RollingFileAppender.  
log4j:ERROR Could not find value for key  
log4j.appender.index\_indexing\_slow\_log\_file  
log4j:ERROR Could not instantiate appender named  
"index\_indexing\_slow\_log\_file".  
log4j:ERROR Could not find value for key  
log4j.appender.index\_search\_slow\_log\_file  
log4j:ERROR Could not instantiate appender named  
"index\_search\_slow\_log\_file".

and the process stucks there.

If I reboot the instance I arrive to the same point. I have to terminate  
that instance and create a new one, reinstalling ES.

It is ES 1.4.4 on Ubuntu 14.04 amd64 kernel 3.13.0-44-generic.

For me it seems like ES in a loop trying to discover a master, and it is  
unresponsive to anything else. I didn't try to shut it down via the  
Shutdown API.

Thanks for any help.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/816dc2a3-0bf3-46cf-9ecf-7f1c77f004a9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/816dc2a3-0bf3-46cf-9ecf-7f1c77f004a9%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:29am UTC](https://discuss.elastic.co/t/es-node-unable-to-start-again/22437/2 "2017-07-06T00:29:26Z")

</div>