# Elastic search master issue **URL:** \ **Category:** Elasticsearch\ **Created:** [June 5, 2024, 1:29pm UTC](https://discuss.elastic.co/t/elastic-search-master-issue/360861 "2024-06-05T13:29:36Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\ **Post date:** [June 5, 2024, 1:35pm UTC](https://discuss.elastic.co/t/elastic-search-master-issue/360861/2 "2024-06-05T13:35:29Z")
Hi @gedrasaknagufum.com, Welcome! I see you've posted log snippets without a lot of context. Can you please give more information such as the version of Elasticsearch you are using, how you are running Elasticsearch, what behaviour you are seeing or what issue you are trying to solve? Looking at the logs snippets I see a couple of potential issues: 1. You have an authentication issue: > [@gedrasaknagufum.com](#): > > [o.e.x.s.a.AuthenticationService] [es\_euwest\_prd\_ec2\_2] Authentication of [elastic] was terminated by realm [rese > rved] - failed to authenticate user [elastic] 1. There is an issue finding the master node: > [@gedrasaknagufum.com](#): > > Jun 05 13:00:54 ip-172-31-43-63 elasticsearch[505]: [2024-06-05T13:00:54,768][WARN][o.e.c.c.ClusterFormationFailureHelper] [es\_euwest\_prd\_ec2\_2] master not discovered or elected yet If it's your first time spinning up the cluster you may need to set property `cluster.initial_master_nodes` [as covered here](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet-an-election-requires-at-least-2-nodes-with-ids-elk-stack-docker-swarm/325548). Alternatively I would look at [this article](https://opster.com/guides/elasticsearch/operations/elasticsearch-master-node-not-discovered/) which discusses some potential causes. Hope that helps! --- _[View the full topic](https://discuss.elastic.co/t/elastic-search-master-issue/360861)._