# JVM core dump with official Docker image for ElasticSearch 5.5.3

**URL:** <https://discuss.elastic.co/t/jvm-core-dump-with-official-docker-image-for-elasticsearch-5-5-3/108578>\
**Category:** Elasticsearch\
**Created:** [November 21, 2017, 3:03pm UTC](https://discuss.elastic.co/t/jvm-core-dump-with-official-docker-image-for-elasticsearch-5-5-3/108578 "2017-11-21T15:03:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andre\_Caron](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_caron/32/24516_2.png) [@Andre\_Caron](https://discuss.elastic.co/u/Andre_Caron)\
**Post date:** [November 21, 2017, 3:03pm UTC](https://discuss.elastic.co/t/jvm-core-dump-with-official-docker-image-for-elasticsearch-5-5-3/108578/1 "2017-11-21T15:03:10Z")

</div>

Hi there!

I'm porting my application to ElasticSearch and Kibana 5.5 (from 1.7 and 4.1, respectively). I'm not migrating any data (yet), only trying to get my application to run against a fresh instance of 5.5.

While doing this, I hit a JVM core dump several times with ElasticSearch 5.5.3 (also occurred on ElasticSearch 5.4.3).

I reported the issue on GitHub (see [https://github.com/elastic/elasticsearch-docker/issues/137](https://github.com/elastic/elasticsearch-docker/issues/137)) with full details. The issue creation tips there suggested sending the info here to reach a wider audience.

Has anyone hit this issue before?

Is there any additional info I can provide that would help shed more light on the issue?

André

---

<div class="post-metadata">

**Author:** ![dliappis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dliappis/32/56174_2.png) [@dliappis](https://discuss.elastic.co/u/dliappis)\
**Post date:** [November 23, 2017, 12:15pm UTC](https://discuss.elastic.co/t/jvm-core-dump-with-official-docker-image-for-elasticsearch-5-5-3/108578/2 "2017-11-23T12:15:45Z")

</div>

Looking at the docker inspect output in [https://github.com/elastic/elasticsearch-docker/issues/137#issue-275738753](https://github.com/elastic/elasticsearch-docker/issues/137#issue-275738753) it seems that you are using a bind mount for /usr/share/elasticsearch so you could check the local mount for the .log file (probably though this output is after you tried to unsuccessfully bind-mount the whole `/usr/share/elasticsearch` dir to extract the log file).

At any rate, if you wish to fish out a file from Docker's union filesystem, in your case, since you are using AUFS with boot2docker, you can always jump inside the VM where docker runs and as root:

```auto
cd /var/lib/docker/aufs
find ./ -name "*hs_err_pid1.log"

```

On an Ubuntu 14.04 VM I installed the latest docker-ce, configured it to use aufs by setting:

```auto
root@m01:/var/lib/docker/aufs# cat /etc/docker/daemon.json 
{"storage-driver": "aufs"}

```

and then started Elasticsearch 5.6.3, without any bind mounts or volumes:

```auto
docker run -d --name es563 docker.elastic.co/elasticsearch/elasticsearch:5.6.3

```

Then I entered the container, created a temp file simulating ES's log file and finally killed the container by abruptly ending the ES process:

```auto
docker exec -ti es563 /bin/bash
touch hs_err_pid1.log
kill 1

```

The as the `root` user in the VM, I can find the log file using:

```auto
# cd /var/lib/docker/aufs/
# find ./ -name "*hs_err_pid1.log"
./diff/0dcb78cf0c2262cb667e6c89dbf96216336697fc4710d26cec4bdc7faf354514/usr/share/elasticsearch/hs_err_pid1.log

```

When you have the contents this file you can paste them here for further troubleshooting.

---

<div class="post-metadata">

**Author:** ![Andre\_Caron](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_caron/32/24516_2.png) [@Andre\_Caron](https://discuss.elastic.co/u/Andre_Caron)\
**Post date:** [November 26, 2017, 3:49am UTC](https://discuss.elastic.co/t/jvm-core-dump-with-official-docker-image-for-elasticsearch-5-5-3/108578/3 "2017-11-26T03:49:14Z")

</div>

Hi @dliappis!

Thanks for the tip. I'll try that and get back here as soon as I have a chance!

---

<div class="post-metadata">

**Author:** ![Andre\_Caron](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_caron/32/24516_2.png) [@Andre\_Caron](https://discuss.elastic.co/u/Andre_Caron)\
**Post date:** [November 29, 2017, 1:54pm UTC](https://discuss.elastic.co/t/jvm-core-dump-with-official-docker-image-for-elasticsearch-5-5-3/108578/4 "2017-11-29T13:54:50Z")

</div>

Alright, so I managed to get back to this. I came in this morning with the same crash as last time. This one doesn't have the bind mount.

Core dumps were not enabled, but I still recovered the `hs_err_pid1.log` file.

I can't seem to upload it here. Attachments seem to be limited to images and the file contents exceed the 7000 character limit on post bodies. I pasted the contents to the GitHub issue to work around these limitations.

Let me know if the log file provides any insight.

---

<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:** [December 27, 2017, 1:54pm UTC](https://discuss.elastic.co/t/jvm-core-dump-with-official-docker-image-for-elasticsearch-5-5-3/108578/5 "2017-12-27T13:54:59Z")

</div>

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