# Working 2.4 ES stops working when upgraded to 5.0

**URL:** <https://discuss.elastic.co/t/working-2-4-es-stops-working-when-upgraded-to-5-0/64173>\
**Category:** Elasticsearch\
**Created:** [October 27, 2016, 5:53pm UTC](https://discuss.elastic.co/t/working-2-4-es-stops-working-when-upgraded-to-5-0/64173 "2016-10-27T17:53:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tee1](https://avatars.discourse-cdn.com/v4/letter/t/839c29/32.png) [@Tee1](https://discuss.elastic.co/u/Tee1)\
**Post date:** [October 27, 2016, 5:53pm UTC](https://discuss.elastic.co/t/working-2-4-es-stops-working-when-upgraded-to-5-0/64173/1 "2016-10-27T17:53:03Z")

</div>

Oh no, it worked beautifully at 2.4 then crapped out at 5.0. unfortunately, I can't seem to find any good log type indication as to the problem. At the status line I see:

systemctl status elasticsearch

â elasticsearch.service - Elasticsearch  
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)  
Active: failed (Result: exit-code) since Thu 2016-10-27 13:47:22 EDT; 5s ago  
Docs: [http://www.elastic.co](http://www.elastic.co)  
Process: 2665 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG\_DIR} -Edefault.path.data=${DATA\_DIR} -Edefault.path.conf=${CONF\_DIR} (code=exited, status=78)  
Process: 2663 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)  
Main PID: 2665 (code=exited, status=78)

Oct 27 13:47:16 [es-1.eval.org](http://es-1.eval.org) systemd[1]: Starting Elasticsearch...  
Oct 27 13:47:16 [es-1.eval.org](http://es-1.eval.org) systemd[1]: Started Elasticsearch.  
Oct 27 13:47:22 [es-1.eval.org](http://es-1.eval.org) systemd[1]: elasticsearch.service: main process exited, code=exited, status=78/n/a  
Oct 27 13:47:22 [es-1.eval.org](http://es-1.eval.org) systemd[1]: Unit elasticsearch.service entered failed state.  
Oct 27 13:47:22 [es-1.eval.org](http://es-1.eval.org) systemd[1]: elasticsearch.service failed.

---

<div class="post-metadata">

**Author:** ![Tee1](https://avatars.discourse-cdn.com/v4/letter/t/839c29/32.png) [@Tee1](https://discuss.elastic.co/u/Tee1)\
**Post date:** [October 27, 2016, 6:51pm UTC](https://discuss.elastic.co/t/working-2-4-es-stops-working-when-upgraded-to-5-0/64173/2 "2016-10-27T18:51:14Z")

</div>

I've narrowed the problem to the "bootstrap.memory\_lock: true". When i comment it out , all works now.  
I've tried to do the steps as outlined on:  
[https://www.elastic.co/guide/en/elasticsearch/reference/master/\_memory\_lock\_check.html](https://www.elastic.co/guide/en/elasticsearch/reference/master/_memory_lock_check.html)

but centos 7.x doesnt not seem to support these steps.

---

<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 5, 2017, 10:09pm UTC](https://discuss.elastic.co/t/working-2-4-es-stops-working-when-upgraded-to-5-0/64173/3 "2017-07-05T22:09:00Z")

</div>