vzdump hanging is the observable issue, but I believe the root cause has something to do with acquiring locks.
I have a 3 node cluster, and the main node with the GUI seems to be working fine. The other two nodes are not reporting any status back to the gui.
I've restarted pvestatd, and looked at /etc/pve/.rrd, and no VMs from the two broken nodes are listed there.
I'd prefer to not reboot these nodes, as the VMs are running properly.
Any vzdump simply hangs forever. They are trying to write to an NFS mounted directory that I have verified is properly mounted, and has plenty of disk space available.
What else can I try to resolve this issue? What other information can I provide to help solve this? I've considered restarting the corosync service, but I've never done that before, and I'm not sure if it's a good idea.
Thanks in advance
Tony Nelson
Starpoint Solutions
I have a 3 node cluster, and the main node with the GUI seems to be working fine. The other two nodes are not reporting any status back to the gui.
I've restarted pvestatd, and looked at /etc/pve/.rrd, and no VMs from the two broken nodes are listed there.
I'd prefer to not reboot these nodes, as the VMs are running properly.
Any vzdump simply hangs forever. They are trying to write to an NFS mounted directory that I have verified is properly mounted, and has plenty of disk space available.
What else can I try to resolve this issue? What other information can I provide to help solve this? I've considered restarting the corosync service, but I've never done that before, and I'm not sure if it's a good idea.
Thanks in advance
Tony Nelson
Starpoint Solutions