Proxmox not running after upgrade to 5.0

[Henrique]

Hey all!

I was doing an upgrade in my test machine, following the instructions in https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0. When I did the dist-upgrade, I let the server upgrade it self.

After a reboot, I don't have a web interface, and all the services are inactive and masked:

● pveproxy.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

I tried running pveversion, and there is no such command. However, running `pvesm`, I get the following error:

Can't locate PVE/Cluster.pm in @INC (you may need to install the PVE::Cluster module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/PVE/CLI/pvesm.pm line 10.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pvesm.pm line 10.
Compilation failed in require at /usr/sbin/pvesm line 6.
BEGIN failed--compilation aborted at /usr/sbin/pvesm line 6.

What can I do? What did go wrong?

Thanks!

 

[dietmar]

are you sure you did

# apt get update
# apt-get dist-upgrade

 

[Henrique]

Yup, I'm sure, otherwise it wouldn't have failed to load proxmox and I wouldn't be in the latest Debian. I was able to fix it using some systemd and apt-get vudu.

For reference, I basically followed the instructions to install Proxmox on Debian (https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch), so I did reinstalled all the Proxmox packages, kind of. I had some issues with dpkg configuration of the pve packages, which I fixed by unmasking the pve-firewall service using

systemctl unmask pve-firewall.service

.

Still not sure why all the pve services were masked in the first place, but at least it's now running just fine.

root@whale:~# pveversion
pve-manager/5.0-23/af4267bf (running kernel: 4.4.35-1-pve)

 

[AaronWalker]

Side note, I had this same issue about a month ago. I believe I installed a non-pve version of a package and it caused similar issues.