Corosync issue, mismatched config files

[hand363]

Hello,

I had a two node setup with one node having two quorum votes, I then added a third node. At this time there were four quorum votes: 2,1,1 (config_version: 7). When I went to update it to be: 1,1,1 (config_version: 8). After some system restarts for unrelated reasons, each node stop seeing each other, but all accessible individually. I noticed two nodes had corosync version 7 and one node had corosync version 8.

Should I manual update the other two nodes to config_version:8? Or should I change the one node back to config_version 7?
How do I restore my cluster everything is down, thanks in advanced!!!
-Malcolm

 

[homelabenthusiast]

@hand363 you can try to sync your cluster with this (you may need to execute the commands twice):

service pve-cluster stop
service corosync stop
service pvestatd stop
service pveproxy stop
service pvedaemon stop

service pve-cluster start
service corosync start
service pvestatd start
service pveproxy start
service pvedaemon start

 

[hand363]

@hand363 you can try to sync your cluster with this (you may need to execute the commands twice):

service pve-cluster stop
service corosync stop
service pvestatd stop
service pveproxy stop
service pvedaemon stop

service pve-cluster start
service corosync start
service pvestatd start
service pveproxy start
service pvedaemon start

Tried this twice as suggested, no luck getting any of the nodes to see one another.. should I change the corosync.conf files to match before I restart the services?

 

[fabian]

yes, please distribute the updated version to all nodes, then restart corosync on all nodes, and then once the cluster has stabilized, also ensure the same copy of the config is in /etc/pve/corosync.cfg

the next time, please follow https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_edit_corosync_conf when you need to update the config!