Proxmox restarted at night

[fcarucci]

It's been happening few times, not every night.

I collected this log:
May 20 02:36:32 pve kernel: [211018.253878] nfs: server nas.home.arpa not responding, timed out May 20 02:36:59 pve kernel: [211045.330514] usbhid uas hid usb_storage nvme xhci_pci xhci_pci_renesas nvme_core ahci crc32_pclmul i2c_piix4 nvme_common bnxt_en xhci_hcd libahci igb i2c_algo_bit dca video wmi gpio_amdpt May 20 02:36:59 pve kernel: [211045.334377] RIP: 0010:dev_watchdog+0x212/0x220 May 20 02:36:59 pve kernel: [211045.334705] Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 71 ec 07 01 01 e8 f3 6d f8 ff 44 89 f1 4c 89 e6 48 c7 c7 00 2a 40 8d 48 89 c2 e8 5e 6c 3a ff <0f> 0b e9 22 ff ff ff 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 May 20 02:36:59 pve kernel: [211045.343785] asm_sysvec_apic_timer_interrupt+0x1b/0x20 May 20 02:36:59 pve kernel: [211045.344100] RIP: 0010:cpuidle_enter_state+0xd8/0x6e0 May 20 02:36:59 pve kernel: [211045.345345] RAX: ffff9da728231700 RBX: ffff9d984618a400 RCX: 000000000000001f May 20 02:36:59 pve kernel: [211045.348377] arch_call_rest_init+0xe/0x30 May 20 02:36:59 pve kernel: [211045.348613] start_kernel+0x695/0xb50 May 20 02:36:59 pve kernel: [211045.349071] secondary_startup_64_no_verify+0xe5/0xeb May 20 02:36:59 pve kernel: [211045.349505] ---[ end trace 0000000000000000 ]--- May 20 02:37:25 pve kernel: [211072.206317] nfs: server 10.0.10.241 not responding, timed out May 20 02:39:08 pve kernel: [ 0.000000] Linux version 6.2.11-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC PVE 6.2.11-2 (2023-05-10T09:13Z) () May 20 02:39:08 pve kernel: [ 0.000000] Command line: initrd=\EFI\proxmox\6.2.11-2-pve\initrd.img-6.2.11-2-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs May 20 02:39:08 pve kernel: [ 0.000000] KERNEL supported cpus:

Anyone knows what I should be looking at next to troubleshoot? Thanks!

 

[fcarucci]

And I just had another self reboot which looks different though:

May 20 08:53:33 pve kernel: [22470.796847] vmbr0: port 5(veth1002i0) entered disabled state
May 20 09:37:17 pve kernel: [25095.711643] CR2: 000000c0005e1010 CR3: 0000000bba810000 CR4: 0000000000750ee0
May 20 09:37:17 pve kernel: [25095.712443]  ? __pfx_dev_watchdog+0x10/0x10
May 20 09:37:17 pve kernel: [25095.718898] R10: 0000000000000000 R11: ffff9ed6801d7d28 R12: ffffffff976d45e0
May 20 09:37:17 pve kernel: [25095.719476]  ? cpuidle_enter_state+0xc8/0x6e0
May 20 09:37:17 pve kernel: [25095.720034]  do_idle+0x20a/0x2a0
May 20 09:37:17 pve kernel: [25095.721092]  </TASK>
May 20 09:37:17 pve kernel: [25095.730222] igb 0000:04:00.0 enp4s0: Reset adapter
May 20 09:39:27 pve kernel: [    0.000000] Linux version 6.2.11-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC PVE 6.2.11-2 (2023-05-10T09:13Z) ()

 

[Spoonman2002]

Something "NAS and NFS" at the other end is not responding.
Perhaps pve needs that data for crucial processes.