# Failed to start Elasticsearch, error code status 143

**URL:** <https://discuss.elastic.co/t/failed-to-start-elasticsearch-error-code-status-143/298303>\
**Category:** Elasticsearch\
**Created:** [February 25, 2022, 4:22pm UTC](https://discuss.elastic.co/t/failed-to-start-elasticsearch-error-code-status-143/298303 "2022-02-25T16:22:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shiva1](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@shiva1](https://discuss.elastic.co/u/shiva1)\
**Post date:** [February 25, 2022, 4:22pm UTC](https://discuss.elastic.co/t/failed-to-start-elasticsearch-error-code-status-143/298303/1 "2022-02-25T16:22:51Z")

</div>

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 :

```auto

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

```auto
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.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 26, 2022, 11:10am UTC](https://discuss.elastic.co/t/failed-to-start-elasticsearch-error-code-status-143/298303/2 "2022-02-26T11:10:10Z")

</div>

What are the Elasticsearch logs?

---

<div class="post-metadata">

**Author:** ![shiva1](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@shiva1](https://discuss.elastic.co/u/shiva1)\
**Post date:** [February 26, 2022, 11:42am UTC](https://discuss.elastic.co/t/failed-to-start-elasticsearch-error-code-status-143/298303/3 "2022-02-26T11:42:42Z")

</div>

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

---

<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:** [March 26, 2022, 11:43am UTC](https://discuss.elastic.co/t/failed-to-start-elasticsearch-error-code-status-143/298303/4 "2022-03-26T11:43:12Z")

</div>

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