[pve-devel] [PATCH ha-manager 3/3] watchdog: sync journal after sending expiration related messages
Maximiliano Sandoval
m.sandoval at proxmox.com
Mon May 19 15:09:35 CEST 2025
One sync comes after warning that the watchdog is about to expire, and a
second right after the watchdog expires.
To maximize the chances the log will contain entries relevant to a fence
event. This would be extremely useful for detecting whether a node
fenced.
Signed-off-by: Maximiliano Sandoval <m.sandoval at proxmox.com>
---
src/watchdog-mux.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/watchdog-mux.c b/src/watchdog-mux.c
index e14c768..8669b10 100644
--- a/src/watchdog-mux.c
+++ b/src/watchdog-mux.c
@@ -268,11 +268,13 @@ main(void)
) {
client_list[i].warning_state = WARNING_ISSUED;
fprintf(stderr, "client watchdog is about to expire\n");
+ sync_journal_unsafe();
}
if ((ctime - client_list[i].time) > client_watchdog_timeout) {
update_watchdog = 0;
fprintf(stderr, "client watchdog expired - disable watchdog updates\n");
+ sync_journal_unsafe();
}
}
}
--
2.39.5
More information about the pve-devel
mailing list