[SOLVED] Accidental 5 upgrade, now massive problems

AZTricky

New Member
Mar 11, 2013
3
0
1
So yesterday I was updating my servers, completely unaware that 5 came out. So I apparently accidently upgraded from 4.4 to 5 and now my servers are having major issues.

Firstly, the web GUI will not come up. 2nd, have my CLI commands look like this.
Code:
root@proxmox4s1:~# qm
unknown file 'replication.cfg' at /usr/share/perl5/PVE/Cluster.pm line 765, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/AbstractConfig.pm line 11, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/AbstractConfig.pm line 11, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/QemuServer.pm line 30, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuServer.pm line 30, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/CLI/qm.pm line 19, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/qm.pm line 19, <DATA> line 751.
Compilation failed in require at /usr/sbin/qm line 6, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/sbin/qm line 6, <DATA> line 751.
root@proxmox4s1:~# pvproxy
-bash: pvproxy: command not found
root@proxmox4s1:~# pveproxy
unknown file 'replication.cfg' at /usr/share/perl5/PVE/Cluster.pm line 765, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/AbstractConfig.pm line 11, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/AbstractConfig.pm line 11, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 10, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 17, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 14, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 14, <DATA> line 751.
Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 751.
BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 751.
root@proxmox4s1:~# pveversion
pve-manager/5.0-23/af4267bf (running kernel: 4.10.17-1-pve)

Now my VMs are down, I can't lose my VMs via reinstall and I'm completely lost on what to do.
 
"accidently"?

how can this happen, you have a long procedure to follow, so this CANNOT happen by accident.

so please describe in full detail what you have done.
 
  • Like
Reactions: AZTricky
I should of stated "I'm really dumb and bad' instead of 'accidentally' and I figured out my mistake shortly after I wrote my first post. What I had did was update my sources.list with pve-no-subscription and failed to notice it said stretch. So it looked like this
Code:
deb [urlchangedbecauseimanewuser] jessie main contrib
deb [urlchangedbecauseimanewuser] stretch pve-no-subscription
# security updates
deb [urlchangedbecauseimanewuser] jessie/updates main contrib

Ran the updates, rebooted, and wound up in my uneasy place. To fix, I essentially went through the 4.4 to 5 upgrade by updating my sources and apt-get dist-upgrade and I was very lucky for that to work. Sorry for wasting anyones time by being a complete and utter dumbass.