# Help getting mlockall to work on ubuntu 14.04 **URL:** \ **Category:** Elasticsearch\ **Created:** [March 28, 2016, 8:34pm UTC](https://discuss.elastic.co/t/help-getting-mlockall-to-work-on-ubuntu-14-04/45623 "2016-03-28T20:34:49Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jerry\_Hoffmeister](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@Jerry\_Hoffmeister](https://discuss.elastic.co/u/Jerry_Hoffmeister)\ **Post date:** [March 28, 2016, 8:34pm UTC](https://discuss.elastic.co/t/help-getting-mlockall-to-work-on-ubuntu-14-04/45623/1 "2016-03-28T20:34:49Z")
Hi, Trying to get mlockall to work... I see this in the log: [2016-03-28 20:06:26,568][WARN][bootstrap] Unable to lock JVM Memory: error=12,reason=Cannot allocate memory [2016-03-28 20:06:26,569][WARN][bootstrap] This can result in part of the JVM being swapped out. [2016-03-28 20:06:26,570][WARN][bootstrap] Increase RLIMIT\_MEMLOCK, soft limit: 65536, hard limit: 65536 [2016-03-28 20:06:26,570][WARN][bootstrap] These can be adjusted by modifying /etc/security/limits.conf, for example: # allow user 'elasticsearch' mlockall elasticsearch soft memlock unlimited elasticsearch hard memlock unlimited [2016-03-28 20:06:26,570][WARN][bootstrap] If you are logged in interactively, you will have to re-login for the new limits to take effect. [2016-03-28 20:06:27,255][INFO][node] [arrow] version[2.2.1], pid[2145], build[d045fc2/2016-03-09T09:38:54Z] I've made the change as suggested to /etc/security/limits.conf and also moved the tmp dir but I still see the above warning and when I run: jhoff909@eip-elk-es2:~$ curl 172.16.0.103:9200/\_nodes/stats/process?pretty | grep mlock % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1140 100 1140 0 0 52600 0 --:--:-- --:--:-- --:--:-- 54285 I don't see the setting? Also, when I look at the limits on the process, looks like my change to limits.conf didn't take effect (I have rebooted): Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 27836 27836 processes Max open files 65535 65535 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 27836 27836 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us What am I missing? I've only made this change on one node in my cluster this far - want to get it working there first... Thanks in advance for the help. ---
**Author:** ![Jerry\_Hoffmeister](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@Jerry\_Hoffmeister](https://discuss.elastic.co/u/Jerry_Hoffmeister)\ **Post date:** [March 28, 2016, 8:44pm UTC](https://discuss.elastic.co/t/help-getting-mlockall-to-work-on-ubuntu-14-04/45623/2 "2016-03-28T20:44:48Z")
I may have solved it - I hadn't set MAX\_LOCKED\_MEMORY=unlimited in the init script. Changing this made the warning go away but running curl 172.16.0.103:9200/\_nodes/stats/process?pretty still doesn't show the setting? I also now see this line in the process limits: Max locked memory unlimited unlimited bytes ---
**Author:** ![msimos](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@msimos](https://discuss.elastic.co/u/msimos)\ **Post date:** [March 28, 2016, 10:00pm UTC](https://discuss.elastic.co/t/help-getting-mlockall-to-work-on-ubuntu-14-04/45623/3 "2016-03-28T22:00:10Z")
You need to set one of the following: systemd: /usr/lib/systemd/system/elasticsearch.service set: LimitMEMLOCK=infinity SysV: /etc/sysconfig/elasticsearch set: MAX\_LOCKED\_MEMORY=unlimited Upstart: /etc/default/elasticsearch set: MAX\_LOCKED\_MEMORY=unlimited Then restart Elasticsearch. ---
**Author:** ![Jerry\_Hoffmeister](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@Jerry\_Hoffmeister](https://discuss.elastic.co/u/Jerry_Hoffmeister)\ **Post date:** [March 28, 2016, 10:04pm UTC](https://discuss.elastic.co/t/help-getting-mlockall-to-work-on-ubuntu-14-04/45623/4 "2016-03-28T22:04:17Z")
Yes, I added MAX\_LOCKED\_MEMORY=unlimited in the package installed init script /etc/init.d/elasticsearch which made the warning go away but I still don't see the setting when I run curl 172.16.0.103:9200/\_nodes/stats/process?pretty which may be just because I've only made the change on one node.... or not. Now all have the same config and I still don't see the setting change in the curl output. ---
**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, 11:04pm UTC](https://discuss.elastic.co/t/help-getting-mlockall-to-work-on-ubuntu-14-04/45623/5 "2017-07-05T23:04:33Z")