Error with elasricsearch

i run this line

sudo -i service elasticsearch start

i got this error

Job for elasticsearch.service failed because a fatal signal was delivered to the control process.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.

when i run "systemctl status Elasticsearch.service" and "journalctl -xe"
i got these

ubuntu@ip-172-31-32-194:~$ systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
     Loaded: loaded (/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)
     Active: failed (Result: signal) since Fri 2021-09-24 20:48:17 UTC; 5min ago
       Docs: https://www.elastic.co
    Process: 30397 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=killed, signal=KILL)
   Main PID: 30397 (code=killed, signal=KILL)

Sep 24 20:48:13 ip-172-31-32-194 systemd[1]: Starting Elasticsearch...
Sep 24 20:48:17 ip-172-31-32-194 systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
Sep 24 20:48:17 ip-172-31-32-194 systemd[1]: elasticsearch.service: Failed with result 'signal'.
Sep 24 20:48:17 ip-172-31-32-194 systemd[1]: Failed to start Elasticsearch.

******************************************************************************************

ubuntu@ip-172-31-32-194:~$ journalctl -xe
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  29006]  1000 29006     2757      663    61440        0             0 systemctl
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  29007]  1000 29007     1897      425    53248        0             0 pager
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  29256]     0 29256   164103     5155   229376        0          -900 snapd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30215]     0 30215   308356     2196   188416        0             0 amazon-ssm-agen
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30245]     0 30245   293453     3530   217088        0             0 ssm-agent-worke
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30293]     0 30293     3450     1039    61440        0             0 sshd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30373]  1000 30373     3483      670    65536        0             0 sshd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30374]  1000 30374     2512      903    57344        0             0 bash
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30383]     0 30383     2792      689    57344        0             0 sudo
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30384]     0 30384     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30385]     0 30385     2757      586    57344        0             0 systemctl
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30396]     0 30396     4061      833    73728        0             0 systemd-tty-ask
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30397]   114 30397   285022    93475   913408        0             0 java
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30398]     0 30398     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30399]     0 30399     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30400]     0 30400     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30401]     0 30401     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30402]     0 30402     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30403]     0 30403     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30404]     0 30404     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30405]     0 30405     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: [  30406]     0 30406     4862      783    57344        0             0 systemd-udevd
Sep 24 20:48:17 ip-172-31-32-194 kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/elasticsearch.service,task=java>Sep 24 20:48:17 ip-172-31-32-194 kernel: Out of memory: Killed process 30397 (java) total-vm:1140088kB, anon-rss:371840kB, file-rss:2060kB, shmem-rss:0kB, UID:114 pgtables:892kB oom_sc>Sep 24 20:48:17 ip-172-31-32-194 kernel: oom_reaper: reaped process 30397 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Sep 24 20:48:17 ip-172-31-32-194 systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit elasticsearch.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 9.
Sep 24 20:48:17 ip-172-31-32-194 sudo[30383]: pam_unix(sudo:session): session closed for user root
Sep 24 20:48:17 ip-172-31-32-194 systemd[1]: elasticsearch.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit elasticsearch.service has entered the 'failed' state with result 'signal'.
Sep 24 20:48:17 ip-172-31-32-194 systemd[1]: Failed to start Elasticsearch.
-- Subject: A start job for unit elasticsearch.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit elasticsearch.service has finished with a failure.
--
-- The job identifier is 4568 and the job result is failed.

how to solve it and thanks

What is in the Elasticsearch logs?

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