[SOLVED] PVE Services can't be restarted

V

Voyaller

Member
Nov 15, 2020
17
2
8
My setup is the following
  • 2x Nodes
  • 1x common NFS storage for backups
  • fully updated by the time i'm writing this

I tried to live migrate a VM from one server to another but it failed so i stopped in. After that, the GUI stopped responding and i tried to restart the pve proxy.

I received this error:

Code: 
systemd[1]: pveproxy.service: Found left-over process 1126107 (pvecm) in control group while starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
systemd[1]: pveproxy.service: Found left-over process 1128503 (pvecm) in control group while starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
systemd[1]: pveproxy.service: Found left-over process 1130929 (pvecm) in control group while starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
systemd[1]: pveproxy.service: Found left-over process 1133305 (pvecm) in control group while starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
systemd[1]: pveproxy.service: Found left-over process 1135719 (pvecm) in control group while starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.

Then i tried to run

Code: 
service pve-cluster restart && service pvedaemon restart && service pvestatd restart && service pveproxy restart

And i got this output:

Code: 
pmxcfs[1144008]: [main] notice: unable to acquire pmxcfs lock - trying again
pmxcfs[1144008]: [main] notice: unable to acquire pmxcfs lock - trying again
pve-ha-lrm[1607]: updating service status from manager failed: Connection refused

I run sudo journalct -xe and i got errors like these:

Code: 
pvestatd[1558]: status update error: Connection refused
pve-ha-lrm[1607]: updating service status from manager failed: Connection refused
pve-ha-lrm[1607]: updating service status from manager failed: Connection refused
pve-firewall[1559]: status update error: Connection refused
pvestatd[1558]: ipcc_send_rec[1] failed: Connection refused
pvestatd[1558]: ipcc_send_rec[2] failed: Connection refused
pvestatd[1558]: ipcc_send_rec[3] failed: Connection refused
pvestatd[1558]: ipcc_send_rec[4] failed: Connection refused
pvestatd[1558]: status update error: Connection refused
sudo[1176792]: pam_unix(sudo:session): session closed for user root
pve-ha-lrm[1607]: updating service status from manager failed: Connection refused

Other issues:
  • /etc/pve is currently empty
Other info:
  • All the VM's are operational
My question is, can i start all those services again?

EDIT: Output from pveversion -v

Code: 
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-9
pve-kernel-5.13: 7.1-7
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-6
pve-kernel-5.13.19-4-pve: 5.13.19-8
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.4.140-1-pve: 5.4.140-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
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.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-network-perl: 0.6.2
libpve-storage-perl: 7.0-15
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
openvswitch-switch: 2.15.0+ds1-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
 
Last edited:
Without the pve-cluster services (aka pmxcfs - proxmox cluster file system) not much will happen.

Code: 
pmxcfs[1144008]: [main] notice: unable to acquire pmxcfs lock - trying again

Try to check if there still is some pmxcfs process running and kill it if necessary. Then try to restart the pve-cluster service. Or if you want to run it manually in the foreground to check against any problems directly: pmxcfs -f
 
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