Search results

I removed the cephs setup on proxmox1 I have a qdevice for quorum Problem appears resolved. Will monitor

Think an update will resolve this 6 --> 7?

Also note: I moved all VMs to proxmox2, rebooted proxmox1 and all good When I move all VM to proxmox1 and reboot proxmox2. proxmox1 eventually self-reboots

So I stood up corosync on a stand-alone server. didn't help (didn't think it would) I am not running HA yet, but now that I have corosync running I might Last error message in syslog is "trying acquire cfs lock 'file-replication_cfg' ..." I hate to think replication is causing this issue.

Can you point me at the "additional settings" that you are referring to. I am not familiar with these, other than corosync for qurom but I am not running that yet

Unsure, never has that happen in the past. Although VMs are migrating without issue AFAIK. However, I certainly could try killing the cluster and re-establishing the cluster if that seems like a good way forward?

I admin a simple 2 proxmox server setup (I know, 3 would be better) I just got both servers upgraded to 6.4, and I noticed an issue. For explanation sake, let's call them proxmox1 and proxmox 2. When I went to reboot proxmox2, the usual would happen. Any running VMs would power down and the...