On Fri, 04 Jul 2025 15:38:56 +0200, Maximiliano Sandoval wrote: > Without a clear-cut message in the log, it is very hard to provide a > definitive > answer to whether a host fenced or not. In some cases the journal on the disk > can be missing up to 2 minutes since its last logged entry and the time where > another node detects the corosync link is down, with such a gap, the fenced > node > would not even record that it lost conenction and it is not possible to > fully-determine if the node was fenced or not. > > [...]
Applied, thanks! [1/6] watchdog-mux: Use #define for 60s timeout [2/6] watchdog-mux: split if block in two if blocks [3/6] watchdog-mux: warn when about to expire [4/6] watchdog-mux: sync journal right after fence warning [5/6] watchdog-mux: break out of loop when updates are disabled [6/6] watchdog-mux: Remove wrapping if guard _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
