# All host in follower status

**URL:** <https://forum.opennebula.io/t/all-host-in-follower-status/10484>\
**Category:** Operations\
**Created:** [April 16, 2022, 4:52pm UTC](https://forum.opennebula.io/t/all-host-in-follower-status/10484 "2022-04-16T16:52:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nkhromoy](https://avatars.discourse-cdn.com/v4/letter/n/8797f3/32.png) [@nkhromoy](https://forum.opennebula.io/u/nkhromoy)\
**Post date:** [April 16, 2022, 4:52pm UTC](https://forum.opennebula.io/t/all-host-in-follower-status/10484/1 "2022-04-16T16:52:39Z")

</div>

![image](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/8/8b0a2a04634ec7bb44de48d33236bb92be5d5099.jpeg)  
the leader server had disc problem. after disk repair and reboot server we hawe 8 server in state follower, in log error Candidate’s term is outdated, can we manualy update term timestamp?

Sat Apr 16 10:10:14 2022 [Z0][ReM][E]: Req:2720 UID:0 one.zone.voterequest result FAILURE [one.zone.voterequest] Candidate’s term is outdated  
Sat Apr 16 10:10:16 2022 [Z0][RRM][E]: Failed to get heartbeat from leader. Starting election proccess  
Sat Apr 16 10:10:25 2022 [Z0][ReM][E]: Req:6128 UID:0 one.zone.voterequest result FAILURE [one.zone.voterequest] Candidate’s term is outdated  
Sat Apr 16 10:10:27 2022 [Z0][RRM][E]: Failed to get heartbeat from leader. Starting election proccess  
Sat Apr 16 10:10:35 2022 [Z0][ReM][E]: Req:1648 UID:0 one.zone.voterequest result FAILURE [one.zone.voterequest] Candidate’s term is outdated  
Sat Apr 16 10:10:37 2022 [Z0][RRM][E]: Failed to get heartbeat from leader. Starting election proccess  
Sat Apr 16 10:10:45 2022 [Z0][ReM][E]: Req:272 UID:0 one.zone.voterequest result FAILURE [one.zone.voterequest] Candidate’s term is outdated  
Sat Apr 16 10:10:47 2022 [Z0][RRM][E]: Failed to get heartbeat from leader. Starting election proccess

---

<div class="post-metadata">

**Author:** ![nkhromoy](https://avatars.discourse-cdn.com/v4/letter/n/8797f3/32.png) [@nkhromoy](https://forum.opennebula.io/u/nkhromoy)\
**Post date:** [April 16, 2022, 5:05pm UTC](https://forum.opennebula.io/t/all-host-in-follower-status/10484/2 "2022-04-16T17:05:01Z")

</div>

I try some variant for resolve problem and now I’m sure that the problem is in the turn number in the raft, because of the failure it turned out that the version in the database is lower than the version in the raft, need a method how to manually correct the turn number in database or in raft.  
 ![image](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/8/87a05deb5d05247764fdf0e5212b2ff86f46df96.jpeg)

---

<div class="post-metadata">

**Author:** ![cgonzalez](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/cgonzalez/32/7096_2.png) [@cgonzalez](https://forum.opennebula.io/u/cgonzalez)\
**Post date:** [April 18, 2022, 9:33am UTC](https://forum.opennebula.io/t/all-host-in-follower-status/10484/3 "2022-04-18T09:33:48Z")

</div>

It seems that the `TERM` value have reached the `UINT_MAX` limit. This is probably caused by a problem electing a new leader in the cluster. The best way to proceed is probably to select the latest leader node (which should have the latest changes) and rebuild the HA cluster from there.

---

<div class="post-metadata">

**Author:** ![nkhromoy](https://avatars.discourse-cdn.com/v4/letter/n/8797f3/32.png) [@nkhromoy](https://forum.opennebula.io/u/nkhromoy)\
**Post date:** [April 18, 2022, 12:14pm UTC](https://forum.opennebula.io/t/all-host-in-follower-status/10484/4 "2022-04-18T12:14:08Z")

</div>

I fixed problem, take backup database, manualy changed term number in first row in logdb table then restore database to all server and run opennebula.