# Elasticsearch did not passed bootstrap

**URL:** <https://discuss.elastic.co/t/elasticsearch-did-not-passed-bootstrap/178791>\
**Category:** Elasticsearch\
**Created:** [April 28, 2019, 9:45am UTC](https://discuss.elastic.co/t/elasticsearch-did-not-passed-bootstrap/178791 "2019-04-28T09:45:19Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dbakti7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dbakti7/32/42250_2.png) [@dbakti7](https://discuss.elastic.co/u/dbakti7)\
**Post date:** [April 28, 2019, 1:32pm UTC](https://discuss.elastic.co/t/elasticsearch-did-not-passed-bootstrap/178791/5 "2019-04-28T13:32:35Z")

</div>

Most likely the user doesn't have permission to lock the memory, you can try the instructions here:

> **[Disable swapping | Elasticsearch Guide \[6.7\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/setup-configuration-memory.html#bootstrap-memory_lock)**

Specifically from

> The most probable reason, on Linux/Unix systems, is that the user running Elasticsearch doesn’t have permission to lock memory. This can be granted as follows:  
> ...

Extra references: [Elasticsearch is not starting when bootstrap.memory\_lock is set to true](https://discuss.elastic.co/t/elasticsearch-is-not-starting-when-bootstrap-memory-lock-is-set-to-true/120962)

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-did-not-passed-bootstrap/178791)._