05.09.2019 · Oct 25, 2016. #4. Hi, we are running a proxmox cluster for near a year without trouble (also an upgrade from 3.4 to 4.1) Last august we have upgraded successfully the cluster to 4.2-17 from previous 4.1. From that time in two months we have experienced four trouble very similar to the one described above.
After physical reboot, node 1 came online, but node 2 never did. It seems I can ssh into the second node, but it is not detected on web interface, and is inaccessible via web interface. Based on some troubleshooting/googling, I attempted to run the steps: service corosync restart. service pve-cluster restart. service pveproxy restart
One node goes offline. I have a Promox/Ceph cluster with 7 nodes, I just did a fresh install over the weekend. Yesterday, when logged into Node 1, any time I tried to interact with Node 2 I got a timeout. I tried logging directly into Node 2, but the UI wouldn’t load. When whole time Ceph didn’t throw any errors.
the nodes as 'offline' and it reflects below (see: Loading Image... ) VM's are running perfectly on the 'kappa' node as I had them all on there. before, but as the nodes are showing offline I cannot create a new VM as it. tells me the specified node is offline. If I navigate to the 'zeus' web panel, everything above is reflected apart.
19.03.2021 · I'm testing the Backup Server at the moment and somehow 2 of 3 PVE test nodes lost the connection - the datastore just seems to be offline (but can be pinged from the PVE nodes, so it's not a network issue).
nodes seem offline, can't communicate, VM's are running. (solved) I've got a bit of a serious issue here. in the middle of upgrading some VM's and suddenly proxmox just...dies. I'm trying to backup some vm's but the backup storage isn't loading, the drop down window where you select where to backup to just spins. the VM's are all up but i can't ...