ERROR: [1] bootstrap checks failed in Elastic Search

While running elastic search via sudo systemctl start elasticsearch.service getting error

Job for elasticsearch.service failed because the control process exited with error code.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.

While running sudo systemctl status elasticsearch.service ,it's displaying

elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-04-10 18:38:40 IST; 12min ago
  Process: 8148 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/ --quiet (code=exited, status=78)
 Main PID: 8148 (code=exited, status=78)

Apr 10 18:38:25 subham systemd[1]: Starting Elasticsearch...
Apr 10 18:38:26 subham elasticsearch[8148]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will li
Apr 10 18:38:40 subham elasticsearch[8148]: ERROR: [1] bootstrap checks failed
Apr 10 18:38:40 subham elasticsearch[8148]: [1]: the default discovery settings are unsuitable for production use; at least one of [discovery.see
Apr 10 18:38:40 subham elasticsearch[8148]: ERROR: Elasticsearch did not exit normally - check the logs at /var/log/elasticsearch/elasticsearch.l
Apr 10 18:38:40 subham systemd[1]: elasticsearch.service: Main process exited, code=exited, status=78/n/a
Apr 10 18:38:40 subham systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Apr 10 18:38:40 subham systemd[1]: Failed to start Elasticsearch.

Below is my elasticsearch.yml:

# ---------------------------------- Cluster -----------------------------------
# Use a descriptive name for your cluster:
# my-application
# ------------------------------------ Node ------------------------------------
# Use a descriptive name for the node:
# node-1
# Add custom attributes to the node:
#node.attr.rack: r1
# ----------------------------------- Paths ------------------------------------
# Path to directory where to store the data (separate multiple locations by comma):
# /var/lib/elasticsearch
# Path to log files:
path.logs: /var/log/elasticsearch
# ----------------------------------- Memory -----------------------------------
# Lock the memory on startup:
#bootstrap.memory_lock: true
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
# Elasticsearch performs poorly when the system is swapping the memory.

OS Version : Ubuntu 18.04
Java Version:

java version "1.8.0_212"
Java(TM) SE Runtime Environment (build 1.8.0_212-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.212-b10, mixed mode)

There should be information about which bootstrap check failed and how to fix this in the Elasticsearch logs. I recommend having a look there.

Could you please send the link here?

Please read

Thanks.The problem is solved.Just Changed to

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