# SIGSEGV JVM Crash

**URL:** <https://discuss.elastic.co/t/sigsegv-jvm-crash/351267>\
**Category:** Elasticsearch\
**Tags:** runtime-fields\
**Created:** [January 17, 2024, 12:18pm UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267 "2024-01-17T12:18:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![vladislav](https://avatars.discourse-cdn.com/v4/letter/v/bbce88/32.png) [@vladislav](https://discuss.elastic.co/u/vladislav)\
**Post date:** [January 17, 2024, 12:18pm UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267/1 "2024-01-17T12:18:47Z")

</div>

Hello! Thanks for help in advance  
I've running a 3-nodes cluster (es1, es2, es3). Recently, after VM restart (es2 node) it constantly crashes after several hours of work with SIGSEGV.  
Here is full error from journalctl:

```auto
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: #
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # A fatal error has been detected by the Java Runtime Environment:
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: #
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # SIGSEGV (0xb) at pc=0x00007f293db4c40b, pid=44800, tid=59146
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: #
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # JRE version: OpenJDK Runtime Environment (21.0.1+12) (build 21.0.1+12-29)
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # Java VM: OpenJDK 64-Bit Server VM (21.0.1+12-29, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # Problematic frame:
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # J 45401 c2 org.apache.lucene.util.compress.LZ4.compressWithDictionary([BIIILorg/apache/lucene/store/DataOutput;Lorg/apache/lucene/util/compress/LZ4$HashTable;)V org.apache.lucene.core@9.8.0 (378 bytes) @ 0x00007f293db4c40b [0x00007f293db4bd80+0x000000000000068b]
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: #
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /usr/share/elasticsearch/core.44800)
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: #
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # An error report file with more information is saved as:
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # /var/log/elasticsearch/hs_err_pid44800.log
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: [49810.564s][warning][os] Loading hsdis library failed
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: #
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # If you would like to submit a bug report, please visit:
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: # https://bugreport.java.com/bugreport/crash.jsp
Jan 16 23:28:27 es2 systemd-entrypoint[44800]: #
Jan 16 23:28:31 es2 systemd-entrypoint[44715]: ERROR: Elasticsearch exited unexpectedly, with exit code 134
Jan 16 23:28:31 es2 systemd[1]: elasticsearch.service: Main process exited, code=exited, status=134/n/a
-- Subject: Unit process exited

```

Problematic frame seems similar everytime, last time it was `# J 40304% c2 org.apache.lucene.codecs.lucene90.blocktree.IntersectTermsEnum._next()Lorg/apache/lucene/util/BytesRef; org.apache.lucene.core@9.8.0 (828 bytes) @ 0x00007fa8cea18a95 [0x00007fa8cea18320+0x0000000000000775]`  
every time there is `org.apache.lucene.core@9.8.0`

Any ideas how to fix those crashes?  
Elasticsearch version - 8.11.1  
OpenJDK 64-Bit Server VM (21.0.1+12-29)

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 17, 2024, 2:08pm UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267/2 "2024-01-17T14:08:25Z")

</div>

> [@vladislav](#):
>
> OpenJDK 64-Bit Server VM (21.0.1+12-29)

[JDK-8321370](https://bugs.openjdk.org/browse/JDK-8321370) perhaps?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 17, 2024, 2:11pm UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267/3 "2024-01-17T14:11:04Z")

</div>

Note that we [strongly recommend using the bundled JDK](https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html#jvm-version); that's the one which is used for most tests, so using a different one is asking for trouble. `21.0.1+12` is the version bundled with v8.11.1.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 17, 2024, 2:13pm UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267/4 "2024-01-17T14:13:37Z")

</div>

Oh wait, sorry, `21.0.1+12-29` means the same as `21.0.1+12`, this is the bundled JDK after all.

---

<div class="post-metadata">

**Author:** ![vladislav](https://avatars.discourse-cdn.com/v4/letter/v/bbce88/32.png) [@vladislav](https://discuss.elastic.co/u/vladislav)\
**Post date:** [January 17, 2024, 4:04pm UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267/5 "2024-01-17T16:04:33Z")

</div>

Yes, this is bundled JDK

---

<div class="post-metadata">

**Author:** ![vladislav](https://avatars.discourse-cdn.com/v4/letter/v/bbce88/32.png) [@vladislav](https://discuss.elastic.co/u/vladislav)\
**Post date:** [January 22, 2024, 5:00am UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267/6 "2024-01-22T05:00:23Z")

</div>

Any ideas?

---

<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:** [February 19, 2024, 5:00am UTC](https://discuss.elastic.co/t/sigsegv-jvm-crash/351267/7 "2024-02-19T05:00:30Z")

</div>

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