On Tue, 2017-05-16 at 10:31 +0200, Thomas Lamprecht wrote: > Honestly, I would just stop the HA services (this marks the VMs > currently under > HA) and then do a clean restart of the pve-cluster corosync services, > I'd do this for all nodes but not all at the same time :) This is as > safe as it > can get, no VM should be interrupted, and I expected that even if we > know the > full trigger of this it will result in the same action.
Sorry, forgot to let everybody know. I dist-upgraded the cluster last week, which restarted clustering and that 'fixed' everything. Thanks for your support. -- Kerio Operator in de Cloud? https://www.kerioindecloud.nl/ Mark Schouten | Tuxis Internet Engineering KvK: 61527076 | http://www.tuxis.nl/ T: 0318 200208 | [email protected] _______________________________________________ pve-user mailing list [email protected] https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
