# Elasticsearch process memory locking failed

**URL:** <https://discuss.elastic.co/t/elasticsearch-process-memory-locking-failed/92427>\
**Category:** Elasticsearch\
**Created:** [July 10, 2017, 8:26am UTC](https://discuss.elastic.co/t/elasticsearch-process-memory-locking-failed/92427 "2017-07-10T08:26:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shantanu\_Deshmukh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shantanu_deshmukh/32/19885_2.png) [@Shantanu\_Deshmukh](https://discuss.elastic.co/u/Shantanu_Deshmukh)\
**Post date:** [July 10, 2017, 8:26am UTC](https://discuss.elastic.co/t/elasticsearch-process-memory-locking-failed/92427/1 "2017-07-10T08:26:02Z")

</div>

I have set boostrap.memory\_lock=true  
Updated /etc/security/limits.conf added memlock unlimited for elastic search user

My elastic search was running fine for many months. Suddenly it failed 1 day back. In logs I can see below error and process never starts

ERROR: bootstrap checks failed  
memory locking requested for elasticsearch process but memory is not locked

I hit ulimit -as and I can see max locked memory set to unlimited. What is going wrong here? I have been trying for hours but all in vain. Please help.

OS is RHEL 7.2  
Elasticsearch 5.1.2

---

<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:** [August 7, 2017, 8:26am UTC](https://discuss.elastic.co/t/elasticsearch-process-memory-locking-failed/92427/2 "2017-08-07T08:26:40Z")

</div>

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