Proxmox newbie braucht Hilfe.

J

jm1282

New Member
Feb 25, 2026
4
0
1
Hallo zusammen, ich bin neu bei Proxmox.
Folgendes Problem habe ich.
Proxmox scheint immer nach ca. 24 Stunden selbst zu rebtooten.
Ich kann dann dann nicht mehr via ssh oder Web UI auf den Proxmox Server zugreifen, erst nach einem von mir ausgelösten reboot.
Ich lasse Proxmox momentan auf einem Lenovo yoga slim i7 laufen.
Überhitzung zum Beispiel kann es nicht sein, da der Laptop mit max. 40°C läuft (laut btop).
Hat jemand von euch vielleicht eine Idee ?
 
Ok, mit der Hardware Angabe kann 10 Jahre alt sein oder 3 Wochen. Das kann vieles sein inkompatible Hardware, ich habe bei meinen installierten noch keine Probleme gehabt, habe es auch noch nie auf einem Notebook installiert. Bitte mehr Informationen. Meine Glaskugel habe ich gerade nicht dabei
 
  • Like
Reactions: news
micneu said:
Ok, mit der Hardware Angabe kann 10 Jahre alt sein oder 3 Wochen. Das kann vieles sein inkompatible Hardware, ich habe bei meinen installierten noch keine Probleme gehabt, habe es auch noch nie auf einem Notebook installiert. Bitte mehr Informationen. Meine Glaskugel habe ich gerade nicht dabei
Click to expand...
Vielleicht hilft das.
journalctl --since "24 hours ago"


Feb 24 06:36:03 pve NetworkManager[1025]: <info> [1771911363.9018] device (wlp0s20f3): set-hw-addr: set MAC address to 9A:D1:81:57:98:75 (scanning)


Feb 24 06:36:03 pve NetworkManager[1025]: <info> [1771911363.9204] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 06:36:03 pve NetworkManager[1025]: <info> [1771911363.9204] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 06:36:03 pve NetworkManager[1025]: <info> [1771911363.9256] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 06:36:03 pve NetworkManager[1025]: <info> [1771911363.9256] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 06:42:56 pve NetworkManager[1025]: <info> [1771911776.9577] device (wlp0s20f3): set-hw-addr: set MAC address to 82:58:D7:23:51:16 (scanning)


Feb 24 06:42:56 pve NetworkManager[1025]: <info> [1771911776.9674] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 06:42:56 pve NetworkManager[1025]: <info> [1771911776.9674] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 06:42:56 pve NetworkManager[1025]: <info> [1771911776.9726] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 06:42:56 pve NetworkManager[1025]: <info> [1771911776.9726] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 06:49:49 pve NetworkManager[1025]: <info> [1771912189.9495] device (wlp0s20f3): set-hw-addr: set MAC address to 9A:A0:42:AB:65:B1 (scanning)


Feb 24 06:49:49 pve NetworkManager[1025]: <info> [1771912189.9643] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 06:49:49 pve NetworkManager[1025]: <info> [1771912189.9643] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 06:49:49 pve NetworkManager[1025]: <info> [1771912189.9695] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 06:49:49 pve NetworkManager[1025]: <info> [1771912189.9695] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 06:56:42 pve NetworkManager[1025]: <info> [1771912602.9420] device (wlp0s20f3): set-hw-addr: set MAC address to CA:E7:B6:67:05:A6 (scanning)


Feb 24 07:03:35 pve NetworkManager[1025]: <info> [1771913015.9952] device (wlp0s20f3): set-hw-addr: set MAC address to 8E:7B:EE:92:47:5B (scanning)


Feb 24 07:03:36 pve NetworkManager[1025]: <info> [1771913016.0072] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:03:36 pve NetworkManager[1025]: <info> [1771913016.0073] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:03:36 pve NetworkManager[1025]: <info> [1771913016.0125] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:03:36 pve NetworkManager[1025]: <info> [1771913016.0125] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 07:10:28 pve NetworkManager[1025]: <info> [1771913428.9715] device (wlp0s20f3): set-hw-addr: set MAC address to 2A:8F:2C:8E:13:1B (scanning)


