# Elastic search automatically stopped after

**URL:** <https://discuss.elastic.co/t/elastic-search-automatically-stopped-after/196797>\
**Category:** Elasticsearch\
**Created:** [August 26, 2019, 2:47pm UTC](https://discuss.elastic.co/t/elastic-search-automatically-stopped-after/196797 "2019-08-26T14:47:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balaji\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/b/9dc877/32.png) [@Balaji\_Ramachandran](https://discuss.elastic.co/u/Balaji_Ramachandran)\
**Post date:** [August 26, 2019, 2:47pm UTC](https://discuss.elastic.co/t/elastic-search-automatically-stopped-after/196797/1 "2019-08-26T14:47:28Z")

</div>

Hi,

We are trying to enable elasticsearch 7.3 using ubuntu 16.04, but after 30 seconds, the service gets automatically stopped. This issue happens while setting up to a specific bind network address to 0.0.0.0. Here I have shared the current elasticsearch .yml configuration file and status.

We made some changes in the .yml configuration file

```
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 0.0.0.0
#
# Set a custom port for HTTP:
#
http.port: 9200
#

```

and the status

```
 elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-08-26 09:39:21 EST; 5min ago
     Docs: http://www.elastic.co
  Process: 881 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=78)
 Main PID: 881 (code=exited, status=78)

Aug 26 09:39:09 p2e systemd[1]: Started Elasticsearch.
Aug 26 09:39:10 p2e elasticsearch[881]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be r
Aug 26 09:39:21 p2e systemd[1]: elasticsearch.service: Main process exited, code=exited, status=78/n/a
Aug 26 09:39:21 p2e systemd[1]: elasticsearch.service: Unit entered failed state.
Aug 26 09:39:21 p2e systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
```

---

<div class="post-metadata">

**Author:** ![mbelaloui](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbelaloui/32/49140_2.png) [@mbelaloui](https://discuss.elastic.co/u/mbelaloui)\
**Post date:** [August 26, 2019, 3:04pm UTC](https://discuss.elastic.co/t/elastic-search-automatically-stopped-after/196797/2 "2019-08-26T15:04:32Z")

</div>

Hello @Balaji_Ramachandran,

In production mode, any bootstrap checks that fail will cause Elasticsearch to refuse to start.

When you change the `network.host` the elasticsearch node assumes that you are moving from development mode to production mode, you should see in the log a msg that say you shloud configure one of the bootstrap options.

Mehdi.

---

<div class="post-metadata">

**Author:** ![mbelaloui](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbelaloui/32/49140_2.png) [@mbelaloui](https://discuss.elastic.co/u/mbelaloui)\
**Post date:** [August 26, 2019, 3:05pm UTC](https://discuss.elastic.co/t/elastic-search-automatically-stopped-after/196797/3 "2019-08-26T15:05:44Z")

</div>

For more informations [https://www.elastic.co/guide/en/elasticsearch/reference/current/\_discovery\_configuration\_check.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/_discovery_configuration_check.html)

Mehdi.

---

<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:** [September 23, 2019, 3:05pm UTC](https://discuss.elastic.co/t/elastic-search-automatically-stopped-after/196797/4 "2019-09-23T15:05:46Z")

</div>

Closed on September 23, 2019, 3:05pm UTC

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