pvestatd segfault

[GarrettB]

Had this show up in logwatch:

WARNING:  Segmentation Faults in these executables
    pvestatd :  1 Time(s)
 
 1 Time(s): Code: 76 01 00 00 48 8b 52 10 49 89 f7 89 cd 48 8d 04 c2 4c 8b 28 48 89 44 24 20 4d 85 ed 0f 84 94 00 00 00 4c 89 eb 0f 1f 44 00 00 <48> 8b 43 08 39 28 75 78 48 63 48 04 4c 39 e1 75 6f 48 8d 78 08 4c

 

[GarrettB]

This is the visible difference.



service pvestatd status showed the service failed. I restarted it, and it is working okay again.

 

[_gabriel]

host cpu model ?
ryzen 1st Gen ?

 

[GarrettB]

No, but AMD - an old FX-8350.

 

[fabian]

could you post your 'pveversion -v' output and the full segfault report from syslog/journal? thanks!

 

[GarrettB]

@fabian Yes, happy to.

root@pve:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-4.15: 5.4-6
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.17-1-pve: 4.15.17-9
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-1
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.1-1
proxmox-backup-file-restore: 2.2.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-7
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

I found this:

May 20 03:29:37 pve kernel: [192830.132411] pvestatd[1406]: segfault at 9 ip 000055831ff5af90 sp 00007ffcae094340 error 4 in perl[55831fea3000+185000]
May 20 03:29:37 pve systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
May 20 03:29:37 pve systemd[1]: pvestatd.service: Failed with result 'signal'.
May 20 03:29:37 pve systemd[1]: pvestatd.service: Consumed 35min 22.312s CPU time.

Nothing else appears to have occurred before or after.

 

[fabian]

please check
- that your memory is okay (e.g., memtest86)
- that your on-disk files are correct (e.g., using debsums)

 

[GarrettB]

Files looked alright, but memtest86 test 7 turned up a bad address on one of the cards. I'll be swapping that one out for a spare. Thanks for your help.