http://192.168.180.206:8001/ 2026-05-14T10:46:27+00:00 http://192.168.180.206:8001/ http://192.168.180.206:8001/_media/wiki:dokuwiki.svg text/html 2023-01-31T07:35:25+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/vm:proxmox:ha:dsiable_fencing?rev=1675150525&do=diff Disable fencing Sometimes, when Proxmox is used in not optimal (cheap) configutation, cluster can fence good node and cause it to reboot. Possible causes: * use only one network - corosync requires low latencies * overloaded CPU pvecm status Cluster information ------------------- Name: example Config Version: 11 Transport: knet Secure auth: on Quorum information ------------------ Date: Mon Jan 30 11:42:01 2023 Quorum provider: corosync_votequoru… text/html 2021-12-28T13:20:54+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/vm:proxmox:ha:watchdog?rev=1640697654&do=diff Proxmox is using watchdog-mux. It is using /dev/watchdog and exposes watchdog service to multiple daemons using socket: root@pve4:~# lsof -n 2>&1 | grep watch watchdog- 3923 root txt REG 0,26 14728 75245 /usr/sbin/watchdog-mux watchdog- 3923 root 1u unix 0x000000006ba3be2b 0t0 40514 type=STREAM watchdog- 3923 root 2u unix 0x000000006ba3be2b …