Proxmox UI is broken

[pJonathan]

Hello, I have a problem with the Proxmox UI ... as you can see in the attached image both the VM/LXC names and statuses and the system resources graphs are not callable. I have unfortunately not found on the internet, but also did not know what to look for explicitly ... maybe someone here can help me
After a reboot everything is normal for one or two days, then there are the problems mentioned.



EDIT: systemctl restart pvestatd helps .... but the problem occurs frequently

 

[Dunuin]

You should check the syslog or journal for error messages that might tell you what isn't working and why. For example journalctl -u pvestatd

 

[pJonathan]

You should check the syslog or journal for error messages that might tell you what isn't working and why. For example journalctl -u pvestatd

The journal shows the following:

May 16 17:39:36 pve systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
May 16 17:39:36 pve systemd[1]: pvestatd.service: Failed with result 'signal'.
May 16 17:39:36 pve systemd[1]: pvestatd.service: Consumed 18min 33.326s CPU time.

 

[bbgeek17]

https://phoenixnap.com/kb/sigsegv

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[pJonathan]

https://phoenixnap.com/kb/sigsegv

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

May 16 17:39:36 pve kernel: [51684.149123] pvestatd[14436]: segfault at 363fbbaee490 ip 0000363fbbaee490 sp 00007ffed0e81608 error 14 in perl[563fbb9b7000+47000]
May 16 17:39:36 pve kernel: [51684.149131] Code: Unable to access opcode bytes at RIP 0x363fbbaee466.
May 16 17:39:36 pve systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
May 16 17:39:36 pve systemd[1]: pvestatd.service: Failed with result 'signal'.
May 16 17:39:36 pve systemd[1]: pvestatd.service: Consumed 18min 33.326s CPU time.

This is the syslog output at this time, the arcticle doesn't really help me ...

 

[bbgeek17]

The article explains the "why" of 11/SEGV, ie memory access. Further searching forum for similar reports we find:
https://forum.proxmox.com/threads/proxmox-crashed-with-segfault-help.57426/
https://forum.proxmox.com/threads/pvestatd-segmentation-fault-segfault.109407/
https://forum.proxmox.com/threads/segmentation-fault-during-installation.125097/
https://forum.proxmox.com/tags/segfault/

There are two main choices: your specific configuration uncovered a rare latent bug in software or you have an issue with hardware.
When reporting an issue with software it is always helpful to provide software versions: pveversion -v

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[pJonathan]

root@pve:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.4-3
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.6
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-2
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

The article explains the "why" of 11/SEGV, ie memory access. Further searching forum for similar reports we find:
https://forum.proxmox.com/threads/proxmox-crashed-with-segfault-help.57426/
https://forum.proxmox.com/threads/pvestatd-segmentation-fault-segfault.109407/
https://forum.proxmox.com/threads/segmentation-fault-during-installation.125097/
https://forum.proxmox.com/tags/segfault/

There are two main choices: your specific configuration uncovered a rare latent bug in software or you have an issue with hardware.
When reporting an issue with software it is always helpful to provide software versions: pveversion -v

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I have a Z590 Mainboard with a i5 11400. I recently upgraded my RAM (not the same sticks) with some problems (BIOS reset several times). I'll go back to the original configuration and see if that's the problem.