Seit heute random Reboots

S

SharkyMoto

New Member
May 9, 2024
3
0
1
Mein Host rebooted seit heute ständig, irgendwie steht nichts im Log, aus dem ich schlau werde. (meine erste Proxmox installation - daher auch nicht wirklich plan, was genau ich da mache und worauf ich achten soll.)

Wird da vielleicht jemand schlau draus?

Code: 
May 09 22:37:01 pve pvedaemon[973]: <root@pam> successful auth for user 'root@pam'
May 09 22:37:27 pve pvedaemon[973]: <root@pam> starting task UPID:pve:000005D6:000036DD:663D3407:qmstart:102:root@pam:
May 09 22:37:27 pve pvedaemon[1494]: start VM 102: UPID:pve:000005D6:000036DD:663D3407:qmstart:102:root@pam:
May 09 22:37:27 pve pvedaemon[1494]: USB Mapping invalid (hardware probably changed): usb device '1-8' not found
May 09 22:37:27 pve pvedaemon[973]: <root@pam> end task UPID:pve:000005D6:000036DD:663D3407:qmstart:102:root@pam: USB Mapping invalid (hardware probably changed): usb device '1-8' not found
May 09 22:37:41 pve pvedaemon[974]: <root@pam> update VM 102: -delete usb1
May 09 22:37:54 pve pvedaemon[975]: <root@pam> update VM 103: -delete usb0
May 09 22:37:56 pve pvedaemon[1581]: start VM 102: UPID:pve:0000062D:0000424D:663D3424:qmstart:102:root@pam:
May 09 22:37:56 pve pvedaemon[975]: <root@pam> starting task UPID:pve:0000062D:0000424D:663D3424:qmstart:102:root@pam:
May 09 22:37:56 pve pvedaemon[1581]: USB Mapping invalid (hardware probably changed): usb device '1-8' not found
May 09 22:37:56 pve pvedaemon[975]: <root@pam> end task UPID:pve:0000062D:0000424D:663D3424:qmstart:102:root@pam: USB Mapping invalid (hardware probably changed): usb device '1-8' not found
May 09 22:37:58 pve pvedaemon[1584]: start VM 103: UPID:pve:00000630:000042ED:663D3426:qmstart:103:root@pam:
May 09 22:37:58 pve pvedaemon[973]: <root@pam> starting task UPID:pve:00000630:000042ED:663D3426:qmstart:103:root@pam:
May 09 22:37:58 pve systemd[1]: Started 103.scope.
May 09 22:37:59 pve kernel: tap103i0: entered promiscuous mode
May 09 22:37:59 pve kernel: vmbr0: port 3(fwpr103p0) entered blocking state
May 09 22:37:59 pve kernel: vmbr0: port 3(fwpr103p0) entered disabled state
May 09 22:37:59 pve kernel: fwpr103p0: entered allmulticast mode
May 09 22:37:59 pve kernel: fwpr103p0: entered promiscuous mode
May 09 22:37:59 pve kernel: vmbr0: port 3(fwpr103p0) entered blocking state
May 09 22:37:59 pve kernel: vmbr0: port 3(fwpr103p0) entered forwarding state
May 09 22:37:59 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
May 09 22:37:59 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
May 09 22:37:59 pve kernel: fwln103i0: entered allmulticast mode
May 09 22:37:59 pve kernel: fwln103i0: entered promiscuous mode
May 09 22:37:59 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
May 09 22:37:59 pve kernel: fwbr103i0: port 1(fwln103i0) entered forwarding state
May 09 22:37:59 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
May 09 22:37:59 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
May 09 22:37:59 pve kernel: tap103i0: entered allmulticast mode
May 09 22:37:59 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
May 09 22:37:59 pve kernel: fwbr103i0: port 2(tap103i0) entered forwarding state
May 09 22:37:59 pve pvedaemon[973]: <root@pam> end task UPID:pve:00000630:000042ED:663D3426:qmstart:103:root@pam: OK
-- Reboot --
May 09 22:40:34 pve kernel: Linux version 6.8.4-2-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.8.4-2 (2024-04-10T17:36Z) ()
May 09 22:40:34 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.4-2-pve root=/dev/mapper/pve-root ro quiet
May 09 22:40:34 pve kernel: KERNEL supported cpus:
May 09 22:40:34 pve kernel:   Intel GenuineIntel
May 09 22:40:34 pve kernel:   AMD AuthenticAMD
May 09 22:40:34 pve kernel:   Hygon HygonGenuine
May 09 22:40:34 pve kernel:   Centaur CentaurHauls
May 09 22:40:34 pve kernel:   zhaoxin   Shanghai 
May 09 22:40:34 pve kernel: BIOS-provided physical RAM map:
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cebaafff] usable
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x00000000cebab000-0x00000000cf98efff] reserved
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x00000000cf98f000-0x00000000cfb8efff] ACPI NVS
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x00000000cfb8f000-0x00000000cfc0efff] ACPI data
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x00000000cfc0f000-0x00000000cfc0ffff] usable
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x00000000cfc10000-0x00000000d67fffff] reserved
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved
May 09 22:40:34 pve kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008277fffff] usable
May 09 22:40:34 pve kernel: NX (Execute Disable) protection: active
May 09 22:40:34 pve kernel: APIC: Static calls initialized
May 09 22:40:34 pve kernel: efi: EFI v2.6 by HP
 
