# Failed to determine new Master

**URL:** <https://forum.yugabyte.com/t/failed-to-determine-new-master/2622>\
**Category:** General\
**Created:** [April 24, 2024, 7:06pm UTC](https://forum.yugabyte.com/t/failed-to-determine-new-master/2622 "2024-04-24T19:06:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![parvez](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@parvez](https://forum.yugabyte.com/u/parvez)\
**Post date:** [April 24, 2024, 7:06pm UTC](https://forum.yugabyte.com/t/failed-to-determine-new-master/2622/1 "2024-04-24T19:06:12Z")

</div>

We have 3 YB Nodes, each node is running master and t-server services. Initially, node01 was the leader, at some point node 3 got elected as a leader but the rest of the nodes are complaining about failing to determine a new master. How to resolve such issues?

ErrorLog:  
W0424 17:13:15.740830 24645 client\_master\_rpc.cc:68] Failed to determine new Master: Timed out (yb/rpc/rpc.cc:220): GetLeaderMasterRpc(addrs: [node02:9090, node01:9090], num\_attempts: 98) passed its deadline 809790.614s (passed: 5.064s): Not found (yb/master/master\_rpc.cc:286): no leader found: GetLeaderMasterRpc(addrs: [node02:9090, node01:9090], num\_attempts: 1)

---

<div class="post-metadata">

**Author:** ![dorian\_yugabyte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/dorian_yugabyte/32/206_2.png) [@dorian\_yugabyte](https://forum.yugabyte.com/u/dorian_yugabyte)\
**Post date:** [April 25, 2024, 6:28am UTC](https://forum.yugabyte.com/t/failed-to-determine-new-master/2622/2 "2024-04-25T06:28:44Z")

</div>

Hi @parvez

Can you upload more logs from these servers?  
Do queries run ok from them?

---

<div class="post-metadata">

**Author:** ![parvez](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@parvez](https://forum.yugabyte.com/u/parvez)\
**Post date:** [May 8, 2024, 4:20am UTC](https://forum.yugabyte.com/t/failed-to-determine-new-master/2622/3 "2024-05-08T04:20:39Z")

</div>

Hi @dorian_yugabyte, ysql port got stuck due to network blips and name resolution failure. DB operations were working. Rolling-Restart of yugabyted service fixed the connectivity issue. Thank you for your response!