Upgrade Failed, Cannot Continue?

A

Andy Huang

Renowned Member
Jan 1, 2013
32
1
73
I tried to run:

Code: 
apt-get upgrade

It results in failure for these packages:
Code: 
Errors were encountered while processing:
pve-firewall
qemu-server
pve-manager
proxmox-ve
pve-ha-manager
pve-container

When I try to run the debug command, I get this:

Code: 
$ journalctl -xn
-- Logs begin at Tue 2015-12-08 05:54:22 PST, end at Mon 2016-05-09 13:42:49 PDT. --
May 09 13:42:49 shana-host pve-firewall[23910]: Attempt to reload PVE/LXC.pm aborted.
May 09 13:42:49 shana-host pve-firewall[23910]: Compilation failed in require at /usr/share/perl5/PVE/FirewallSimulator.pm line 9, <DATA> line 751.
May 09 13:42:49 shana-host pve-firewall[23910]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/FirewallSimulator.pm line 9, <DATA> line 751.
May 09 13:42:49 shana-host pve-firewall[23910]: Compilation failed in require at /usr/share/perl5/PVE/Service/pve_firewall.pm line 16, <DATA> line 751.
May 09 13:42:49 shana-host pve-firewall[23910]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pve_firewall.pm line 16, <DATA> line 751.
May 09 13:42:49 shana-host pve-firewall[23910]: Compilation failed in require at /usr/sbin/pve-firewall line 6, <DATA> line 751.
May 09 13:42:49 shana-host pve-firewall[23910]: BEGIN failed--compilation aborted at /usr/sbin/pve-firewall line 6, <DATA> line 751.
May 09 13:42:49 shana-host systemd[1]: pve-firewall.service: control process exited, code=exited status=255
May 09 13:42:49 shana-host systemd[1]: Failed to start Proxmox VE firewall.
-- Subject: Unit pve-firewall.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pve-firewall.service has failed.
--
-- The result is failed.
May 09 13:42:49 shana-host systemd[1]: Unit pve-firewall.service entered failed state.

Here's my version info:
Code: 
$ pveversion
pve-manager/4.2-4/2660193c (running kernel: 4.2.2-1-pve)

Can anyone please advise?
 
I wanted to do upgrade first to get to latest available in the same branch before I do dist-upgrade, but this definitely fixed the problem for me. Thanks!
 
Interesing. I've always the this for full upgrades.

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

So, for this one I then had to do
apt-get -y dist-upgrade
then
apt-get -y upgrade
 
You must log in or register to reply here.
Top Bottom