Feb 24 07:10:28 pve NetworkManager[1025]: <info> [1771913428.9767] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:10:28 pve NetworkManager[1025]: <info> [1771913428.9767] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:10:28 pve NetworkManager[1025]: <info> [1771913428.9768] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:10:28 pve NetworkManager[1025]: <info> [1771913428.9768] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 07:17:01 pve CRON[23775]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)


Feb 24 07:17:01 pve CRON[23777]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)


Feb 24 07:17:01 pve CRON[23775]: pam_unix(cron:session): session closed for user root


Feb 24 07:17:20 pve NetworkManager[1025]: <info> [1771913840.9960] device (wlp0s20f3): set-hw-addr: set MAC address to DE:41:F9:16:20:D7 (scanning)


Feb 24 07:24:13 pve NetworkManager[1025]: <info> [1771914253.9961] device (wlp0s20f3): set-hw-addr: set MAC address to 3A:2F:21:44:AF:A3 (scanning)


Feb 24 07:24:14 pve NetworkManager[1025]: <info> [1771914254.0145] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:24:14 pve NetworkManager[1025]: <info> [1771914254.0145] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:24:14 pve NetworkManager[1025]: <info> [1771914254.0195] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:24:14 pve NetworkManager[1025]: <info> [1771914254.0195] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 07:31:07 pve NetworkManager[1025]: <info> [1771914667.9016] device (wlp0s20f3): set-hw-addr: set MAC address to BA:BB:50:E4:BA:D6 (scanning)


Feb 24 07:31:07 pve NetworkManager[1025]: <info> [1771914667.9068] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:31:07 pve NetworkManager[1025]: <info> [1771914667.9068] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:31:07 pve NetworkManager[1025]: <info> [1771914667.9069] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:31:07 pve NetworkManager[1025]: <info> [1771914667.9069] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 07:38:00 pve NetworkManager[1025]: <info> [1771915080.9289] device (wlp0s20f3): set-hw-addr: set MAC address to A2:85:49:94:16:48 (scanning)


Feb 24 07:38:00 pve NetworkManager[1025]: <info> [1771915080.9443] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:38:00 pve NetworkManager[1025]: <info> [1771915080.9443] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:38:00 pve NetworkManager[1025]: <info> [1771915080.9494] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:38:00 pve NetworkManager[1025]: <info> [1771915080.9494] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 07:44:53 pve NetworkManager[1025]: <info> [1771915493.9919] device (wlp0s20f3): set-hw-addr: set MAC address to 9A:18:09:7B:D5:5A (scanning)


Feb 24 07:44:54 pve NetworkManager[1025]: <info> [1771915494.0011] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:44:54 pve NetworkManager[1025]: <info> [1771915494.0012] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:44:54 pve NetworkManager[1025]: <info> [1771915494.0064] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:44:54 pve NetworkManager[1025]: <info> [1771915494.0065] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 07:51:46 pve NetworkManager[1025]: <info> [1771915906.8968] device (wlp0s20f3): set-hw-addr: set MAC address to 6E:25:FF:C6:8D:7D (scanning)


Feb 24 07:51:46 pve NetworkManager[1025]: <info> [1771915906.9102] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:51:46 pve NetworkManager[1025]: <info> [1771915906.9102] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:51:46 pve NetworkManager[1025]: <info> [1771915906.9155] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:51:46 pve NetworkManager[1025]: <info> [1771915906.9155] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 07:58:39 pve NetworkManager[1025]: <info> [1771916319.9340] device (wlp0s20f3): set-hw-addr: set MAC address to DE:B5:6C:22:1B:BC (scanning)


Feb 24 07:58:39 pve NetworkManager[1025]: <info> [1771916319.9473] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 07:58:39 pve NetworkManager[1025]: <info> [1771916319.9474] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 07:58:39 pve NetworkManager[1025]: <info> [1771916319.9526] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 07:58:39 pve NetworkManager[1025]: <info> [1771916319.9526] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


Feb 24 08:05:32 pve NetworkManager[1025]: <info> [1771916732.9219] device (wlp0s20f3): set-hw-addr: set MAC address to 9E:DE:ED:A2:1D:54 (scanning)


