quorum

Dear, We try to create a cluster, when we add the second node, we receive the following errors: From the web interface: cluster not ready - no quorum? From command line where we created the cluster on: Quorum information ------------------ Date: Thu Dec 29 12:58:38 2016 Quorum...

Hi is it a problem having an even node number (4,6,8,....) for quorum? we have a 4 node cluster where nodes are rebooting erratic (when very high load I guess...) if yes, is incrementing quorum_votes: 1 to quorum_votes: 2 on one node the solution? regards Peter

I have a cluster with 2 nodes, and as configured by default, they both have 1 vote and will not reach quorum: Votequorum information ---------------------- Expected votes: 2 Highest expected: 2 Total votes: 1 Quorum: 2 Activity blocked Flags: I've tried stopping the...

After updating a two node cluster to 4.3, I have rebooted the nodes one by one (not at the same time). After reboot none of the VM's were running, trying to start them on any node gave a cluster error: root@proxmox2:~# qm start 111 cluster not ready - no quorum? Checking the cluster showed...

Hi Guys, Need help setting up VM to start at boot but after quorum is reached. I often find VM does not start at boot due to quorum is not reached yet. I run 3 PVE 4.3 nodes in cluster with HA enabled for some VMs on top of GlusterFS, and non-HA VMs on top of ZFS RAID10, and 4x 10GbE LACP...

Hi all, we have cluster configuration which consists in a 2 nodes - unicast udpu (multicast not available). The cluster is up and running, I added and removed a test machine from HA. The question is, we have the following output for "ha-manager status", on this cluster, two node up and running...

Hi all, Firstly, a little background so you know where I am: I used to run two physical CentOS servers at home as active/standby for a few personal projects. The active server ran mail, ownCloud, databases etc etc, and each night the active server sent a WoL to the standby and rsync'd...

Hello all, I've just upgraded our 3-server cluster from last 3.x version to latest 4.x (Community Subscription) without any problems (almost). As we're running our primary firewall virtualized as well in Proxmox we changed the clusters nodes gateways (vmbr0 => eth4) to a physical firewall in...

Following the guides to remove a node from a cluster, i shutdown and deleted the node that was to be shutdown as per the instructions in the wiki (following the WARNING) that it should NOT ever go online again because that would mess upp the cluster. Now i can't write to /etc/pve at all and if...