E-ES: 'Cannot allocate memory' Error While Starting Elastic Search (Doc ID 2503629.1)

Last updated on APRIL 04, 2025

Applies to:

Goal

 Question: How to overcome the below when starting the  elasticsearch service?
"
ERROR: [2] bootstrap checks failed
[1]: memory locking requested for elasticsearch process but memory is not locked
[2]: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk"
..
Unable to lock JVM Memory: error=12, reason=Cannot allocate memory
[WARN ][o.e.b.JNANatives         ] This can result in part of the JVM being swapped out.
[WARN ][o.e.b.JNANatives         ] Increase RLIMIT_MEMLOCK, soft limit: 65536, hard limit: 65536
[WARN ][o.e.b.JNANatives         ] These can be adjusted by modifying /etc/security/limits.conf, for example:
# allow user 'elasticsearch' mlockall
elasticsearch soft memlock unlimited
elasticsearch hard memlock unlimited

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.