Search results

I think you are right Fabian. It was up for 128 days prior, a testament to the reliability of Proxmox and Linux in general.

All plausible Jonathon. I am not a VI master, so I would not have used the 0 like you said. However I just learnt a new vi command. I may have set it to 20 instead of the config_version as you said. I am just happy it is all fixed. The problem was compounded as it only happened after the update.

Good news (for me at least). I have it all stable with the correct version. Servers boot properly. Thank you to Dietmar and GadgetPig. Your feedback led me to the right answer. When it was up with all three nodes I was able to edit /etc/pve/corosync.conf and the new version propagated to all...

UPDATE: I rebooted pve1 again and it is back to not starting. I suspect that what happens is I change corosync file version to 2. When I reboot it can start corosync, but it then replicates corosync.conf from the other HVs (pve2 is the master) and changes to 20. When it reboots after that it is...

Thanks for that confirmation. I'm obviously doing it all wrong because I change the version to 2 and when I restart corosync it changes back to 20. I tried taking pve3 offline with pmxcfs -l and it rebooted, taking all the VMs with it. When it came back up it was back to 20 in the version. I...

Dietmar, I just changed pve1 corosync.conf to fix the version and it started immediately. However, in the web interface the other hvs don't see it as active. Should I edit the corosync files on all HVs and restart corosync?

Yes but it was always there on all three HVs I think, unless it changed after the upgrade to pve1. The timestamp on the file is from the last reboot. -rw-r--r-- 1 root root 520 Dec 16 14:06 corosync.conf If I change it, could it bring the other nodes down. As it is not the master will it...

And from pve2 for context. root@pve2:~# cat /etc/corosync/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: pve1 nodeid: 3 quorum_votes: 1 ring0_addr: pve1 } node { name: pve2 nodeid: 1 quorum_votes: 1 ring0_addr: pve2 }...

Sure. 192.168.44.1 is pve2 root@pve1:~# cat /etc/corosync/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: pve1 nodeid: 3 quorum_votes: 1 ring0_addr: pve1 } node { name: pve2 nodeid: 1 quorum_votes: 1 ring0_addr: pve2 }...

I have a cluster of 3 nodes. They were all running happily as below. root@pve2:/etc/pve# pveversion -v proxmox-ve: 5.1-30 (running kernel: 4.13.8-3-pve) pve-manager: 5.1-38 (running version: 5.1-38/1e9bc777) pve-kernel-4.10.17-2-pve: 4.10.17-20 pve-kernel-4.13.8-3-pve: 4.13.8-30...