Failed to start Elasticsearch, error code status 143

[shiva1 (Shivakumar Mahalingam)]

Hi,
I am new to installing Elasticsearch, I did install Elasticsearch in debian buster 10, and when trying to start the Elasticsearch have the issue, it fails to start with (code=exited, status=143)

Output :

root@ip-172-31-21-204:/usr/share# systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
   Loaded: loaded (/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Fri 2022-02-25 15:44:44 UTC; 8min ago
     Docs: https://www.elastic.co
  Process: 20359 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=143)
 Main PID: 20359 (code=exited, status=143)

Feb 25 15:43:28 ip-172-31-21-204 systemd[1]: Starting Elasticsearch...
Feb 25 15:44:43 ip-172-31-21-204 systemd[1]: elasticsearch.service: Start operation timed out. Terminating.
Feb 25 15:44:44 ip-172-31-21-204 systemd[1]: elasticsearch.service: Failed with result 'timeout'.
Feb 25 15:44:44 ip-172-31-21-204 systemd[1]: Failed to start Elasticsearch.`Preformatted text`

Lot of blogs talks about increase the timeout value but where do we need to do it?

Elasticsearch.yml

network.host: localhost
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
# trying to fix Timout issue
#
elasticsearch.shardTimeout: 60000

Any quick update will be really helpful.

[dadoonet (David Pilato)]

What are the Elasticsearch logs?

[shiva1 (Shivakumar Mahalingam)]

Thanks for your reply i found out from logs the memory was less & causing the issue so increased my instance capacity and it worked.