pve-manager failed to update

[LolekUK]

Hi,

My pve-manager failed to update to the latest version this morning and now the service won't start, any thoughts?

I can access the host via SSH, info below:

apt update etc.
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://ftp.debian.org/debian bullseye InRelease Hit:3 http://ftp.debian.org/debian bullseye-updates InRelease Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease Get:5 https://dl.cloudsmith.io/public/pve-edge/kernel/deb/debian bullseye InRelease [5,168 B] Fetched 5,168 B in 0s (13.4 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libpve-common-perl libpve-rs-perl 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up pve-manager (7.1-11) ... Job for pvedaemon.service failed because the control process exited with error code. 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 Errors were encountered while processing: pve-manager E: Sub-process /usr/bin/dpkg returned an error code (1)

systemctl status

systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-03-24 10:28:14 GMT; 49s ago
    Process: 5590 ExecStart=/usr/bin/pvedaemon start (code=exited, status=2)
        CPU: 560ms

Mar 24 10:28:14 vmh systemd[1]: pvedaemon.service: Scheduled restart job, restart counter is at 5.
Mar 24 10:28:14 vmh systemd[1]: Stopped PVE API Daemon.
Mar 24 10:28:14 vmh systemd[1]: pvedaemon.service: Start request repeated too quickly.
Mar 24 10:28:14 vmh systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Mar 24 10:28:14 vmh systemd[1]: Failed to start PVE API Daemon.

journalctl -xe

Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Mar 24 10:28:14 vmh systemd[1]: Failed to start PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 3370 and the job result is failed.
Mar 24 10:28:14 vmh systemd[1]: pvedaemon.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pvedaemon.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Mar 24 10:28:14 vmh systemd[1]: Stopped PVE API Daemon.
░░ Subject: A stop job for unit pvedaemon.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pvedaemon.service has finished.
░░
░░ The job identifier is 3461 and the job result is done.
Mar 24 10:28:14 vmh systemd[1]: pvedaemon.service: Start request repeated too quickly.
Mar 24 10:28:14 vmh systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Mar 24 10:28:14 vmh systemd[1]: Failed to start PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 3461 and the job result is failed.

 

[fabian]

did you maybe use 'apt upgrade' instead of 'apt dist-upgrade'?

anyhow, resetting the failed status of the service in question should give you the actual error:

systemctl reset-failed pvedaemon
systemctl restart pvedaemon
journalctl --since "-1min" -u pvedaemon

 

[LolekUK]

Ah, running only apt dist-upgrade fixed it!

I normally run them all at the same time, shall I not do it, do it in different order?

apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y && apt-get autoremove -y && apt-get autoclean -y

Thank you @fabian

 

[fabian]

apt-get upgrade is not needed and can be harmful because of the way PVE updates work (compared to Debian, which only ships major bug fixes and security fixes during the life time of a release, PVE also introduces new features, which sometimes require introducing breaking dependency relations, dependencies on new internal or third-party packages, and so on)

 

[LolekUK]

apt-get upgrade is not needed and can be harmful because of the way PVE updates work (compared to Debian, which only ships major bug fixes and security fixes during the life time of a release, PVE also introduces new features, which sometimes require introducing breaking dependency relations, dependencies on new internal or third-party packages, and so on)

Thank you, I will stop running it!