Proxmox broken at upgrade to 4.4-5.

[ulzha]

Hi!

We have 2 nodes in a cluster. After running upgrade we received message:

Setting up pve-manager (4.4-5) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script 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)

And systemctl status pvedaemon.service outputs:

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
   Active: failed (Result: exit-code) since Tue 2017-02-07 14:40:16 EET; 41s ago
  Process: 1511 ExecStart=/usr/bin/pvedaemon start (code=exited, status=2)

Feb 07 14:40:16 pmx01 pvedaemon[1511]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/C...e 13.
Feb 07 14:40:16 pmx01 pvedaemon[1511]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Feb 07 14:40:16 pmx01 pvedaemon[1511]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.p...e 13.
Feb 07 14:40:16 pmx01 pvedaemon[1511]: Compilation failed in require at /usr/share/perl5/PVE/Service/pv...ne 8.
Feb 07 14:40:16 pmx01 pvedaemon[1511]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Servic...ne 8.
Feb 07 14:40:16 pmx01 pvedaemon[1511]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Feb 07 14:40:16 pmx01 pvedaemon[1511]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Feb 07 14:40:16 pmx01 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Feb 07 14:40:16 pmx01 systemd[1]: Failed to start PVE API Daemon.
Feb 07 14:40:16 pmx01 systemd[1]: Unit pvedaemon.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

After reboot one node is down. Other one seems to be working just fine, but has not been rebooted yet. Has anyone encountered similar issue?

Thanks!

 

[tom]

I assume you didn´t follow the upgrade guide and you run "apt-get upgrade" instead of "apt-get dist-upgrade".?

See https://pve.proxmox.com/wiki/Downlo...Proxmox_Virtual_Environment_4.x_to_latest_4.4

 

[ulzha]

Yes, this is correct. Everything is up and running.
Will be more careful next time.

Thank you!