Recent content by deniswitt

I have the exact same issue. This makes Proxmox 6, Debian 10 and DRBD completely incompatible. Unfortunately Proxmox 6 depends on Debian 10. There seems to be an patch for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1866458 Maybe you can contact Linbit to backport this...

Hi baerm, unfortunately "ignore" doesn't work: service 'vm:102' in error state, must be disabled and fixed first (500) Same for migration: Requesting HA migration for VM 111 to node hosting2 service 'vm:111' in error state, must be disabled and fixed first TASK ERROR: command 'ha-manager...

Hi baerm, we are using 4.13 as well. ha-manager doesn't seem to help, as the only working option is "disabled", which will stop the machines which is what we try to avoid. Thanks anyway.

Hi Belokan, the funny thing is, the backup error was for the group testing, the errors are reported for the group hosting. Anyway, your proposed solution works fine, but is a pain in the ass when you have more than 10 VMs. Is there a command line solution? pvecm only seems to have the option...

Hi, the HA state for all our VMs on our proxmox test environment is "error" since this morning and the backup has been failed. The odd part, als VMs are running perfectly. The state for our containers are fine. How can I remove the error state without restarting the VMs? And more importantly...

Sure, but Murphy... (Corosync didn't crashed once, yet, it was killed on purpose to see what happens, as said, I'm evaluating at the moment.) Would it be save to monitor Corosync with an systemd watchdog, or via supervisord to restart it in case of errors or might this interfere with the...

Hi, I'm currently evaluate Proxmox for a 5 Node HA-Setup. During some tests I noticed that Proxmox isn't able to live migrate VMs/Container when Corosync crashes on one node the VMs/CTs are running on. Instead the Node gets restarted and the VMs/CTs are started on another node (after quite some...