Code:
root@host:~# service pvestatd status
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled)
Active: deactivating (final-sigkill) (Result: timeout) since Tue 2017-05-16 08:42:37 CEST; 9min ago
Process: 25511 ExecStop=/usr/bin/pvestatd stop (code=exited, status=0/SUCCESS)
Process: 26219 ExecStart=/usr/bin/pvestatd start (code=exited, status=255)
Main PID: 1706
CGroup: /system.slice/pvestatd.service
└─1706 pvestatd
May 16 08:48:55 host pvestatd[26219]: start failed - can't aquire lock '/var/run/pvestatd.pid.lock' - Resource temporarily unavailable
May 16 08:48:55 host pvestatd[26219]: start failed - can't aquire lock '/var/run/pvestatd.pid.lock' - Resource temporarily unavailable
May 16 08:48:55 host systemd[1]: pvestatd.service: control process exited, code=exited status=255
May 16 08:50:25 host systemd[1]: pvestatd.service stop-final-sigterm timed out. Killing.Can't start pvestatd
Pveproxy is running
Is a Cluster node
kill -9 already tried
Code:
root@host:~# pveversion -v
proxmox-ve: 4.4-84 (running kernel: 4.4.44-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-109
pve-firmware: 1.1-10
libpve-common-perl: 4.0-94
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-96
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80service pvestatd start
Job for pvestatd.service failed. See 'systemctl status pvestatd.service' and 'journalctl -xn' for details.
Last edited:
