Full logs as in the whole of the journal, or just specific to a process?
The usually happens just out of the blue but has during an upgrade too.
pveversion -v
Interesting. Wonder when those issues were introduced. The number of VMs and HA resources we have has not changed since these issues occurred.
Our issues started mid-Nov.
Good to know this affects everyone equally :-)
We have had discussion on this topic in the past on this forum, It would be nice to get a way to see the softdog status and get logging of when the watchers decide to NOT ping the watchdog for...
Now you mention it, we saw that on our last upgrade.
Nodes drying during apt-get dist-upgrade. Never seen that before. We just thought it was because they were busy.
No entries around the time of the reboot.
Jan 20 04:04:06 hv-5-i corosync[1826]: [QUORUM] Sync members[7]: 1 2 3 4 5 6 7
Jan 20 04:04:06 hv-5-i corosync[1826]: [QUORUM] Sync joined[6]: 1 2 3 4 6 7
Jan 20 04:04:06 hv-5-i corosync[1826]...
Something we've seen in version 9 is an increase in watchdog reboots - in fact from none to many.
Last few entries of the journal show:
```
Jan 22 04:39:09 hv-5-i watchdog-mux[1504]: client watchdog is about to expire
Jan 22 04:39:09 hv-5-i...