Search results

HAHAHA! Yes! I fixed it. What I lack in talent, I make up for in perseverance. OK, here's what to do. I noticed that softdog wasn't starting, and without that, the watchdog-mux.service fails with an 'invalid argument' error message. Without softdog loading, the HA won't work. However, I noticed...

If I do a grep -r softdog /var/log/* on a working node I see this in the logs following a reboot:- syslog:Aug 6 13:03:05 pve-clstr-02 kernel: [ 13.261757] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0) syslog:Aug 6 13:03:05 pve-clstr-02 kernel: [...

Hi, this just happened to me as well. I upgraded three nodes in a cluster as follows. pve6 nautilus -> pve6 octopus -> pve7 octopus. The final step broke the watchdog on one of the nodes. All identical hardware. (SuperMicro). Same HW watchdog setting, disabled. That node doesn't load the softdog...

FWIW here's what I had to mirror to go from ProxMox v6 nautilus to v7 pacific. debmirror /srv/mirror/debian/pve/ --nosource --host=download.proxmox.com --root=debian/pve --dist=buster --section=pve-no-subscription --i18n -arch=amd64 --passive --cleanup --progress --method=http debmirror...