# Boot Strap check failed

**URL:** <https://discuss.elastic.co/t/boot-strap-check-failed/67566>\
**Category:** Elasticsearch\
**Created:** [November 30, 2016, 12:55am UTC](https://discuss.elastic.co/t/boot-strap-check-failed/67566 "2016-11-30T00:55:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sureshkumar](https://avatars.discourse-cdn.com/v4/letter/s/c2a13f/32.png) [@Sureshkumar](https://discuss.elastic.co/u/Sureshkumar)\
**Post date:** [November 30, 2016, 12:55am UTC](https://discuss.elastic.co/t/boot-strap-check-failed/67566/1 "2016-11-30T00:55:58Z")

</div>

Hi  
When i upgrade to elastic search 5.0.2 below error message received and its elastic search instance is getting closed.  
[2016-11-30T00:47:09,525][INFO][o.e.t.TransportService] [m7H0n9h] publish\_address {10.50.0.165:9300}, bound\_addresses {[::]:9300}  
[2016-11-30T00:47:09,531][INFO][o.e.b.BootstrapCheck] [m7H0n9h] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks  
ERROR: bootstrap checks failed  
initial heap size [2147483648] not equal to maximum heap size [4294967296]; this can cause resize pauses and prevents mlockall from locking the entire heap  
max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]  
memory locking requested for elasticsearch process but memory is not locked  
max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144]  
[2016-11-30T00:47:09,538][INFO][o.e.n.Node] [m7H0n9h] stopping ...  
[2016-11-30T00:47:09,640][INFO][o.e.n.Node] [m7H0n9h] stopped  
[2016-11-30T00:47:09,640][INFO][o.e.n.Node] [m7H0n9h] closing ...  
[2016-11-30T00:47:09,658][INFO][o.e.n.Node] [m7H0n9h] closed

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [November 30, 2016, 8:19am UTC](https://discuss.elastic.co/t/boot-strap-check-failed/67566/2 "2016-11-30T08:19:26Z")

</div>

I think the messages state pretty clearly what you need to do. What, in particular, do you want to see clarified?

---

<div class="post-metadata">

**Author:** ![Sureshkumar](https://avatars.discourse-cdn.com/v4/letter/s/c2a13f/32.png) [@Sureshkumar](https://discuss.elastic.co/u/Sureshkumar)\
**Post date:** [November 30, 2016, 6:31pm UTC](https://discuss.elastic.co/t/boot-strap-check-failed/67566/3 "2016-11-30T18:31:28Z")

</div>

Thanks for responding.  
I like to know how to fix this issue.

---

<div class="post-metadata">

**Author:** ![Sureshkumar](https://avatars.discourse-cdn.com/v4/letter/s/c2a13f/32.png) [@Sureshkumar](https://discuss.elastic.co/u/Sureshkumar)\
**Post date:** [November 30, 2016, 6:35pm UTC](https://discuss.elastic.co/t/boot-strap-check-failed/67566/4 "2016-11-30T18:35:40Z")

</div>

> [@Sureshkumar](#):
>
> non-loopback or non-link-local address

I didnt face this issue previous version. I am little confused where to fix the issue. currently my Elasticsearch instance is AWS.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 4, 2016, 6:32am UTC](https://discuss.elastic.co/t/boot-strap-check-failed/67566/5 "2016-12-04T06:32:04Z")

</div>

Read this: [https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 1, 2017, 6:32am UTC](https://discuss.elastic.co/t/boot-strap-check-failed/67566/6 "2017-01-01T06:32:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.