Elastic search automatically stopped after


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 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):
# 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'.

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.


For more informations https://www.elastic.co/guide/en/elasticsearch/reference/current/_discovery_configuration_check.html


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