Node randomly rebooting. Possible watchdog error?

[domtech05]

Hey guys,
I'm really new to the whole proxmox and networking scene. I have a node set up at the minuet just running a few bits. I have an issue at the moment where the node seems to decide it wants to reboot itself. This reboot will hang until I manually cut power and reboot the system myself. This causes a lot of issues as this hosts my DNS and DHCP servers. I've copied below the part of the log that I think is relevant. Looks like some kind of watchdog (don't know much about this). If anyone can help me diagnose and solve this as well as possibly explain a bit more behind it that would be amazing!
Many thanks, Dom

Jan 17 11:28:23 DSH-SRV-01 kernel: r8169 0000:06:00.0 enp6s0: NETDEV WATCHDOG: CPU: 6: transmit queue 0 timed out 9920 ms
Jan 17 11:28:23 DSH-SRV-01 kernel: r8169 0000:06:00.0 enp6s0: ASPM disabled on Tx timeout
Jan 17 11:28:23 DSH-SRV-01 systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)!
Jan 17 11:28:23 DSH-SRV-01 systemd[1]: systemd-udevd.service: Killing process 465 (systemd-udevd) with signal SIGABRT.
Jan 17 11:29:53 DSH-SRV-01 systemd[1]: systemd-udevd.service: State 'stop-watchdog' timed out. Killing.
Jan 17 11:29:53 DSH-SRV-01 systemd[1]: systemd-udevd.service: Killing process 465 (systemd-udevd) with signal SIGKILL.
Jan 17 11:31:23 DSH-SRV-01 systemd[1]: systemd-udevd.service: Processes still around after SIGKILL. Ignoring.
Jan 17 11:32:53 DSH-SRV-01 systemd[1]: systemd-udevd.service: State 'final-sigterm' timed out. Killing.
Jan 17 11:32:53 DSH-SRV-01 systemd[1]: systemd-udevd.service: Killing process 465 (systemd-udevd) with signal SIGKILL.

 

[waltar]

That's from your allowed powersaving mode "suspend to idle" in your bios cpu settings so change that to just allow S3 powersaving mode. Reason:
Upon wake, when systemd sees the clock has advanced beyond the 3 minute watchdog timeout, it will kill and restart services that have the watchdog enabled.