# Elasticsearch service often goes down or gets killed

**URL:** <https://discuss.elastic.co/t/elasticsearch-service-often-goes-down-or-gets-killed/23320>\
**Category:** Elasticsearch\
**Created:** [April 20, 2015, 12:13pm UTC](https://discuss.elastic.co/t/elasticsearch-service-often-goes-down-or-gets-killed/23320 "2015-04-20T12:13:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastien\_Vassaux](https://avatars.discourse-cdn.com/v4/letter/s/e95f7d/32.png) [@Sebastien\_Vassaux](https://discuss.elastic.co/u/Sebastien_Vassaux)\
**Post date:** [April 20, 2015, 12:13pm UTC](https://discuss.elastic.co/t/elasticsearch-service-often-goes-down-or-gets-killed/23320/1 "2015-04-20T12:13:02Z")

</div>

Hello!

My webserver is running ubuntu 14.10 with elasticsearch 1.5.0 and java  
1.7u55

For some reason,\* the elasticsearch service often goes down,\* resulting in  
my website not being available to my users anymore (using FOSElasticaBundle  
with symfony).

I am using systemctl to restart it automatically, but I would prefer a good  
fix once and for all. I feel the logs I have are not descriptive enough.  
Being pretty new to managing a server, I need some help.

Can someone help me figure out the reason for this failure ? What are the  
right files I can output here to better understand the issue ?

Thanks !

_My systemctl status gives :_

elasticsearch.service - ElasticSearch  
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled)  
Active: active (running) since Mon 2015-04-20 12:04:24 CEST; 1h 56min  
ago \<------------- Here it means restarted 1h56 ago. Why did it  
fail in the first place ?  
Main PID: 9120 (java)  
CGroup: /system.slice/elasticsearch.service  
└─9120 /usr/bin/java -Xms256m -Xmx1g -Djava.awt.headless=true  
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC  
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingO...

_In my journalctl, I have :_

Apr 18 18:56:19 [xx.ovh.net](http://xx.ovh.net) sshd[29397]: error: open /dev/tty failed - could  
not set controlling tty: Permission denied  
Apr 20 13:52:45 [xx.ovh.net](http://xx.ovh.net) sshd[9764]: error: open /dev/tty failed - could  
not set controlling tty: Permission denied

--  
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/f0f6e4d3-35f6-4d63-ab91-bf048332e467%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f0f6e4d3-35f6-4d63-ab91-bf048332e467%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [April 21, 2015, 8:31pm UTC](https://discuss.elastic.co/t/elasticsearch-service-often-goes-down-or-gets-killed/23320/2 "2015-04-21T20:31:33Z")

</div>

You need to monitor the cluster with something like Marvel, kopf or HQ to  
find out what is happening.  
ES may die if the cluster is overloaded (think OOM), but you should see  
something in the logs on that.

On 20 April 2015 at 22:13, Sébastien Vassaux [svassaux@gmail.com](mailto:svassaux@gmail.com) wrote:

> Hello!
> 
> My webserver is running ubuntu 14.10 with elasticsearch 1.5.0 and java  
> 1.7u55
> 
> For some reason,\* the elasticsearch service often goes down,\* resulting  
> in my website not being available to my users anymore (using  
> FOSElasticaBundle with symfony).
> 
> I am using systemctl to restart it automatically, but I would prefer a  
> good fix once and for all. I feel the logs I have are not descriptive  
> enough.  
> Being pretty new to managing a server, I need some help.
> 
> Can someone help me figure out the reason for this failure ? What are the  
> right files I can output here to better understand the issue ?
> 
> Thanks !
> 
> _My systemctl status gives :_
> 
> elasticsearch.service - Elasticsearch  
> Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled)  
> Active: active (running) since Mon 2015-04-20 12:04:24 CEST; 1h 56min  
> ago \<------------- Here it means restarted 1h56 ago. Why did it  
> fail in the first place ?  
> Main PID: 9120 (java)  
> CGroup: /system.slice/elasticsearch.service  
> └─9120 /usr/bin/java -Xms256m -Xmx1g -Djava.awt.headless=true  
> -XX:+UseParNewGC -XX:+UseConcMarkSweepGC  
> -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingO...
> 
> _In my journalctl, I have :_
> 
> Apr 18 18:56:19 [xx.ovh.net](http://xx.ovh.net) sshd[29397]: error: open /dev/tty failed -  
> could not set controlling tty: Permission denied  
> Apr 20 13:52:45 [xx.ovh.net](http://xx.ovh.net) sshd[9764]: error: open /dev/tty failed -  
> could not set controlling tty: Permission denied
> 
> --  
> 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/f0f6e4d3-35f6-4d63-ab91-bf048332e467%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f0f6e4d3-35f6-4d63-ab91-bf048332e467%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/f0f6e4d3-35f6-4d63-ab91-bf048332e467%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f0f6e4d3-35f6-4d63-ab91-bf048332e467%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEYi1X\_Yhe-0TQme5PY\_c\_7DfoXKGkyUZWeVjTiieokL9Wb8cA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_Yhe-0TQme5PY_c_7DfoXKGkyUZWeVjTiieokL9Wb8cA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Tony\_Chong\_2](https://avatars.discourse-cdn.com/v4/letter/t/db5fbb/32.png) [@Tony\_Chong\_2](https://discuss.elastic.co/u/Tony_Chong_2)\
**Post date:** [April 21, 2015, 9:43pm UTC](https://discuss.elastic.co/t/elasticsearch-service-often-goes-down-or-gets-killed/23320/3 "2015-04-21T21:43:24Z")

</div>

I have seen these types of issues because the heap size was not big enough.  
It WILL just die and you will not know what happened.

--  
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/22b9822d-d532-47cb-adac-fc9acbf74f49%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/22b9822d-d532-47cb-adac-fc9acbf74f49%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:18am UTC](https://discuss.elastic.co/t/elasticsearch-service-often-goes-down-or-gets-killed/23320/4 "2017-07-06T00:18:27Z")

</div>