All nodes left the cluster in the early morning
Oct 27 03:53:51 corosync[1602]: [QUORUM] Sync members[1]: 2
Oct 27 03:53:51 corosync[1602]: [QUORUM] Sync left[3]: 1 3 4
Oct 27 03:53:51 corosync[1602]: [TOTEM ] A new membership (2.ba4) was...
These are the errors showing on the 3 other nodes
pvescheduler[1505772]: jobs: cfs-lock 'file-jobs_cfg' error: no quorum!
pvescheduler[1505771]: replication: cfs-lock 'file-replication_cfg' error: no quorum!
On the node I updated, just lots of...
I have a 4 node cluster running Proxmox 9. I just updated one node with the latest packages and kernel. I spotted something odd and realised that the cluster had no quorum. I don't know if that was due to the upgrade or whether it happed...
No difference. I had initially created the fresh container with nesting enabled (by mistake as it doesn't really need it). But the old containers work without nesting.
Don't think it's the config. It matches the old container details.
arch: amd64
cores: 2
hostname: test
memory: 2048
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.0.1,hwaddr=XX:XX:XX:XX:XX:XX,ip=192.168.0.29/24,type=veth
onboot: 1
ostype...
A VM may be an option. What I've done now is take a backup and restore of the original working container to a new one. This works fine even on a different physical server.
The one difference I can spot is that the fresh install is running...
Hi,
I am running the latest Proxmox v9 with a container running Debian 9 (yes it's very old, running an application which is currently being upgraded).
It was originally created more than 6 years ago and is running fine. I've now created a new...