Upgrade from pve-manager 4.1-22 to 4.1-33 fails

Mactive

New Member
Apr 21, 2016
9
0
1
27
Hello all,

I'm in a bit of a pickle here. I was running a recently upgraded (about a month ago) pve host and wanted to run update today. It failed on configuring pve-manager.
I only pull packages from the proxmox repo and security updates from debian.
# proxmox no subscription
deb http://download.proxmox.com/debian jessie pve-no-subscription
# security updates
deb http://security.debian.org/ jessie/updates main contrib


I have the following in journalctl
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: unknown file 'ha/fence.cfg' at /usr/share/perl5/PVE/Cluster.pm line 760, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 17, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 17, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in require at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in require at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in require at /usr/bin/pvedaemon line 11, <DATA> line 751.
Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11, <DATA> line 751.
Apr 21 17:19:03 activebackup1 systemd[1]: pvedaemon.service: control process exited, code=exited status=255
Apr 21 17:19:03 activebackup1 systemd[1]: Failed to start PVE API Daemon.
Apr 21 17:19:03 activebackup1 systemd[1]: Unit pvedaemon.service entered failed state.


I'm sure I'm missing some kind of dependency. Any help is much appreciated, all of my VMs are down!
 

Mactive

New Member
Apr 21, 2016
9
0
1
27
Resolved. I did not have the main jessie repo in my sources.list since in the past it had packages that were not compatible like a different version of OpenVSwitch. I added it back, ran update and dist-upgrade, and everything upgraded successfully. Back up and running.
 

Romkus

New Member
Nov 13, 2016
9
0
1
33
I just had same errors, but in some different reason: i had linked "stretch" version of ProxMox repository into "jessie" Debian to apt... Be never hurry.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!