Last edited:
  • Like
Reactions: SharkyMoto
Ich kann laut terminal nur eine version anpinnen? habe gestern aber mal alle USB devices aus den mappings genommen, und seitdem läuft es stabil. hat das vielleicht auch damit zu tun? dachte erst an ein ram problem, dem scheint ja dann aber nicht so zu sein.
 
update: lief den ganzen tag stabil und heute um die (mehr oder weniger) gleichen uhrzeiten wieder fritte gegangen. ist da irgendwas konfiguriert, was ich übersehe?

Code: 
May 10 22:59:41 pve cron[911]: (CRON) INFO (Running @reboot jobs)
May 10 22:59:41 pve systemd[1]: Starting pvedaemon.service - PVE API Daemon...
May 10 22:59:41 pve systemd[1]: Starting pvestatd.service - PVE Status Daemon...
May 10 22:59:42 pve pve-firewall[921]: starting server
May 10 22:59:42 pve systemd[1]: Started pve-firewall.service - Proxmox VE firewall.
May 10 22:59:42 pve pvestatd[928]: starting server
May 10 22:59:42 pve systemd[1]: Started pvestatd.service - PVE Status Daemon.
May 10 22:59:42 pve pvedaemon[947]: starting server
May 10 22:59:42 pve pvedaemon[947]: starting 3 worker(s)
May 10 22:59:42 pve pvedaemon[947]: worker 948 started
May 10 22:59:42 pve pvedaemon[947]: worker 949 started
May 10 22:59:42 pve pvedaemon[947]: worker 950 started
May 10 22:59:42 pve systemd[1]: Started pvedaemon.service - PVE API Daemon.
May 10 22:59:42 pve systemd[1]: Starting pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon...
May 10 22:59:42 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
May 10 22:59:43 pve pve-ha-crm[956]: starting server
May 10 22:59:43 pve pve-ha-crm[956]: status change startup => wait_for_quorum
May 10 22:59:43 pve systemd[1]: Started pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon.
May 10 22:59:44 pve pveproxy[957]: starting server
May 10 22:59:44 pve pveproxy[957]: starting 3 worker(s)
May 10 22:59:44 pve pveproxy[957]: worker 958 started
May 10 22:59:44 pve pveproxy[957]: worker 959 started
May 10 22:59:44 pve pveproxy[957]: worker 960 started
May 10 22:59:44 pve systemd[1]: Started pveproxy.service - PVE API Proxy Server.
May 10 22:59:44 pve systemd[1]: Starting pve-ha-lrm.service - PVE Local HA Resource Manager Daemon...
May 10 22:59:44 pve systemd[1]: Starting spiceproxy.service - PVE SPICE Proxy Server...
May 10 22:59:44 pve spiceproxy[963]: starting server
May 10 22:59:44 pve spiceproxy[963]: starting 1 worker(s)
May 10 22:59:44 pve spiceproxy[963]: worker 964 started
May 10 22:59:44 pve systemd[1]: Started spiceproxy.service - PVE SPICE Proxy Server.
May 10 22:59:44 pve pve-ha-lrm[965]: starting server
May 10 22:59:44 pve pve-ha-lrm[965]: status change startup => wait_for_agent_lock
May 10 22:59:44 pve systemd[1]: Started pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.
May 10 22:59:44 pve systemd[1]: Starting pve-guests.service - PVE guests...
May 10 22:59:45 pve pve-guests[967]: <root@pam> starting task UPID:pve:000003C8:00000756:663E8AC1:startall::root@pam:
May 10 22:59:45 pve pvesh[967]: Starting VM 100
May 10 22:59:45 pve pve-guests[969]: start VM 100: UPID:pve:000003C9:00000759:663E8AC1:qmstart:100:root@pam:
May 10 22:59:45 pve pve-guests[968]: <root@pam> starting task UPID:pve:000003C9:00000759:663E8AC1:qmstart:100:root@pam:
May 10 22:59:46 pve systemd[1]: Created slice qemu.slice - Slice /qemu.
May 10 22:59:46 pve systemd[1]: Started 100.scope.
May 10 22:59:47 pve kernel: tap100i0: entered promiscuous mode
May 10 22:59:47 pve kernel: vmbr0: port 2(tap100i0) entered blocking state
May 10 22:59:47 pve kernel: vmbr0: port 2(tap100i0) entered disabled state
May 10 22:59:47 pve kernel: tap100i0: entered allmulticast mode
May 10 22:59:47 pve kernel: vmbr0: port 2(tap100i0) entered blocking state
May 10 22:59:47 pve kernel: vmbr0: port 2(tap100i0) entered forwarding state
May 10 22:59:49 pve chronyd[740]: Selected source 116.203.244.102 (2.debian.pool.ntp.org)
May 10 22:59:49 pve chronyd[740]: System clock TAI offset set to 37 seconds
May 10 22:59:50 pve pvesh[967]: Starting VM 102
May 10 22:59:50 pve pve-guests[1014]: start VM 102: UPID:pve:000003F6:0000094D:663E8AC6:qmstart:102:root@pam:
May 10 22:59:50 pve pve-guests[968]: <root@pam> starting task UPID:pve:000003F6:0000094D:663E8AC6:qmstart:102:root@pam:
May 10 22:59:51 pve systemd[1]: Started 102.scope.
May 10 22:59:52 pve kernel: tap102i0: entered promiscuous mode
May 10 22:59:52 pve kernel: vmbr0: port 3(tap102i0) entered blocking state
May 10 22:59:52 pve kernel: vmbr0: port 3(tap102i0) entered disabled state
May 10 22:59:52 pve kernel: tap102i0: entered allmulticast mode
May 10 22:59:52 pve kernel: vmbr0: port 3(tap102i0) entered blocking state
May 10 22:59:52 pve kernel: vmbr0: port 3(tap102i0) entered forwarding state
May 10 22:59:52 pve kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
May 10 22:59:52 pve kernel: cp210x 1-10:1.0: device disconnected
May 10 22:59:52 pve kernel: netfs: FS-Cache loaded
May 10 22:59:52 pve kernel: Key type cifs.spnego registered
May 10 22:59:52 pve kernel: Key type cifs.idmap registered
May 10 22:59:52 pve kernel: CIFS: Attempting to mount //192.168.1.105/Proxmox
May 10 22:59:55 pve pvesh[967]: Starting VM 103
May 10 22:59:55 pve pve-guests[968]: <root@pam> starting task UPID:pve:0000046E:00000B43:663E8ACB:qmstart:103:root@pam:
May 10 22:59:55 pve pve-guests[1134]: start VM 103: UPID:pve:0000046E:00000B43:663E8ACB:qmstart:103:root@pam:
May 10 22:59:56 pve systemd[1]: Started 103.scope.
May 10 22:59:57 pve kernel: tap103i0: entered promiscuous mode
May 10 22:59:57 pve kernel: vmbr0: port 4(fwpr103p0) entered blocking state
May 10 22:59:57 pve kernel: vmbr0: port 4(fwpr103p0) entered disabled state
May 10 22:59:57 pve kernel: fwpr103p0: entered allmulticast mode
May 10 22:59:57 pve kernel: fwpr103p0: entered promiscuous mode
May 10 22:59:57 pve kernel: vmbr0: port 4(fwpr103p0) entered blocking state
May 10 22:59:57 pve kernel: vmbr0: port 4(fwpr103p0) entered forwarding state
May 10 22:59:57 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
May 10 22:59:57 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
May 10 22:59:57 pve kernel: fwln103i0: entered allmulticast mode
May 10 22:59:57 pve kernel: fwln103i0: entered promiscuous mode
May 10 22:59:57 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
May 10 22:59:57 pve kernel: fwbr103i0: port 1(fwln103i0) entered forwarding state
May 10 22:59:57 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
May 10 22:59:57 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
May 10 22:59:57 pve kernel: tap103i0: entered allmulticast mode
May 10 22:59:57 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
May 10 22:59:57 pve kernel: fwbr103i0: port 2(tap103i0) entered forwarding state
May 10 22:59:58 pve kernel: usb 1-10: reset full-speed USB device number 2 using xhci_hcd
May 10 23:00:00 pve systemd[1]: systemd-fsckd.service: Deactivated successfully.
May 10 23:00:00 pve pve-guests[967]: <root@pam> end task UPID:pve:000003C8:00000756:663E8AC1:startall::root@pam: OK
May 10 23:00:00 pve systemd[1]: Finished pve-guests.service - PVE guests.
May 10 23:00:01 pve systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
May 10 23:00:01 pve pvescheduler[1233]: starting server
May 10 23:00:01 pve systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
May 10 23:00:01 pve systemd[1]: Reached target multi-user.target - Multi-User System.
May 10 23:00:01 pve systemd[1]: Reached target graphical.target - Graphical Interface.
May 10 23:00:01 pve systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
May 10 23:00:01 pve systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
May 10 23:00:01 pve systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
May 10 23:00:01 pve systemd[1]: Startup finished in 2.194s (kernel) + 32.509s (userspace) = 34.703s.
May 10 23:01:58 pve chronyd[740]: Selected source 162.159.200.123 (2.debian.pool.ntp.org)
May 10 23:02:00 pve chronyd[740]: Source 173.249.33.207 replaced with 78.46.53.2 (2.debian.pool.ntp.org)
-- Reboot --
May 10 23:05:07 pve kernel: Linux version 6.8.4-2-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.8.4-2 (2024-04-10T17:36Z) ()
May 10 23:05:07 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.4-2-pve root=/dev/mapper/pve-root ro quiet
May 10 23:05:07 pve kernel: KERNEL supported cpus:
May 10 23:05:07 pve kernel:   Intel GenuineIntel
May 10 23:05:07 pve kernel:   AMD AuthenticAMD
May 10 23:05:07 pve kernel:   Hygon HygonGenuine
May 10 23:05:07 pve kernel:   Centaur CentaurHauls
May 10 23:05:07 pve kernel:   zhaoxin   Shanghai 
May 10 23:05:07 pve kernel: BIOS-provided physical RAM map:
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cebaafff] usable
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x00000000cebab000-0x00000000cf98efff] reserved
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x00000000cf98f000-0x00000000cfb8efff] ACPI NVS
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x00000000cfb8f000-0x00000000cfc0efff] ACPI data
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x00000000cfc0f000-0x00000000cfc0ffff] usable
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x00000000cfc10000-0x00000000d67fffff] reserved
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved
May 10 23:05:07 pve kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008277fffff] usable
May 10 23:05:07 pve kernel: NX (Execute Disable) protection: active
May 10 23:05:07 pve kernel: APIC: Static calls initialized
May 10 23:05:07 pve kernel: efi: EFI v2.6 by HP
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back