Need some assistance here, got some problems after adding a new node to the cluster.
1. Two nodes, vm1 & vm3 was powered up and working. One node, vm2, was shut down.
2. Added a new node, vm4, to the cluster without problems
3. Powered on the shut down node, and it refuses to join the cluster
vm3 & vm4 runs Proxmoc 4.2
vm1 & vm2 runs Proxmox 4.1
On the failed node I can see that the corosync.conf has not been updated with the new host.
Checking the log with journalctl, I can see that corosync starts up and connects to the initial cluster member, but fails shortly after. One interesting line in the log reads:
[CMAP] Recieved config version (6) is different than my config version (5)! Exiting
Could this be because of the different proxmox versions ? Seems strange since the three working nodes have mixed versions.
Is there some way to force the failed node to resync the corosync config ?
1. Two nodes, vm1 & vm3 was powered up and working. One node, vm2, was shut down.
2. Added a new node, vm4, to the cluster without problems
3. Powered on the shut down node, and it refuses to join the cluster
vm3 & vm4 runs Proxmoc 4.2
vm1 & vm2 runs Proxmox 4.1
On the failed node I can see that the corosync.conf has not been updated with the new host.
Checking the log with journalctl, I can see that corosync starts up and connects to the initial cluster member, but fails shortly after. One interesting line in the log reads:
[CMAP] Recieved config version (6) is different than my config version (5)! Exiting
Could this be because of the different proxmox versions ? Seems strange since the three working nodes have mixed versions.
Is there some way to force the failed node to resync the corosync config ?