# Elasticsearch crash because of JVM fatal error

**URL:** https://discuss.elastic.co/t/elasticsearch-crash-because-of-jvm-fatal-error/185055
**Category:** Elasticsearch
**Created:** [June 10, 2019, 9:03pm UTC](https://discuss.elastic.co/t/elasticsearch-crash-because-of-jvm-fatal-error/185055 "2019-06-10T21:03:55Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![xiang-liu-exa](https://avatars.discourse-cdn.com/v4/letter/x/71e660/32.png) [@xiang-liu-exa](https://discuss.elastic.co/u/xiang-liu-exa)
#### Post date: [June 10, 2019, 9:03pm UTC](https://discuss.elastic.co/t/elasticsearch-crash-because-of-jvm-fatal-error/185055/1 "2019-06-10T21:03:55Z")

</div>

Elasticsearch version 6.2.4  
The error before the process crash:

> Jun 08 10:45:44 xxx-168-24 docker[11136]: #  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: # A fatal error has been detected by the Java Runtime Environment:  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: #  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: # SIGSEGV (0xb) at pc=0x00007f3536e1eb08, pid=11, tid=139856347916032  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: #  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: # JRE version: Java(TM) SE Runtime Environment (8.0\_91-b14) (build 1.8.0\_91-b14)  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 compressed oops)  
> Jun 08 10:45:44 psr-ex3000-168-24 docker[11136]: # Problematic frame:  
> Jun 08 10:45:44 psr-ex3000-168-24 docker[11136]: # J 27430 C2 org.elasticsearch.index.engine.LiveVersionMap.getUnderLock(Lorg/apache/lucene/util/BytesRef;Lorg/elasticsearch/index/engine/LiveVersionMap$Maps;)Lorg/elasticsearch/index/engine/VersionValue; (69 bytes) @ 0x00007f3536e1eb08 [0x00007f3536e1de40+0xcc8]  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: #  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: # Core dump written. Default location: /opt/elasticsearch/core or core.11  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: #  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: # An error report file with more information is saved as:  
> Jun 08 10:45:44 xxx-168-24 docker[11136]: # /opt/elasticsearch/hs\_err\_pid11.log  
> Jun 08 10:45:45 xxx-168-24 docker[11136]: #  
> Jun 08 10:45:45 xxx-168-24 docker[11136]: # If you would like to submit a bug report, please visit:  
> Jun 08 10:45:45 xxx-168-24 docker[11136]: # [Crash Report](http://bugreport.java.com/bugreport/crash.jsp)  
> Jun 08 10:45:45 xxx-168-24 docker[11136]: #

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [June 10, 2019, 9:57pm UTC](https://discuss.elastic.co/t/elasticsearch-crash-because-of-jvm-fatal-error/185055/2 "2019-06-10T21:57:03Z")

</div>

There should be Elasticsearch logs with more information?

---

<div class="post-metadata">

### Author: ![xiang-liu-exa](https://avatars.discourse-cdn.com/v4/letter/x/71e660/32.png) [@xiang-liu-exa](https://discuss.elastic.co/u/xiang-liu-exa)
#### Post date: [June 10, 2019, 10:17pm UTC](https://discuss.elastic.co/t/elasticsearch-crash-because-of-jvm-fatal-error/185055/3 "2019-06-10T22:17:03Z")

</div>

This is the last logs before crash.  
Before JVM error, there are some GC message which are normal.

---

<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: [July 8, 2019, 10:17pm UTC](https://discuss.elastic.co/t/elasticsearch-crash-because-of-jvm-fatal-error/185055/4 "2019-07-08T22:17:12Z")

</div>

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