Yes.ok so just to make sure you want me to do apt update && apt dist-upgrade on all my nodes ?
Yes.ok so just to make sure you want me to do apt update && apt dist-upgrade on all my nodes ?
This should not happen. Can you please check the term.log `/var/log/apt/term.log` from the server who gets hangs at upgrade process?I litteraly came back this morning and it's still hanging... but if I open another shell and type apt list --upgradable it says done.
dpkg --configure -a
apt install -f
apt dist-upgrade -y
systemctl reset-failed corosync; systemctl restart corosync
corosync-cfgtool -s
, pvecm status
that the cluster is up and quorate againoh okay, I had it all wrong then. Thanks for the explanation !no, nothing in PVE will change that part of the config on its own (it's pretty much hardcoded to "2" ).
someone with admin level access must have done that at some point in the past (probably confusing version and config_version), which made the config no longer parseable. the next restart of corosync then triggers the error, until then corosync just refuses to reload the faulty config and keeps running with the previously loaded one..