Rando Crash?

[Smash_Override]

TLDR: Proxmox GUI & CLI non responsive. Rebooted, all is working again. Where should I look to figure out what happened?

I understand there are multiple logs that I could look through, but not sure where to start? I am running win serv 2022 on a VM hosting PLEX so nothing crazy. I couldn't get into plex or the PM Gui. I could ping the VM, but not PM. I tried getting in through the CLI direct off the box and after typing in the UN, the screen when black with not output. Where should I be looking to figure out what happened?

Thanks
Smash

PM:8.2.7
MB: asrock x399 fatality
Processor: AMD Ryzen 2990wx (32 Cores, 64 threads)
Processor Cooler: Noctua tower cooler
RAM: 96 GB DDR4 3200 because this Asrock board sucks and won't recognize a full 128 GB. Known issue.

 

[Moayad]

Hi,

The journalctl/syslog should give you what cause the issue. You can generate the syslog in a specific time using the following command:

journalctl --since '2024-11-11 00:00:00' --until '2024-11-11 08:50:15' > /tmp/$(hostname)-syslog.txt

You may have to edit the date/time in the above command for the crash time or before in 30~ minutes.

 

[Smash_Override]

By any chance, would someone lend me a brain byte and help me understand the syslog? It appears the system crashed at Nov 12 08:02:11. I don't know what I should be looking for? Also, why is this thing hitting gmail servers? I also just ran the system upgrade through the gui: apt-get dist-upgrade. Looks like it upgraded the kernel. Giving it a reboot and lets see what happens.

Thanks much!!!
The Ignorant One

 

[Moayad]

Thank you for the syslog!

In the syslog I see the following:

Nov 12 08:02:11 pve kernel: perf: interrupt took too long (3962 > 3942), lowering kernel.perf_event_max_sample_rate to 50000

Before the reboot, this message interrupt took too long indicate CPU interrupt delays, which can imply performance or system stress that could do a crash. I would check the usage of I/O, CPU, Memory at that time.