New Proxmox install, crash, reboot, why?

[Spodster]

I have a fairly new to me (eBay) NUC that seems to work perfectly ok aside from the fact it seems to go into a suspend, hibernate, restart process or Proxmox seems to crash when left.

Scenario is If left for a few hours I can come back to it and there's no HDMI output to the screen.
NUC Power light is lit permanently like it's on.
Wiggle mouse give the keyboard a poke and a few seconds later you see the NUC power light go off, hear the fans spin up, you see the BIOS screen, Grub menu?, Proxmox start and it boots up.

In the syslog from GUI I can see a reboot message, anywhere I can go for further info?

Nov 05 11:17:01 proxmox CRON[32377]: pam_unix(cron:session): session closed for user root
Nov 05 12:02:16 proxmox smartd[656]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 79
Nov 05 12:17:01 proxmox CRON[40726]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 05 12:17:01 proxmox CRON[40727]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 05 12:17:01 proxmox CRON[40726]: pam_unix(cron:session): session closed for user root
-- Reboot --
Nov 05 13:07:06 proxmox kernel: Linux version 6.2.16-19-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-19 (2023-10-24T12:07Z) ()
Nov 05 13:07:06 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-19-pve root=/dev/mapper/pve-root ro quiet
Nov 05 13:07:06 proxmox kernel: KERNEL supported cpus:
Nov 05 13:07:06 proxmox kernel: Intel GenuineIntel
Nov 05 13:07:06 proxmox kernel: AMD AuthenticAMD
Nov 05 13:07:06 proxmox kernel: Hygon HygonGenuine
Nov 05 13:07:06 proxmox kernel: Centaur CentaurHauls
Nov 05 13:07:06 proxmox kernel: zhaoxin Shanghai
Nov 05 13:07:06 proxmox kernel: BIOS-provided physical RAM map:
Nov 05 13:07:06 proxmox kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
etc......



root@proxmox:~# last
root pts/0 Sun Nov 5 21:23 still logged in
root pts/0 Sun Nov 5 21:00 - 21:23 (00:22)
root pts/0 Sun Nov 5 13:13 - 21:00 (07:46)
root pts/0 Sun Nov 5 13:07 - 13:13 (00:06)
reboot system boot 6.2.16-19-pve Sun Nov 5 13:07 still running
reboot system boot 6.2.16-19-pve Sun Nov 5 07:32 still running
root pts/0 Sat Nov 4 20:47 - crash (10:44)
reboot system boot 6.2.16-19-pve Sat Nov 4 20:35 still running
root pts/0 Sat Nov 4 20:13 - down (00:12)
root pts/0 Sat Nov 4 20:06 - 20:13 (00:06)
reboot system boot 6.2.16-19-pve Sat Nov 4 20:04 - 20:25 (00:20)
root pts/0 Sat Nov 4 11:21 - crash (08:43)
root pts/0 Sat Nov 4 11:20 - 11:21 (00:01)
root pts/0 Sat Nov 4 11:12 - 11:20 (00:07)
reboot system boot 6.2.16-19-pve Sat Nov 4 11:06 - 20:25 (09:18)
root pts/0 Sat Nov 4 10:57 - down (00:00)
root pts/0 Sat Nov 4 10:53 - 10:57 (00:03)
reboot system boot 6.2.16-19-pve Sat Nov 4 10:35 - 10:57 (00:22)
root pts/0 Sat Nov 4 00:25 - crash (10:10)
root pts/0 Sat Nov 4 00:24 - 00:25 (00:01)
root pts/0 Sat Nov 4 00:23 - 00:24 (00:00)
root pts/0 Sat Nov 4 00:21 - 00:23 (00:02)
root pts/0 Sat Nov 4 00:20 - 00:21 (00:00)
root pts/0 Sat Nov 4 00:15 - 00:20 (00:05)
reboot system boot 6.2.16-19-pve Fri Nov 3 23:22 - 10:57 (11:35)
root pts/0 Fri Nov 3 22:45 - crash (00:36)
root pts/0 Fri Nov 3 22:31 - 22:45 (00:14)
root pts/0 Fri Nov 3 21:39 - 22:31 (00:51)
root pts/0 Fri Nov 3 21:05 - 21:39 (00:33)
reboot system boot 6.2.16-19-pve Fri Nov 3 19:28 - 10:57 (15:29)
root pts/0 Fri Nov 3 17:31 - crash (01:57)
reboot system boot 6.2.16-19-pve Fri Nov 3 17:30 - 10:57 (17:26)
root pts/0 Fri Nov 3 17:27 - down (00:02)
reboot system boot 6.2.16-3-pve Fri Nov 3 17:26 - 17:30 (00:04)

Does the above imply it's crashing?



journctl gives me a gap...

