pvestatd causing unresponsive status in web GUI

Coolguy3289

Member
Mar 10, 2017
20
0
6
23
Ohio
primeserversinc.com
Hello,
I've just added a 4th node to my existing proxmox cluster, and I'm running into an intermittent issue with the status of the node and VMs on that node turning to the gray question mark, storage stats not loading. When I run `systemctl status pvestatd` the service shows as running. When I try to restart the service it hangs on the following:
Code:
Jun 29 17:37:19 vm4 pvestatd[33691]: received signal TERM
Jun 29 17:37:19 vm4 pvestatd[33691]: server closing
Jun 29 17:37:19 vm4 pvestatd[33691]: server stopped
Jun 29 17:38:50 vm4 systemd[1]: pvestatd.service: State 'stop-sigterm' timed out. Killing.
Jun 29 17:38:50 vm4 systemd[1]: pvestatd.service: Killing process 6339 (lvs) with signal SIGKILL.
Jun 29 17:38:50 vm4 systemd[1]: pvestatd.service: Killing process 33803 (vgs) with signal SIGKILL.
Jun 29 17:40:20 vm4 systemd[1]: pvestatd.service: Processes still around after SIGKILL. Ignoring.
These processes not killing seems to hang the restart process with pvestatd.

System info:
Code:
root@vm4:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.44-1-pve)
pve-manager: 6.2-6 (running version: 6.2-6/ee1d7754)
pve-kernel-5.4: 6.2-3
pve-kernel-helper: 6.2-3
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.44-1-pve: 5.4.44-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve2
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-3
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-8
pve-cluster: 6.1-8
pve-container: 3.1-8
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1
 

Coolguy3289

Member
Mar 10, 2017
20
0
6
23
Ohio
primeserversinc.com
I've considered ceph, and def appreciate the video since it will help me when I decide to switch. At the moment I don't have the time to do so. Do you think that has something to do with this issue?
 

About

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

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 your own in 60 seconds.

Buy now!