elasticsearch bootstrap.memory_lock: true

 bootstrap.memory_lock: true

systemctl start elasticsearch

Job for elasticsearch.service failed because the control process exited with error code. See "systemctl status elasticsearch.service" and "journalctl -xe" for details.

[root@s20200210 home]# tail /var/log/me

tail: cannot open ‘/var/log/me’ for reading: No such file or directory

[root@s20200210 home]# tail /var/log/messages

Nov  9 07:35:15 s20200210 systemd: Stopping The nginx HTTP and reverse proxy server...

Nov  9 07:35:15 s20200210 systemd: Stopped The nginx HTTP and reverse proxy server.

Nov  9 07:35:57 s20200210 systemd: Starting Elasticsearch...

Nov  9 07:36:21 s20200210 systemd-entrypoint: ERROR: [1] bootstrap checks failed. You must address the points described in the following [1] lines before starting Elasticsearch.

Nov  9 07:36:21 s20200210 systemd-entrypoint: bootstrap check failure [1] of [1]: memory locking requested for elasticsearch process but memory is not locked

Nov  9 07:36:21 s20200210 systemd-entrypoint: ERROR: Elasticsearch did not exit normally - check the logs at /home/elasticsearch/elasticsearch.log

Nov  9 07:36:23 s20200210 systemd: elasticsearch.service: main process exited, code=exited, status=78/n/a

Nov  9 07:36:23 s20200210 systemd: Failed to start Elasticsearch.

Nov  9 07:36:23 s20200210 systemd: Unit elasticsearch.service entered failed state.

Nov  9 07:36:23 s20200210 systemd: elasticsearch.service failed.

[root@s20200210 home]# vim  memory locking requested for elasticsearch process but memory is not locked