# Difficulties forming a new Elastic Stack possibly because of Elasticsearch discovery procedure **URL:** \ **Category:** Elasticsearch\ **Created:** [February 9, 2020, 9:22pm UTC](https://discuss.elastic.co/t/difficulties-forming-a-new-elastic-stack-possibly-because-of-elasticsearch-discovery-procedure/218482 "2020-02-09T21:22:20Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![pwh589](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@pwh589](https://discuss.elastic.co/u/pwh589)\ **Post date:** [February 9, 2020, 9:22pm UTC](https://discuss.elastic.co/t/difficulties-forming-a-new-elastic-stack-possibly-because-of-elasticsearch-discovery-procedure/218482/1 "2020-02-09T21:22:20Z")
Hi, I am trying to form an Elastic Stack made of a single RHEL 7.4 Elasticsearch node, a RHEL 7.4 Kibana node, and RHEL 7.4 Logstash node, all 7.5.2 (current version as of now). For some reason, in 7.5.2 Elasticsearch wont work for me. Every time I start it up, it tries to find nodes for a cluster, while I don't want a cluster at all, and I've set "discovery.seed\_hosts" to "" in the config file . Its weird because in previous versions it worked fine for me, and it didn't search for a master node to form a cluster. Because of this, I believe, Kibana Isn't working as well - as I try to run it, it writes "License information could not be obtained from Elasticsearch for the [data] cluster." mostly, and once in a few messages, "Unable to connect to Elasticsearch. Error: [master\_not\_discovered\_exception] null". How can I fix this? I though about completely disabling the discovery check but I don't know how to... Thank you for your help. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [February 9, 2020, 11:16pm UTC](https://discuss.elastic.co/t/difficulties-forming-a-new-elastic-stack-possibly-because-of-elasticsearch-discovery-procedure/218482/2 "2020-02-09T23:16:24Z")
Did you set [`cluster.initial_master_nodes`](https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-settings.html#initial_master_nodes)? You need to do so even for a single node cluster. Setting `discovery.seed_hosts: []` is not sufficient; there are situations where this setting might be empty even though there are multiple nodes. `cluster.initial_master_nodes` determines the nodes in the initial cluster. ---
**Author:** ![pwh589](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@pwh589](https://discuss.elastic.co/u/pwh589)\ **Post date:** [February 9, 2020, 11:48pm UTC](https://discuss.elastic.co/t/difficulties-forming-a-new-elastic-stack-possibly-because-of-elasticsearch-discovery-procedure/218482/3 "2020-02-09T23:48:35Z")
Thank you very much for your answer! I've set "cluster.initial\_master\_nodes" to the node's name (by default the host name), and now Elasticsearch seems to work!. Now Kibana says the user that I use to run it don't have sufficient privileges to access a file, but I think I just might fix it myself. Thanks again! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 8, 2020, 11:48pm UTC](https://discuss.elastic.co/t/difficulties-forming-a-new-elastic-stack-possibly-because-of-elasticsearch-discovery-procedure/218482/4 "2020-03-08T23:48:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.