# Memlock is stopping node from starting after update **URL:** \ **Category:** Elasticsearch\ **Created:** [November 13, 2017, 12:42pm UTC](https://discuss.elastic.co/t/memlock-is-stopping-node-from-starting-after-update/107389 "2017-11-13T12:42:21Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jannesvh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jannesvh/32/22371_2.png) [@jannesvh](https://discuss.elastic.co/u/jannesvh)\ **Post date:** [November 13, 2017, 12:42pm UTC](https://discuss.elastic.co/t/memlock-is-stopping-node-from-starting-after-update/107389/1 "2017-11-13T12:42:21Z")
Hi, I updated from 5.5.2 to 5.6.4 and after the update my node doesn't want to start with memlock = true. getting this in my log file: ```auto Unable to lock JVM Memory: error=12, reason=Cannot allocate memory ``` /etc/security/limits.conf ```auto elasticsearch - nofile 65535 elasticsearch - memlock unlimited ``` ---
**Author:** ![jannesvh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jannesvh/32/22371_2.png) [@jannesvh](https://discuss.elastic.co/u/jannesvh)\ **Post date:** [November 14, 2017, 8:19am UTC](https://discuss.elastic.co/t/memlock-is-stopping-node-from-starting-after-update/107389/2 "2017-11-14T08:19:44Z")
I tried to setup a new node with 5.6.4 and I cant start it with memlock = true. So I assume something changed in 5.6.4 regarding memlock? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 12, 2017, 8:19am UTC](https://discuss.elastic.co/t/memlock-is-stopping-node-from-starting-after-update/107389/3 "2017-12-12T08:19:56Z")
Closed on December 12, 2017, 8:19am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.