Nov 03 17:26:17 proxmox kernel: Linux version 6.2.16-3-pve (tom@sbuild) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC >
Nov 03 17:26:17 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-3-pve root=/dev/mapper/pve-root ro quiet
Nov 03 17:26:17 proxmox kernel: KERNEL supported cpus:
Nov 03 17:26:17 proxmox kernel: Intel GenuineIntel
Nov 03 17:26:17 proxmox kernel: AMD AuthenticAMD
Nov 03 17:26:17 proxmox kernel: Hygon HygonGenuine
Nov 03 17:26:17 proxmox kernel: Centaur CentaurHauls
Nov 03 17:26:17 proxmox kernel: zhaoxin Shanghai
Nov 03 17:26:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Nov 03 17:26:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Nov 03 17:26:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Nov 03 17:26:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Nov 03 17:26:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Nov 03 17:26:17 proxmox kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Nov 03 17:26:17 proxmox kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Nov 03 17:26:17 proxmox kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Nov 03 17:26:17 proxmox kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Nov 03 17:26:17 proxmox kernel: signal: max sigframe size: 2032
Nov 03 17:26:17 proxmox kernel: BIOS-provided physical RAM map:
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000040400000-0x0000000080252fff] usable
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000080253000-0x0000000080253fff] ACPI NVS
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000080254000-0x0000000080254fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000080255000-0x000000008a250fff] usable
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000008a251000-0x000000008a717fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000008a718000-0x000000008a794fff] ACPI data
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000008a795000-0x000000008a7f4fff] ACPI NVS
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000008a7f5000-0x000000008af27fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000008af28000-0x000000008affefff] type 20
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000008afff000-0x000000008affffff] usable
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x000000008b000000-0x000000008fffffff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 03 17:26:17 proxmox kernel: BIOS-e820: [mem 0x0000000100000000-0x000000086dffffff] usable
Nov 03 17:26:17 proxmox kernel: NX (Execute Disable) protection: active
Nov 03 17:26:17 proxmox kernel: efi: EFI v2.70 by American Megatrends
Nov 03 17:26:17 proxmox kernel: efi: TPMFinalLog=0x8a7c4000 ACPI 2.0=0x8a731000 ACPI=0x8a731000 SMBIOS=0x8adde000 SMBIOS 3.0=0x8addd000 MEMATTR=0x8670d018 ESRT=0x8add>
Nov 03 17:26:17 proxmox kernel: efi: Remove mem48: MMIO range=[0xe0000000-0xefffffff] (256MB) from e820 map
Nov 03 17:26:17 proxmox kernel: e820: remove [mem 0xe0000000-0xefffffff] reserved
Nov 03 17:26:17 proxmox kernel: efi: Not removing mem49: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
Nov 03 17:26:17 proxmox kernel: efi: Not removing mem50: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
Nov 03 17:26:17 proxmox kernel: efi: Not removing mem51: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
Nov 03 17:26:17 proxmox kernel: efi: Not removing mem52: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
Nov 03 17:26:17 proxmox kernel: efi: Remove mem53: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Nov 03 17:26:17 proxmox kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
Nov 03 17:26:17 proxmox kernel: secureboot: Secure boot disabled
Nov 03 17:26:17 proxmox kernel: SMBIOS 3.1.1 present.
Nov 03 17:26:17 proxmox kernel: DMI: Intel(R) Client Systems NUC7i7DNKE/NUC7i7DNB, BIOS DNKBLi7v.86A.0080.2023.0912.1403 09/12/2023
Nov 03 17:26:17 proxmox kernel: tsc: Detected 2100.000 MHz processor
Nov 03 17:26:17 proxmox kernel: tsc: Detected 2099.944 MHz TSC
Nov 03 17:26:17 proxmox kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 03 17:26:17 proxmox kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 03 17:26:17 proxmox kernel: last_pfn = 0x86e000 max_arch_pfn = 0x400000000
...skipping...
Nov 05 13:07:13 proxmox spiceproxy[1004]: worker 1005 started
Nov 05 13:07:13 proxmox systemd[1]: Started spiceproxy.service - PVE SPICE Proxy Server.
Nov 05 13:07:13 proxmox systemd[1]: Starting pve-guests.service - PVE guests...
Nov 05 13:07:14 proxmox pve-guests[1007]: <root@pam> starting task UPIDroxmox:000003F0:0000047B:65479382:startall::root@pam:
Nov 05 13:07:14 proxmox pve-guests[1007]: <root@pam> end task UPIDroxmox:000003F0:0000047B:65479382:startall::root@pam: OK
Nov 05 13:07:14 proxmox systemd[1]: Finished pve-guests.service - PVE guests.
Nov 05 13:07:14 proxmox systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Nov 05 13:07:14 proxmox pvescheduler[1010]: starting server
Nov 05 13:07:14 proxmox systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
Nov 05 13:07:14 proxmox systemd[1]: Reached target multi-user.target - Multi-User System.
Nov 05 13:07:14 proxmox systemd[1]: Reached target graphical.target - Graphical Interface.
Nov 05 13:07:15 proxmox systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
Nov 05 13:07:15 proxmox systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Nov 05 13:07:15 proxmox systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Nov 05 13:07:15 proxmox systemd[1]: Startup finished in 12.507s (firmware) + 9.278s (loader) + 3.358s (kernel) + 8.840s (userspace) = 33.984s.
Nov 05 13:07:21 proxmox IPCC.xs[993]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:192.168.1.47 user=root
Nov 05 13:07:21 proxmox kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/>
Nov 05 13:07:22 proxmox kernel: FS-Cache: Loaded
Nov 05 13:07:22 proxmox kernel: Key type cifs.spnego registered
Nov 05 13:07:22 proxmox kernel: Key type cifs.idmap registered
Nov 05 13:07:22 proxmox kernel: CIFS: Attempting to mount \\192.168.1.165\Proxmox
Nov 05 13:07:23 proxmox pvedaemon[993]: authentication failure; rhost=::ffff:192.168.1.47 user=root@pam msg=Authentication failure
Nov 05 13:07:29 proxmox pvedaemon[994]: <root@pam> successful auth for user 'root@pam'
Nov 05 13:07:36 proxmox pvedaemon[993]: <root@pam> starting task UPIDroxmox:00000454:00000D34:65479398:vncshell::root@pam:
Nov 05 13:07:36 proxmox pvedaemon[1108]: starting termproxy UPIDroxmox:00000454:00000D34:65479398:vncshell::root@pam:
Nov 05 13:07:36 proxmox pvedaemon[994]: <root@pam> successful auth for user 'root@pam'
Nov 05 13:07:36 proxmox login[1115]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Nov 05 13:07:36 proxmox systemd-logind[665]: New session 1 of user root.
Nov 05 13:07:36 proxmox systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Nov 05 13:07:36 proxmox systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Nov 05 13:07:36 proxmox systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Nov 05 13:07:36 proxmox systemd[1]: Starting user@0.service - User Manager for UID 0...
Nov 05 13:07:36 proxmox (systemd)[1121]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Nov 05 13:07:36 proxmox systemd[1121]: Queued start job for default target default.target.
Nov 05 13:07:36 proxmox systemd[1121]: Created slice app.slice - User Application Slice.
Nov 05 13:07:36 proxmox systemd[1121]: Reached target paths.target - Paths.
Nov 05 13:07:36 proxmox systemd[1121]: Reached target timers.target - Timers.
Nov 05 13:07:36 proxmox systemd[1121]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Nov 05 13:07:36 proxmox systemd[1121]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Nov 05 13:07:36 proxmox systemd[1121]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Nov 05 13:07:36 proxmox systemd[1121]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Nov 05 13:07:36 proxmox systemd[1121]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Nov 05 13:07:36 proxmox systemd[1121]: Reached target sockets.target - Sockets.
Nov 05 13:07:36 proxmox systemd[1121]: Reached target basic.target - Basic System.
Nov 05 13:07:36 proxmox systemd[1121]: Reached target default.target - Main User Target.
Nov 05 13:07:36 proxmox systemd[1121]: Startup finished in 124ms.
Nov 05 13:07:36 proxmox systemd[1]: Started user@0.service - User Manager for UID 0.
Nov 05 13:07:36 proxmox systemd[1]: Started session-1.scope - Session 1 of User root.
Nov 05 13:07:36 proxmox login[1136]: ROOT LOGIN on '/dev/pts/0'
Nov 05 13:07:37 proxmox systemd[1]: systemd-fsckd.service: Deactivated successfully.
Nov 05 13:07:51 proxmox chronyd[809]: Selected source 109.74.206.120 (2.debian.pool.ntp.org)
Nov 05 13:07:51 proxmox chronyd[809]: System clock TAI offset set to 37 seconds
Nov 05 13:07:52 proxmox chronyd[809]: Selected source 81.128.218.110 (2.debian.pool.ntp.org)
Nov 05 13:08:57 proxmox chronyd[809]: Selected source 81.130.79.209 (2.debian.pool.ntp.org)
Nov 05 13:11:07 proxmox chronyd[809]: Selected source 81.128.218.110 (2.debian.pool.ntp.org)
Nov 05 13:13:32 proxmox systemd-logind[665]: Session 1 logged out. Waiting for processes to exit.
Nov 05 13:13:32 proxmox systemd[1]: session-1.scope: Deactivated successfully.
Nov 05 13:13:32 proxmox pvedaemon[993]: <root@pam> end task UPIDroxmox:00000454:00000D34:65479398:vncshell::root@pam: OK
Nov 05 13:13:32 proxmox systemd-logind[665]: Removed session 1.
Nov 05 13:13:42 proxmox systemd[1]: Stopping user@0.service - User Manager for UID 0...
Nov 05 13:13:42 proxmox systemd[1121]: Activating special unit exit.target...
Nov 05 13:13:42 proxmox systemd[1121]: Stopped target default.target - Main User Target.


With "Skipping" just as it reboots, I use the keyboard etc.

Any ideas where I start looking?

 

[Nollimox]

Any ideas where I start looking?

Not sure however, it's a server and servers are never intended to sleep...see if you can turn that off in the bios.

 

[Spodster]

There's nothing in the BIOS re turning itself off.
I ran a memtest for 4-5 hours with no issues.

I'm currently pursuing this thread/fix and hoping I have the same issue and can easily be fixed.
I've tried the GRUB fix so far.