[SOLVED] PVE Manager does not start - no obvious reason found

[apoc]

Hello guys,

hope your doing fine.
I am having an issue which I am trying to track. I am not successful in finding a solution.
Since a few days my upgrade of the PVE host failed. I have decided to do a reboot since kernel upgrades were pending.
After the reboot pve manager is not started. VMs are not started automatically as well. Was able to start VMs via "qm" command.

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 pvedaemon.service returns

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: activating (start) since Sat 2022-03-26 21:31:27 CET; 1s ago
Cntrl PID: 58270 (pvedaemon)
      Tasks: 1 (limit: 154542)
     Memory: 77.5M
        CPU: 1.138s
     CGroup: /system.slice/pvedaemon.service
             └─58270 /usr/bin/perl -T /usr/bin/pvedaemon start

journalctl -xe does not show any obvious.

sudo pveversion
pve-manager/7.1-11/8d529482 (running kernel: 5.13.19-6-pve)

Thanks for your help

 

[fiona]

Hi,
does the systemctl status output really end there? What is the output of journalctl -b -u pvedaemon.service and pveversion -v?

 

[fabian]

The following packages have been kept back:
  libpve-common-perl libpve-rs-perl

you used apt upgrade instead of apt full-upgrade..

 

[apoc]

does the systemctl status output really end there?

Yes it does indeed end there.

you used apt upgrade instead of apt full-upgrade.

that is true. My script uses this since years. Will check back if that helps/works.

Thanks so far @fabian and @Fabian_E

 

[apoc]

sudo pveupdate
sudo pveupgrade

This did the trick for me. I am still wondering why my script worked for years and suddenly it did not do it anymore.
Thanks for your help.