# Bootstrap check failure in 8.15.2

**URL:** <https://discuss.elastic.co/t/bootstrap-check-failure-in-8-15-2/368660>\
**Category:** Elasticsearch\
**Created:** [October 11, 2024, 3:54am UTC](https://discuss.elastic.co/t/bootstrap-check-failure-in-8-15-2/368660 "2024-10-11T03:54:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mousumis](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@mousumis](https://discuss.elastic.co/u/mousumis)\
**Post date:** [October 11, 2024, 3:54am UTC](https://discuss.elastic.co/t/bootstrap-check-failure-in-8-15-2/368660/1 "2024-10-11T03:54:16Z")

</div>

I am trying to upgrade an elasticsearch deployment from 8.14.1 to 8.15.2. It is not able to start up due to the following bootstrap check failure.

```auto
[ERROR][org.elasticsearch.bootstrap.Elasticsearch] [server-deployment] node validation exception
[2] bootstrap checks failed. You must address the points described in the following [2] lines before starting Elasticsearch. For more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.15/bootstrap-checks.html]
bootstrap check failure [1] of [2]: max size virtual memory [-1] for user [<redacted>] is too low, increase to [unlimited]; for more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.15/max-size-virtual-memory-check.html]
bootstrap check failure [2] of [2]: max file size [-1] for user [<redacted>] is too low, increase to [unlimited]; for more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.15/_max_file_size_check.html]

```

From what I can gather in release docs these checks have not changed in 8.15 in particular. Is there any reason this would now start failing? I have verified that 8.14 can still start up on the base image we build on, so our OS specs have not changed.

---

<div class="post-metadata">

**Author:** ![buitcj](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@buitcj](https://discuss.elastic.co/u/buitcj)\
**Post date:** [October 15, 2024, 6:17pm UTC](https://discuss.elastic.co/t/bootstrap-check-failure-in-8-15-2/368660/2 "2024-10-15T18:17:00Z")

</div>

I also noticed this and actually my bootstrap started failing in upgrading from 8.14.3 to 8.15.1

It might have something to do with [Move rlimit calls into NativeAccess (#108805) · elastic/elasticsearch@bc499e7 · GitHub](https://github.com/elastic/elasticsearch/commit/bc499e7c830d55c94042f141e4c1501348f397aa)

---

<div class="post-metadata">

**Author:** ![mousumis](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@mousumis](https://discuss.elastic.co/u/mousumis)\
**Post date:** [October 16, 2024, 8:07pm UTC](https://discuss.elastic.co/t/bootstrap-check-failure-in-8-15-2/368660/3 "2024-10-16T20:07:20Z")

</div>

Update on this - we have found that installing the libzstd library (which we did not previously have in our image) resolved the bootstrap issue.

I do not understand why this is occurring though. It looks like there were changes to how the bootstrap check is done in 8.15 as [buitcj](https://discuss.elastic.co/u/buitcj) mentioned in their comment, but how is the libzstd library tied to this? Moreover, this sounds like a bug or unintended side effect which should be remediated or at the very least documented.