Feb 24 08:05:32 pve NetworkManager[1025]: <info> [1771916732.9301] device (wlp0s20f3): supplicant interface state: inactive -> disconnected


Feb 24 08:05:32 pve NetworkManager[1025]: <info> [1771916732.9301] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected


Feb 24 08:05:32 pve NetworkManager[1025]: <info> [1771916732.9354] device (wlp0s20f3): supplicant interface state: disconnected -> inactive


Feb 24 08:05:32 pve NetworkManager[1025]: <info> [1771916732.9354] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive


lines 1-65
 
Und vielleicht dies noch.
journalctl -u pveproxy -u pvedaemon -u pvestatd -u pve-cluster --since "24 hours ago" -p warning


Feb 25 04:47:20 pve pvestatd[1390]: auth key pair too old, rotating..


root@pve:~# pvecm status


Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?


root@pve:~# journalctl -u pveproxy -u pvedaemon -u pvestatd -u pve-cluster --since "24 hours ago" -p warning


Feb 25 04:47:20 pve pvestatd[1390]: auth key pair too old, rotating..


root@pve:~# journalctl --since "24 hours ago" -p warning


Feb 24 13:03:14 pve kernel: xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.


Feb 24 13:03:14 pve ModemManager[1061]: <wrn> [plugin-manager] task 2: port context already scheduled


Feb 24 16:40:04 pve blkmapd[1168]: exit on signal(15)


Feb 24 16:40:10 pve systemd[1]: lxcfs.service: Failed with result 'exit-code'.


-- Boot 2146184f76c74c94b5c7054ae9948a2a --


Feb 24 16:40:34 pve kernel: pnp 00:02: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]


Feb 24 16:40:34 pve kernel: resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000fedcdfff], which spans more than pnp 00:02 [mem 0xfedc0000-0xfedc7fff]


Feb 24 16:40:34 pve kernel: caller uncore_get_box_mmio_addr+0xe2/0x150 mapping multiple BARs


Feb 24 16:40:34 pve kernel: hpet_acpi_add: no address or irqs in _CRS


Feb 24 16:40:34 pve kernel: tpm tpm0: tpm_read_log_acpi: Failed to map ACPI memory


Feb 24 16:40:34 pve kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp


Feb 24 16:40:34 pve kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.


Feb 24 16:40:34 pve kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'


Feb 24 16:40:34 pve kernel: spl: loading out-of-tree module taints kernel.


Feb 24 16:40:34 pve kernel: zfs: module license 'CDDL' taints kernel.


Feb 24 16:40:34 pve kernel: Disabling lock debugging due to kernel taint


Feb 24 16:40:34 pve kernel: zfs: module license taints kernel.


Feb 24 16:40:34 pve (udev-worker)[425]: lo: Invalid network interface name, ignoring:


Feb 24 16:40:34 pve lvm[469]: PV /dev/nvme0n1p3 online, VG pve is complete.


Feb 24 16:40:34 pve lvm[469]: VG pve finished


Feb 24 16:40:34 pve kernel: intel-hid INT33D5:00: failed to enable HID power button


Feb 24 16:40:34 pve kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator


Feb 24 16:40:34 pve kernel: spi-nor spi0.1: supply vcc not found, using dummy regulator


Feb 24 16:40:35 pve tlp[592]: Error: TLP's power saving will not apply on boot because tlp.service is not enabled --> Invoke 'systemctl enable tlp.service' to ensure the full functionality of >


Feb 24 16:40:35 pve kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: SOF firmware and/or topology file not found.


Feb 24 16:40:35 pve kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof_probe_work failed err: -2


Feb 24 16:40:35 pve kernel: nvme nvme0: using unchecked data buffer


Feb 24 16:40:36 pve blkmapd[1145]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory


Feb 24 16:40:37 pve kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.


Feb 24 16:40:37 pve tlp[1348]: Error: TLP's power saving will not apply on boot because tlp.service is not enabled --> Invoke 'systemctl enable tlp.service' to ensure the full functionality of>


Feb 24 16:40:39 pve kernel: kauditd_printk_skb: 110 callbacks suppressed


Feb 24 18:53:13 pve kernel: xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.


