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
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
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?