[SOLVED] 4.4-5 Upgrade gone wrong?

mhammett

Renowned Member
Mar 11, 2009
161
2
83
DeKalb, Illinois, United States
I did an apt-get upgrade, resulting in the below errors. Thoughts?

Code:
Processing triggers for 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 (--unpack):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-4.4.35-1-pve
Errors were encountered while processing:
 pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@stl-prox1:~# systemctl status pvedaemon.service
â pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
   Active: active (running) (Result: exit-code) since Fri 2017-02-24 07:50:17 CST; 1 day 23h ago
  Process: 17262 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=2)
 Main PID: 1723 (pvedaemon)
   CGroup: /system.slice/pvedaemon.service
           ââ 1723 pvedaemon
           ââ 1988 [lxc monitor] /var/lib/lxc 106
           ââ 3306 pvedaemon worker
           ââ29304 [lxc monitor] /var/lib/lxc 105
           ââ29589 pvedaemon worker
           ââ32138 pvedaemon worker

Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Feb 26 07:18:20 stl-prox1 pvedaemon[17262]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Feb 26 07:18:20 stl-prox1 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Feb 26 07:18:20 stl-prox1 systemd[1]: Reload failed for PVE API Daemon.
 
You should never do an apt-get upgrade, always apt-get dist-upgrade

If you try and run apt-get dist-upgrade this could/may fix your situation.
 
  • Like
Reactions: mhammett

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!

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!