Digging deeper than the logs presented in interface's system log

denmalley

New Member
Jan 11, 2025
1
0
1
Hi all, I am a fairly new to pve and linux in general. Running a two-node homelab (so far) with a mini PC and a larger server box that is hosting a NAS VM. Every few weeks, the mini PC goes offline (which I can confirm through the interface on the other node's IP) and I can't seem to remedy through anything but a hard reboot of the machine. Once it comes back up I scroll through the system logs present in the interface and the last few entries prior to reboot show:

Jun 19 21:04:21 pve1 pveproxy[4141029]: worker 1764391 finished
Jun 19 21:04:21 pve1 pveproxy[4141029]: starting 1 worker(s)
Jun 19 21:04:21 pve1 pveproxy[4141029]: worker 1774298 started
Jun 19 21:07:02 pve1 pveproxy[1753021]: worker exit
Jun 19 21:07:02 pve1 pveproxy[4141029]: worker 1753021 finished
Jun 19 21:07:02 pve1 pveproxy[4141029]: starting 1 worker(s)
Jun 19 21:07:02 pve1 pveproxy[4141029]: worker 1774793 started
-- Reboot --

Which is what I recall seeing in the past as well. Searching the Internet for issues related to these log entries doesn't seem to indicate any type of problem that I can find, and these do not give me any sense of an error happening from the way they're written either. I just recently got uptime kuma running and pinging the node plus two VMs - interstingly the VMs went down around 21:10 (three minutes after the last written entries above), but the pve node itself was still pinging successfully until I rebooted. So I am wondering where else I can look within my logs that might help me track down what is happening here?

If I need to, I can move the mini PC closer to my regular PC setup and run it off my switch there until it does it again, and then I'd be able to hook a monitor up to it.

Thanks in advance for any suggestions!