Version 9.1.1
Lost the quorum node and when to remove it which failed half way. Tried to delete it manually in the /etc/pve/corosync.conf and pretty sure I messed something up.
Cluster information
-------------------
Name: ClusterName
Config Version: 3
Transport: knet
Secure auth: on
Membership information
----------------------
Nodeid Name
Unable to start votequorum status tracking: CS_ERR_BAD_HANDLE
Cluster is able to see the proxmox stats of each node just not able to see the VM's nor replication is able to work. Restoring to the last working config in corosync.conf has failed.
un 03 16:48:35 first pmxcfs[2401095]: [main] notice: resolved node name 'first' to '10.65.5.20' for default node IP address
Jun 03 16:48:35 first pmxcfs[2401095]: [main] notice: resolved node name 'first' to '10.65.5.20' for default node IP address
Jun 03 16:48:35 first pmxcfs[2401095]: [main] notice: unable to acquire pmxcfs lock - trying again
Jun 03 16:48:35 first pmxcfs[2401095]: [main] notice: unable to acquire pmxcfs lock - trying again
systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Trying on 2nd node:
pvecm expected 1
You cannot change expected votes, corosync is not using votequorum
Lost the quorum node and when to remove it which failed half way. Tried to delete it manually in the /etc/pve/corosync.conf and pretty sure I messed something up.
Cluster information
-------------------
Name: ClusterName
Config Version: 3
Transport: knet
Secure auth: on
Membership information
----------------------
Nodeid Name
Unable to start votequorum status tracking: CS_ERR_BAD_HANDLE
Cluster is able to see the proxmox stats of each node just not able to see the VM's nor replication is able to work. Restoring to the last working config in corosync.conf has failed.
un 03 16:48:35 first pmxcfs[2401095]: [main] notice: resolved node name 'first' to '10.65.5.20' for default node IP address
Jun 03 16:48:35 first pmxcfs[2401095]: [main] notice: resolved node name 'first' to '10.65.5.20' for default node IP address
Jun 03 16:48:35 first pmxcfs[2401095]: [main] notice: unable to acquire pmxcfs lock - trying again
Jun 03 16:48:35 first pmxcfs[2401095]: [main] notice: unable to acquire pmxcfs lock - trying again
systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Trying on 2nd node:
pvecm expected 1
You cannot change expected votes, corosync is not using votequorum