Server unintentionally reboot

C

chchia

Active Member
Aug 18, 2020
82
30
38
47
journalctl show following error, where pbs is my proxmox backup server which was powered off, and i dont think it caused the reboot.

May 16 06:09:52 proxmox kernel: BUG: kernel NULL pointer dereference, address: 00000000000000a0

Code: 
proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.4-3
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.8.1-1-pve-signed: 6.8.1-1
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5: 6.5.13-5
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.1
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.2-1
proxmox-backup-file-restore: 3.2.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.6
pve-container: 5.1.10
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.0
pve-firewall: 5.0.7
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.2.2-1
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2

Code: 
May 16 06:09:29 proxmox pvestatd[1877]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 16 06:09:39 proxmox pvestatd[1877]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 16 06:09:42 proxmox kernel: [UFW BLOCK] IN=vmbr0 OUT= MAC=01:00:5e:00:00:01:c8:7f:54:c2:c1:30:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=55670 DF PROTO=2
May 16 06:09:49 proxmox pvestatd[1877]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 16 06:09:52 proxmox kernel: BUG: kernel NULL pointer dereference, address: 00000000000000a0
-- Boot 39c6298cd97e4535b87fbd3a73eafcb2 --
May 16 06:10:30 proxmox kernel: Linux version 6.8.4-3-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-3 (2024-05>
May 16 06:10:30 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.4-3-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt intel_pstate=disable initcall_blacklist=sysfb_>
May 16 06:10:30 proxmox kernel: KERNEL supported cpus:
May 16 06:10:30 proxmox kernel:   Intel GenuineIntel
May 16 06:10:30 proxmox kernel:   AMD AuthenticAMD
May 16 06:10:30 proxmox kernel:   Hygon HygonGenuine
May 16 06:10:30 proxmox kernel:   Centaur CentaurHauls
May 16 06:10:30 proxmox kernel:   zhaoxin   Shanghai
May 16 06:10:30 proxmox kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
May 16 06:10:30 proxmox kernel: BIOS-provided physical RAM map:
 
Last edited:
the second reboot today which did not show any error:

Code: 
May 16 15:38:36 proxmox pvestatd[1871]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 16 15:38:43 proxmox kernel: [UFW BLOCK] IN=vmbr0 OUT= MAC=01:00:5e:00:00:01:c8:7f:54:c2:c1:30:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=42000 DF PROTO=2
May 16 15:38:45 proxmox pvestatd[1871]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
-- Boot 2f4b2065847b461490660ed8c47f2775 --
May 16 15:39:39 proxmox kernel: Linux version 6.8.4-3-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-3 (2024-05>
May 16 15:39:39 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.4-3-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt intel_pstate=disable initcall_blacklist=sysfb_>
May 16 15:39:39 proxmox kernel: KERNEL supported cpus:
 
it happen again today in the middle of the night where no one is using the server nor VM......

Code: 
May 18 04:17:50 proxmox pvestatd[2081]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 18 04:18:00 proxmox pvestatd[2081]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 18 04:18:11 proxmox pvestatd[2081]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 18 04:18:20 proxmox pvestatd[2081]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 18 04:18:30 proxmox pvestatd[2081]: pbs: error fetching datastores - 500 Can't connect to 192.168.1.13:8007 (No route to host)
May 18 04:18:34 proxmox kernel: BUG: kernel NULL pointer dereference, address: 00000000000000a0
-- Boot e705514f03d346cf8ac953882668509d --
May 18 11:11:36 proxmox kernel: Linux version 6.8.4-3-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-3 (2024-05->
May 18 11:11:36 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.4-3-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt intel_pstate=disable initcall_blacklist=sysfb_i>
May 18 11:11:36 proxmox kernel: KERNEL supported cpus:
May 18 11:11:36 proxmox kernel:   Intel GenuineIntel
May 18 11:11:36 proxmox kernel:   AMD AuthenticAMD
May 18 11:11:36 proxmox kernel:   Hygon HygonGenuine
May 18 11:11:36 proxmox kernel:   Centaur CentaurHauls
May 18 11:11:36 proxmox kernel:   zhaoxin   Shanghai 
May 18 11:11:36 proxmox kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
 
These things are usually hardware related. Do you use ECC memory? Otherwise run a memtest. Then start replacing hardware parts until you find the problem.

EDIT: Maybe boot the system with the Ubuntu 24.04 installer and stess the system to see if it also happens without Proxmox.
 
Last edited:
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