Upgrade to 4.x Failing

webbytech

New Member
Mar 27, 2011
18
0
1
/etc/hosts file is correct, dpkg --configure -a has been ran and I still get errors
Any help would be appreciated:

root@proxmox2:~# apt-get install proxmox-ve

Reading package lists... Done

Building dependency tree

Reading state information... Done

The following extra packages will be installed:

pve-container pve-firewall pve-ha-manager pve-manager qemu-server

The following NEW packages will be installed:

proxmox-ve pve-container pve-firewall pve-ha-manager pve-manager qemu-server

0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.

Need to get 0 B/5,438 kB of archives.

After this operation, 1,043 kB of additional disk space will be used.

Do you want to continue? [Y/n] y

Preconfiguring packages ...

Selecting previously unselected package pve-firewall.

(Reading database ... 49854 files and directories currently installed.)

Preparing to unpack .../pve-firewall_2.0-29_amd64.deb ...

Unpacking pve-firewall (2.0-29) ...

Selecting previously unselected package pve-ha-manager.

Preparing to unpack .../pve-ha-manager_1.0-32_amd64.deb ...

Unpacking pve-ha-manager (1.0-32) ...

Selecting previously unselected package qemu-server.

Preparing to unpack .../qemu-server_4.0-85_amd64.deb ...

Unpacking qemu-server (4.0-85) ...

Selecting previously unselected package pve-container.

Preparing to unpack .../pve-container_1.0-71_all.deb ...

Unpacking pve-container (1.0-71) ...

Selecting previously unselected package pve-manager.

Preparing to unpack .../pve-manager_4.2-17_amd64.deb ...

Unpacking pve-manager (4.2-17) ...

Selecting previously unselected package proxmox-ve.

Preparing to unpack .../proxmox-ve_4.2-58_all.deb ...

Unpacking proxmox-ve (4.2-58) ...

Processing triggers for man-db (2.7.0.2-5) ...

Processing triggers for systemd (215-17+deb8u4) ...

Setting up pve-firewall (2.0-29) ...

Failed to reload-or-restart pve-firewall.service: Unit pve-firewall.service is masked.

dpkg: error processing package pve-firewall (--configure):

subprocess installed post-installation script returned error exit status 1

dpkg: dependency problems prevent configuration of qemu-server:

qemu-server depends on pve-firewall; however:

Package pve-firewall is not configured yet.


dpkg: error processing package qemu-server (--configure):

dependency problems - leaving unconfigured

dpkg: dependency problems prevent configuration of pve-manager:

pve-manager depends on qemu-server (>= 1.1-1); however:

Package qemu-server is not configured yet.

pve-manager depends on pve-firewall; however:

Package pve-firewall is not configured yet.


dpkg: error processing package pve-manager (--configure):

dependency problems - leaving unconfigured

dpkg: dependency problems prevent configuration of proxmox-ve:

proxmox-ve depends on pve-manager; however:

Package pve-manager is not configured yet.

proxmox-ve depends on qemu-server; however:

Package qemu-server is not configured yet.


dpkg: error processing package proxmox-ve (--configure):

dependency problems - leaving unconfigured

dpkg: dependency problems prevent configuration of pve-ha-manager:

pve-ha-manager depends on qemu-server; however:

Package qemu-server is not configured yet.


dpkg: error processing package pve-ha-manager (--configure):

dependency problems - leaving unconfigured

dpkg: dependency problems prevent configuration of pve-container:

pve-container depends on pve-ha-manager; however:

Package pve-ha-manager is not configured yet.


dpkg: error processing package pve-container (--configure):

dependency problems - leaving unconfigured

Errors were encountered while processing:

pve-firewall

qemu-server

pve-manager

proxmox-ve

pve-ha-manager

pve-container

E: Sub-process /usr/bin/dpkg returned an error code (1)
 
I have the same errors today. So sad. And can't fix it.
20160723_B1JeyVHU.png
 
make sure that you follow the upgrade docs exactly, maybe you missed a reboot.?
 
"apt-get upgrade" is the wrong command.

read the upgrade docs again.
 
p.s. kernel panic was not after upgrade, but after install proxmox-ve - my mistake, sorry
- - - -
Remove Proxmox VE 3.x packages in order to avoid dependency errors - Done all
Install the new kernel - Done
Upgrade the basic system to Debian Jessie - Done
Reboot
Install Proxmox VE 4.0:

apt-get install proxmox-ve
kernel panic
reboot
System start without bridge. Up eth0. Install proxmox-ve again and have errors.



 
Last edited:
My fix was unmasking the pve.firewall service, it then installed and configured everything properly

Note: This is not part of the instructions.
 
My fix was unmasking the pve.firewall service, it then installed and configured everything properly

Note: This is not part of the instructions.
no need to mask that service - simply don't enable the firewall in the web interface?
 
We don't use the firewall, however during the upgrade it apparently masked. As son as I uninstalled pve-firewall, unmasked and then ran the upgrade again it worked fine.