Upgrade failure for 7.4 (pve-manager)

[j1a2o]

Using apt dist-upgrade:

Setting up pve-manager (7.4-3) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
 installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Logs in systemctl status pvedaemon.service:

Mar 23 10:19:25 pve systemd[1]: Reloading PVE API Daemon.
Mar 23 10:19:30 pve pvedaemon[829892]: start failed - can't acquire lock '/var/run/pvedaemon.pid.lock' - Resource temporarily unavailable
Mar 23 10:19:30 pve pvedaemon[829892]: start failed - can't acquire lock '/var/run/pvedaemon.pid.lock' - Resource temporarily unavailable
Mar 23 10:19:30 pve systemd[1]: pvedaemon.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 23 10:19:30 pve systemd[1]: Reload failed for PVE API Daemon.

Looks like pvedaemon.pid.lock exists but pvedaemon.pid is missing. Not sure if expected.

 

[j1a2o]

I solved it by looking up the pid of the running pvedaemon, putting it in a new /var/run/pvedaemon.pid file, and then running apt dist-upgrade again. Everything looks good now. Not sure why pvedaemon.pid was missing in the first place.

 

[tuxick]

In my case i found an old lock file, removed that and started pvedaemon.