Proxmox host locking up

[andcbii]

Just recently my proxmox host keeps looking up. This started around early July and has happed 2-3 times since then (maybe 1 every 2-3 weeks). The host is totally unresponsive. I can not ping it or SSH into it. The display also stops working so I can not access it directly either. This is the system logs from the last time it happened. Where should I be looking to see what might be causing the issue?

Aug 03 11:10:45 proxmox1 pveproxy[1391293]: worker exit
Aug 03 11:10:45 proxmox1 pveproxy[2420]: worker 1391293 finished
Aug 03 11:10:45 proxmox1 pveproxy[2420]: starting 1 worker(s)
Aug 03 11:10:45 proxmox1 pveproxy[2420]: worker 1417507 started
Aug 03 11:11:41 proxmox1 pveproxy[1396311]: worker exit
Aug 03 11:11:41 proxmox1 pveproxy[2420]: worker 1396311 finished
Aug 03 11:11:41 proxmox1 pveproxy[2420]: starting 1 worker(s)
Aug 03 11:11:41 proxmox1 pveproxy[2420]: worker 1417982 started
Aug 03 11:14:22 proxmox1 postfix/qmgr[2164]: 7D04910707: from=<>, size=2584, nrcpt=1 (queue active)
Aug 03 11:14:22 proxmox1 postfix/error[1419299]: 7D04910707: to=<admin@alderaan.co>, relay=none, delay=247966, delays=247966/0.01/0/0.01, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to alt1.aspmx.l.google.com[2607:f8b0:400d:c0e::1a]:25: Network is unreachable)
Aug 03 11:17:01 proxmox1 CRON[1420611]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Aug 03 11:17:01 proxmox1 CRON[1420612]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 03 11:17:01 proxmox1 CRON[1420611]: pam_unix(cron:session): session closed for user root
-- Reboot --
Aug 03 19:40:44 proxmox1 kernel: Linux version 6.8.12-12-pve (build@proxmox) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-12 (2025-07-14T13:20Z) ()
Aug 03 19:40:44 proxmox1 kernel: Command line: initrd=\EFI\proxmox\6.8.12-12-pve\initrd.img-6.8.12-12-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs
Aug 03 19:40:44 proxmox1 kernel: KERNEL supported cpus:
Aug 03 19:40:44 proxmox1 kernel:   Intel GenuineIntel
Aug 03 19:40:44 proxmox1 kernel:   AMD AuthenticAMD
Aug 03 19:40:44 proxmox1 kernel:   Hygon HygonGenuine
Aug 03 19:40:44 proxmox1 kernel:   Centaur CentaurHauls
Aug 03 19:40:44 proxmox1 kernel:   zhaoxin   Shanghai
Aug 03 19:40:44 proxmox1 kernel: BIOS-provided physical RAM map:
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d1efff] usable
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x0000000009d1f000-0x0000000009ffffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x000000000a20e000-0x00000000c310cfff] usable
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000c310d000-0x00000000c310dfff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000c310e000-0x00000000ca17afff] usable
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000ca17b000-0x00000000ca52efff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000ca52f000-0x00000000ca692fff] ACPI data
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000ca693000-0x00000000ca9eafff] ACPI NVS
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000ca9eb000-0x00000000cb9fefff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000cb9ff000-0x00000000ccffffff] usable
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000cd000000-0x00000000cfffffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fd400000-0x00000000fd5fffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000202f2fffff] usable
Aug 03 19:40:44 proxmox1 kernel: BIOS-e820: [mem 0x000000202f300000-0x000000202fffffff] reserved
Aug 03 19:40:44 proxmox1 kernel: NX (Execute Disable) protection: active
Aug 03 19:40:44 proxmox1 kernel: APIC: Static calls initialized

 

[emunt6]

Hi!

Experience from previous same topics, the solutions from the past ( check all):
1., - Hardware Problem ( check components, manufacturer websites for RMA/defects ),
2., - Upgrade motherboard BIOS ( check manufacturer websites for BIOS updates and components firmware updates),
3., - Disable All PowerSaving options (C-State, Hibernation, Change PowerManagement settings to "High Perfomance mode") in BIOS/Hardware ( CPU, NVME ).
4., - Disable All Hyperthreading/SMT options in BIOS, set to static cores.

Above all, the other problem could be the hardware is "not server grade",
so manufacturer not built/implement component as it should be - so other software workaround ( kernel command line parameters ) needed.

So for help, I bet your problem is "Option 3" ( CPU/Hardware going to sleep, cannot recover ).

 

[andcbii]

This ended up being an issue with a network card. took out the intel x520-da2 that i had installed an the issue went way.