Feb 24 18:53:13 pve ModemManager[1061]: <wrn> [plugin-manager] task 2: port context already scheduled


Feb 24 18:55:45 pve sshd-session[2177]: error: mm_reap: preauth child terminated by signal 15


Feb 24 18:55:45 pve blkmapd[1145]: exit on signal(15)


Feb 24 18:55:50 pve systemd[1]: lxcfs.service: Failed with result 'exit-code'.


-- Boot ee280505d02a412aa6686ad2d1fd2766 --


Feb 24 18:56:15 pve kernel: pnp 00:02: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]


Feb 24 18:56:15 pve kernel: resource: resource sanity check: requesting [mem 0x00000000fedc0000-0x00000000fedcdfff], which spans more than pnp 00:02 [mem 0xfedc0000-0xfedc7fff]


Feb 24 18:56:15 pve kernel: caller uncore_get_box_mmio_addr+0xe2/0x150 mapping multiple BARs


Feb 24 18:56:15 pve kernel: hpet_acpi_add: no address or irqs in _CRS


Feb 24 18:56:15 pve kernel: tpm tpm0: tpm_read_log_acpi: Failed to map ACPI memory


Feb 24 18:56:15 pve kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp


Feb 24 18:56:15 pve kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.


Feb 24 18:56:15 pve kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'


Feb 24 18:56:15 pve kernel: spl: loading out-of-tree module taints kernel.


Feb 24 18:56:15 pve kernel: zfs: module license 'CDDL' taints kernel.


Feb 24 18:56:15 pve kernel: Disabling lock debugging due to kernel taint


Feb 24 18:56:15 pve kernel: zfs: module license taints kernel.


Feb 24 18:56:15 pve (udev-worker)[423]: lo: Invalid network interface name, ignoring:


Feb 24 18:56:15 pve lvm[467]: PV /dev/nvme0n1p3 online, VG pve is complete.


Feb 24 18:56:15 pve lvm[467]: VG pve finished


Feb 24 18:56:15 pve kernel: intel-hid INT33D5:00: failed to enable HID power button


Feb 24 18:56:15 pve kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator


Feb 24 18:56:15 pve kernel: spi-nor spi0.1: supply vcc not found, using dummy regulator


Feb 24 18:56:16 pve tlp[605]: Error: TLP's power saving will not apply on boot because tlp.service is not enabled --> Invoke 'systemctl enable tlp.service' to ensure the full functionality of >


Feb 24 18:56:16 pve kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: SOF firmware and/or topology file not found.


Feb 24 18:56:16 pve kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof_probe_work failed err: -2


Feb 24 18:56:16 pve blkmapd[961]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory


Feb 24 18:56:16 pve kernel: nvme nvme0: using unchecked data buffer


Feb 24 18:56:18 pve kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.


Feb 24 18:56:18 pve tlp[1349]: Error: TLP's power saving will not apply on boot because tlp.service is not enabled --> Invoke 'systemctl enable tlp.service' to ensure the full functionality of>


Feb 24 18:56:20 pve kernel: kauditd_printk_skb: 110 callbacks suppressed


Feb 25 04:47:20 pve pvestatd[1390]: auth key pair too old, rotating..


Feb 25 05:00:15 pve kernel: vmbr0: the hash_elasticity option has been deprecated and is always 16


lines 1-65
 
Woher weißt du, dass neu gestarted wird? Ich würde mir mal folgendes ansehen
Bash: 
lspci -vnnk | awk '/Ethernet/{print $0}' RS=
Wenn das Problem wieder auftaucht nutze auch mal das Keyboard direkt und schaue dir journalctl -kr an.
Bitte benutzte Code Blöcke damit das lesbar ist.
 
Last edited:
Impact said:
Woher weiß du, dass neu gestarted wird? Ich würde mir mal folgendes ansehen
Bash: 
lspci -vnnk | awk '/Ethernet/{print $0}' RS=
Wenn das Problem wieder auftaucht nutze auch mal das Keyboard direkt und schaue dir journalctl -kr an.
Bitte benutzte Code Blöcke damit das lesbar ist.
Click to expand...
Ok, mache ich. Danke
 
You must log in or register to reply here.
Top Bottom
Back