Bootstrap check failure

I tried using ES on AWS server of ubutu image, and modify the elasticsearch.yml file of node, discovery.seed_hosts, master node . But got error with bootstrap node validation exception
and it shows "at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured" which i already did. Thank youu

Below is my elasticsearch.yml configuration
cluster.name: es-demo
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: 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):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
network.host: ip1

 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 ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
#The default list of hosts is ["127.0.0.1", "[::1]"]
#
discovery.seed_hosts: ["ip1(the ip of 1st node)", "ip2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: ["ip1"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
#
node.master: true

Can you please post the entire Elasticsearch log from startup to this error?

@warkolm Hmm it is already resolved anyway, thank you

Can you share what it was, it might help someone in future.

1 Like

hmm, sorry because i didnt copy the whole log and i think the problem have to do with the node configuration in elasticsearch.yml file

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