[SOLVED] Second server in HA reboots when loosing quorum?

lela810

New Member
Aug 17, 2022
6
0
1
Switzerland
Hello everyone


I wanted to try the new CRS features and added some machines and my two servers into an HA (I know, only 2 votes and so on).
But still wanted to try it.

Did some updates on one server, migrated all the VMs to the second server and pressed reboot on the first one.
Just a minute or so later, the second PVE SERVER reboots by itself.
I've attached the system logs, where you can see it losing quorum and some time later rebooting.

Normal behavior? Hope not...
Thanks in advance, for some advice :)
 

Attachments

  • pve log.txt
    2.5 KB · Views: 3
Fencing can reboot nodes when quorum is lost. Thats a feature, not a bug. And yes, a HA cluster needs quorum which isn't possible with just 2 nodes. At least add a SBC/Thin-Client/NAS as a qdevice for a third vote:
https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_external_vote_support

https://pve.proxmox.com/wiki/High_Availability#_how_it_works
When a cluster member determines that it is no longer in the cluster quorum, the LRM waits for a new quorum to form. As long as there is no quorum the node cannot reset the watchdog. This will trigger a reboot after the watchdog times out (this happens after 60 seconds).
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!