# Reviving Elasticsearch 5.0.0

**URL:** <https://discuss.elastic.co/t/reviving-elasticsearch-5-0-0/67111>\
**Category:** Elasticsearch\
**Created:** [November 24, 2016, 1:33pm UTC](https://discuss.elastic.co/t/reviving-elasticsearch-5-0-0/67111 "2016-11-24T13:33:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![DimitrisFilippou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dimitrisfilippou/32/13229_2.png) [@DimitrisFilippou](https://discuss.elastic.co/u/DimitrisFilippou)\
**Post date:** [November 24, 2016, 1:33pm UTC](https://discuss.elastic.co/t/reviving-elasticsearch-5-0-0/67111/1 "2016-11-24T13:33:13Z")

</div>

My Elastic Stack is correctly up and running with Logstash , Kibana and Elasticsearch. Elasticsearch is running as a daemon (/etc/init.d/elasticsearch start|stop etc...).

Sometimes due to low memory Elasticsearch fails and kibana status turns red. I obviously need to upgrade my memory and i did to 8 GB but still i want to be 100% sure that it will never crash/fail .

My question is how can i get Elasticsearch to run again as a daemon after it fails?

It fails rarely but it does.. so when it does i want it to run again.

My Elasticsearch version is 5.0.0 , im using ubuntu 16.04 and i followed these steps

> **[jimfilippou/elastic-stack](https://github.com/jimfilippou/elastic-stack)**
>
> elastic-stack - A complete documentation on how to install Elastic Stack on Ubuntu 16.04 Server ASAP 😎

in addition , supervisor is not ideal for this issue because it can't handle daemons.

---

<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:** [November 27, 2016, 7:40am UTC](https://discuss.elastic.co/t/reviving-elasticsearch-5-0-0/67111/2 "2016-11-27T07:40:25Z")

</div>

Well you can setup something to autorestart ES, but that never solves the problem of _why_ it stopped.  
That's a whole other thing to deal with and I am not sure there is a simple solution.

---

<div class="post-metadata">

**Author:** ![ara](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@ara](https://discuss.elastic.co/u/ara)\
**Post date:** [November 27, 2016, 11:45am UTC](https://discuss.elastic.co/t/reviving-elasticsearch-5-0-0/67111/3 "2016-11-27T11:45:18Z")

</div>

Hi Dimitris,

it looks like you are using upstart, so you could investigate the **respawn** stanza in your upstart script  
[http://upstart.ubuntu.com/cookbook/#respawn](http://upstart.ubuntu.com/cookbook/#respawn)

And +1 with what Mark said you should investigate why ES crash.  
ES can run with low memory, I use ES\_HEAP\_SIZE=1g (in ES shell script) in two VM and never had a crash

---

<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:** [December 25, 2016, 11:45am UTC](https://discuss.elastic.co/t/reviving-elasticsearch-5-0-0/67111/4 "2016-12-25T11:45:31Z")

</div>

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