# Elasticsearch.service: Main process exited, code=killed, status=9/KILL

**URL:** https://discuss.elastic.co/t/elasticsearch-service-main-process-exited-code-killed-status-9-kill/304358
**Category:** Elasticsearch
**Tags:** docker
**Created:** [May 10, 2022, 2:14pm UTC](https://discuss.elastic.co/t/elasticsearch-service-main-process-exited-code-killed-status-9-kill/304358 "2022-05-10T14:14:49Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![viththakan](https://avatars.discourse-cdn.com/v4/letter/v/58f4c7/32.png) [@viththakan](https://discuss.elastic.co/u/viththakan)
#### Post date: [May 10, 2022, 2:14pm UTC](https://discuss.elastic.co/t/elasticsearch-service-main-process-exited-code-killed-status-9-kill/304358/1 "2022-05-10T14:14:49Z")

</div>

Hi I havefirst installed Elasticsearch, logstash, kibana and filebeats in the same order. When I installed Elasticsearch and checked status It worked. Now it is showing the error like

```auto
systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
     Loaded: loaded (/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Tue 2022-05-10 13:55:52 UTC; 45s ago
       Docs: https://www.elastic.co
    Process: 65664 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pi>
   Main PID: 65664 (code=killed, signal=KILL)

May 10 13:55:48 Master systemd[1]: Starting Elasticsearch...
May 10 13:55:52 Master systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
May 10 13:55:52 Master systemd[1]: elasticsearch.service: Failed with result 'signal'.
May 10 13:55:52 Master systemd[1]: Failed to start Elasticsearch.

```

Here is the System log files

```auto
journalctl -xe
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mount has successfully ente>
May 10 13:59:22 Master systemd[957]: run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mo>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:23 Master filebeat[20844]: 2022-05-10T13:59:23.806Z INFO [monitoring] log/log.go:184 Non-zero metrics in th>
May 10 13:59:24 Master systemd[957]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mo>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:24 Master systemd[1]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.moun>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount has successfully ente>
May 10 13:59:26 Master systemd[1]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.moun>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount has successfully ente>
May 10 13:59:26 Master systemd[957]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mo>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
lines 2212-2246/2246 (END)
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mount has successfully entered the 'dead' state.
May 10 13:59:22 Master systemd[957]: run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:23 Master filebeat[20844]: 2022-05-10T13:59:23.806Z INFO [monitoring] log/log.go:184 Non-zero metrics in the last 30s {"monitorin>
May 10 13:59:24 Master systemd[957]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:24 Master systemd[1]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount has successfully entered the 'dead' state.
May 10 13:59:26 Master systemd[1]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount has successfully entered the 'dead' state.
May 10 13:59:26 Master systemd[957]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.

```

I think it is not because of the memory issue. What else could cause the error? Can anyone help?

---

<div class="post-metadata">

### Author: ![ibra\_013](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ibra_013/32/104827_2.png) [@ibra\_013](https://discuss.elastic.co/u/ibra_013)
#### Post date: [May 17, 2022, 8:41pm UTC](https://discuss.elastic.co/t/elasticsearch-service-main-process-exited-code-killed-status-9-kill/304358/2 "2022-05-17T20:41:15Z")

</div>

Hi,

could you share the Elasticsearch logs.

---

<div class="post-metadata">

### Author: ![viththakan](https://avatars.discourse-cdn.com/v4/letter/v/58f4c7/32.png) [@viththakan](https://discuss.elastic.co/u/viththakan)
#### Post date: [May 19, 2022, 3:59am UTC](https://discuss.elastic.co/t/elasticsearch-service-main-process-exited-code-killed-status-9-kill/304358/3 "2022-05-19T03:59:13Z")

</div>

```auto
journalctl -xe
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mount has successfully ente>
May 10 13:59:22 Master systemd[957]: run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mo>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:23 Master filebeat[20844]: 2022-05-10T13:59:23.806Z INFO [monitoring] log/log.go:184 Non-zero metrics in th>
May 10 13:59:24 Master systemd[957]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mo>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:24 Master systemd[1]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.moun>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount has successfully ente>
May 10 13:59:26 Master systemd[1]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.moun>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount has successfully ente>
May 10 13:59:26 Master systemd[957]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mo>
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
lines 2212-2246/2246 (END)
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mount has successfully entered the 'dead' state.
May 10 13:59:22 Master systemd[957]: run-docker-runtime\x2drunc-moby-a65d06ab5e6db0fc7998e2e08e52f42bbfdc0ed4bae68ed3e26ca952248c48a8-runc.VIHXZg.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:23 Master filebeat[20844]: 2022-05-10T13:59:23.806Z INFO [monitoring] log/log.go:184 Non-zero metrics in the last 30s {"monitorin>
May 10 13:59:24 Master systemd[957]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.
May 10 13:59:24 Master systemd[1]: run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-67ab76e3a5066f7f06458a61d5e343d661b8b0474260a4b2dcd5ac08c3dca762-runc.Goykwd.mount has successfully entered the 'dead' state.
May 10 13:59:26 Master systemd[1]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount has successfully entered the 'dead' state.
May 10 13:59:26 Master systemd[957]: run-docker-runtime\x2drunc-moby-86db097b0ad520faa4c03565ee2cb4c546d795171f91715c8f2830250d3ac9fa-runc.yWcyIW.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has successfully entered the 'dead' state.

```

---

<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: [June 16, 2022, 3:59am UTC](https://discuss.elastic.co/t/elasticsearch-service-main-process-exited-code-killed-status-9-kill/304358/4 "2022-06-16T03:59:20Z")

</div>

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