Proxmox rebootet nicht selbstständig nach Anforderung

[Holger76]

Hallo zusammen,

seit ein paar Monaten habe ich das Problem, (seit evtl 2-3x rebootet), dass Proxmox nicht mehr automatisch neu startet.. d.h. es werden alle VMs etc runtergefahren, die Proxmox Oberflache ist auch nicht mehr erreichbar, aber dann gehts nicht weiter. Egal wie lange ich warte, de reboot erfolgt nicht und die Oberfläche nach reboot erscheint nicht, Auch per SSH komme ich nicht drauf.
Nur ein langes drücken auf den Powerknopf meines NUCs bringt den Rechner dann zum stehen und anschließend startet er ohne Probleme neu. Ich versuche das natürlich tunlichst zu vermeiden, aber irgendwann reicht es halt.
Ich habe mir jetzt mal das Syslog anschaut:

Spoiler: LOG

May 20 22:01:51 pve systemd[1]: Stopped PVE guests.
May 20 22:01:51 pve systemd[1]: Stopping Proxmox VE LXC Syscall Daemon...
May 20 22:01:51 pve systemd[1]: Stopping PVE Status Daemon...
May 20 22:01:51 pve systemd[1]: Stopping PVE SPICE Proxy Server...
May 20 22:01:51 pve systemd[1]: Stopping Proxmox VE firewall...
May 20 22:01:51 pve systemd[1]: Stopping PVE Local HA Resource Manager Daemon...
May 20 22:01:51 pve systemd[1]: pve-lxc-syscalld.service: Main process exited, code=killed, status=15/TERM
May 20 22:01:51 pve systemd[1]: pve-lxc-syscalld.service: Succeeded.
May 20 22:01:51 pve systemd[1]: Stopped Proxmox VE LXC Syscall Daemon.
May 20 22:01:51 pve kernel: [4063216.360773] usb 1-1: USB disconnect, device number 26
May 20 22:01:51 pve spiceproxy[2328]: received signal TERM
May 20 22:01:51 pve spiceproxy[2328]: server closing
May 20 22:01:51 pve spiceproxy[3034630]: worker exit
May 20 22:01:51 pve spiceproxy[2328]: worker 3034630 finished
May 20 22:01:51 pve spiceproxy[2328]: server stopped
May 20 22:01:51 pve pvestatd[2255]: received signal TERM
May 20 22:01:51 pve pvestatd[2255]: server closing
May 20 22:01:51 pve pvestatd[2255]: server stopped
May 20 22:01:51 pve kernel: [4063216.745080] usb 1-1: new full-speed USB device number 27 using xhci_hcd
May 20 22:01:51 pve pve-firewall[2252]: received signal TERM
May 20 22:01:51 pve pve-firewall[2252]: server closing
May 20 22:01:51 pve pve-firewall[2252]: clear firewall rules
May 20 22:01:51 pve pve-firewall[2252]: server stopped
May 20 22:01:51 pve pve-ha-lrm[2330]: received signal TERM
May 20 22:01:51 pve pve-ha-lrm[2330]: got shutdown request with shutdown policy 'conditional'
May 20 22:01:51 pve pve-ha-lrm[2330]: reboot LRM, stop and freeze all services
May 20 22:01:51 pve pve-ha-lrm[2330]: server stopped
May 20 22:01:51 pve kernel: [4063216.896051] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
May 20 22:01:51 pve kernel: [4063216.896053] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 20 22:01:51 pve kernel: [4063216.896054] usb 1-1: Product: ConBee II
May 20 22:01:51 pve kernel: [4063216.896054] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
May 20 22:01:51 pve kernel: [4063216.896055] usb 1-1: SerialNumber: DE2130253
May 20 22:01:51 pve kernel: [4063216.897622] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
May 20 22:01:52 pve systemd[1]: spiceproxy.service: Succeeded.
May 20 22:01:52 pve systemd[1]: Stopped PVE SPICE Proxy Server.
May 20 22:01:52 pve systemd[1]: pvestatd.service: Succeeded.
May 20 22:01:52 pve systemd[1]: Stopped PVE Status Daemon.
May 20 22:01:52 pve systemd[1]: pve-firewall.service: Succeeded.
May 20 22:01:52 pve systemd[1]: Stopped Proxmox VE firewall.
May 20 22:01:52 pve systemd[1]: pve-ha-lrm.service: Succeeded.
May 20 22:01:52 pve systemd[1]: Stopped PVE Local HA Resource Manager Daemon.
May 20 22:01:52 pve systemd[1]: Stopping PVE API Proxy Server...
May 20 22:01:52 pve systemd[1]: Stopping PVE Qemu Event Daemon...
May 20 22:01:52 pve systemd[1]: Stopping PVE Cluster HA Resource Manager Daemon...
May 20 22:01:52 pve systemd[1]: Stopping LXC Container Initialization and Autoboot Code...
May 20 22:01:52 pve systemd[1]: qmeventd.service: Main process exited, code=killed, status=15/TERM
May 20 22:01:52 pve systemd[1]: qmeventd.service: Succeeded.
May 20 22:01:52 pve systemd[1]: Stopped PVE Qemu Event Daemon.
May 20 22:01:52 pve systemd[1]: lxc.service: Control process exited, code=exited, status=1/FAILURE
May 20 22:01:52 pve systemd[1]: lxc.service: Failed with result 'exit-code'.
May 20 22:01:52 pve systemd[1]: Stopped LXC Container Initialization and Autoboot Code.
May 20 22:01:52 pve systemd[1]: Stopping LXC network bridge setup...
May 20 22:01:52 pve systemd[1]: Stopping FUSE filesystem for LXC...
May 20 22:01:52 pve systemd[1]: lxc-net.service: Succeeded.
May 20 22:01:52 pve systemd[1]: Stopped LXC network bridge setup.
May 20 22:01:52 pve systemd[2569998]: var-lib-lxcfs.mount: Succeeded.
May 20 22:01:52 pve systemd[1]: var-lib-lxcfs.mount: Succeeded.
May 20 22:01:52 pve lxcfs[1840]: Running destructor lxcfs_exit
May 20 22:01:52 pve systemd[1]: Unmounted /var/lib/lxcfs.
May 20 22:01:52 pve fusermount[3079823]: /bin/fusermount: failed to unmount /var/lib/lxcfs: Invalid argument
May 20 22:01:52 pve systemd[1]: lxcfs.service: Succeeded.
May 20 22:01:52 pve systemd[1]: Stopped FUSE filesystem for LXC.
May 20 22:01:53 pve pve-ha-crm[2318]: received signal TERM
May 20 22:01:53 pve pve-ha-crm[2318]: server received shutdown request
May 20 22:01:53 pve pve-ha-crm[2318]: server stopped
May 20 22:01:53 pve pveproxy[2321]: received signal TERM
May 20 22:01:53 pve pveproxy[2321]: server closing
May 20 22:01:53 pve pveproxy[3034632]: worker exit
May 20 22:01:53 pve pveproxy[3034631]: worker exit
May 20 22:01:53 pve pveproxy[2321]: worker 3034632 finished
May 20 22:01:53 pve pveproxy[2321]: worker 3034631 finished
May 20 22:01:53 pve pveproxy[2321]: worker 3034633 finished
May 20 22:01:53 pve pveproxy[2321]: server stopped
May 20 22:01:54 pve systemd[1]: pve-ha-crm.service: Succeeded.
May 20 22:01:54 pve systemd[1]: Stopped PVE Cluster HA Resource Manager Daemon.
May 20 22:07:47 pve systemd-modules-load[977]: Inserted module 'coretemp'
May 20 22:07:47 pve systemd-modules-load[977]: Inserted module 'iscsi_tcp'
May 20 22:07:47 pve systemd[1]: Starting Flush Journal to Persistent Storage...
May 20 22:07:47 pve systemd-modules-load[977]: Inserted module 'ib_iser'
May 20 22:07:47 pve systemd[1]: Started Create Static Device Nodes in /dev.
May 20 22:07:47 pve systemd[1]: Starting udev Kernel Device Manager...
May 20 22:07:47 pve systemd-modules-load[977]: Inserted module 'vhost_net'
May 20 22:07:47 pve systemd[1]: Started Flush Journal to Persistent Storage.
May 20 22:07:47 pve systemd[1]: Started Load Kernel Modules.
May 20 22:07:47 pve systemd[1]: Starting Apply Kernel Variables...
May 20 22:07:47 pve systemd[1]: Mounting Kernel Configuration File System...
May 20 22:07:47 pve systemd[1]: Mounting FUSE Control File System...
May 20 22:07:47 pve systemd[1]: Mounted Kernel Configuration File System.
May 20 22:07:47 pve systemd[1]: Mounted FUSE Control File System.
May 20 22:07:47 pve systemd[1]: Started udev Coldplug all Devices.
May 20 22:07:47 pve systemd[1]: Starting Helper to synchronize boot up for ifupdown...
May 20 22:07:47 pve systemd[1]: Starting udev Wait for Complete Device Initialization...
May 20 22:07:47 pve systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May 20 22:07:47 pve systemd[1]: Reached target Local File Systems (Pre).
May 20 22:07:47 pve systemd[1]: Started Apply Kernel Variables.
May 20 22:07:47 pve systemd[1]: Started udev Kernel Device Manager.
May 20 22:07:47 pve kernel: [ 0.000000] Linux version 5.4.114-1-pve (build@proxmox) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.4.114-1 (Sun, 09 May 2021 17:13:05 +0200) ()

Also gegen 22:01:54 war das letzte vor dem "Hardware" Neustart. Ich kann da leider nichts erkennen, was Probleme verursacht bzw wüßte ich nicht, was da noch kommen sollte...
Hat von Euch jmd eine Idee ?

Grüße,
Holger

 

[Dunuin]

Ich hatte das auch schon. Da gab es dann aber in der Konsole noch Nachrichten die glaube ich nicht in den Logs standen. Musst du mal per KVM oder physischem Monitor gucken was Proxmox da noch macht nach dem Runterfahren.