# Not able to start elasticsearch due to failed memory lock

**URL:** <https://discuss.elastic.co/t/not-able-to-start-elasticsearch-due-to-failed-memory-lock/158009>\
**Category:** Elasticsearch\
**Created:** [November 23, 2018, 12:34pm UTC](https://discuss.elastic.co/t/not-able-to-start-elasticsearch-due-to-failed-memory-lock/158009 "2018-11-23T12:34:33Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Magnus\_Kessler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnus_kessler/32/42001_2.png) [@Magnus\_Kessler](https://discuss.elastic.co/u/Magnus_Kessler)\
**Post date:** [November 26, 2018, 8:02am UTC](https://discuss.elastic.co/t/not-able-to-start-elasticsearch-due-to-failed-memory-lock/158009/6 "2018-11-26T08:02:27Z")

</div>

Have a look at this previous [post](https://discuss.elastic.co/t/es-5-2-node-validation-exception-bootstrap-checks-failed-no-other-error/77922/4), which described a similar issue.

Could you please check if the logs contain messages that show in more detail why the syscall filters failed? It may have to do with the way the kernel was compiled.

If all else fails, you may have to disable memlock and syscall filtering (see the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/_system_call_filter_check.html), on how to do this).

---

_[View the full topic](https://discuss.elastic.co/t/not-able-to-start-elasticsearch-due-to-failed-memory-lock/158009)._