accidently upgraded to 6.3 buster from 5.1 stretch

T

teddyh2o

New Member
Proxmox Subscriber
Jan 28, 2021
9
0
1
42
accidently upgraded to Proxmox 6.3 buster from 5.1 stretch without following the procedure.
the end user used
Code: 
deb http://download.proxmox.com/debian/pve buster pve-no-subscription
on stretch.
i changed the repository to stretch and try to install proxmox-ve but getting this error
Code: 
Reading package lists... Done
Building dependency tree
Reading state information... Done
proxmox-ve is already the newest version (6.3-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

i know this is a stupid user error but is it possible to reinstall/download to 5.1 or 5.3?
currently, pveproxy and pvedaemon are unstable to start
 
humm still not to run after 5.3 install. qm works fine.

pveversion -v
Code: 
proxmox-ve: 5.4-2 (running kernel: 5.4.106-1-pve)
pve-manager: 5.4-8 (running version: 5.4-8/51d494ca)
pve-kernel-5.4: 6.3-8
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph: 12.2.13-pve1~bpo9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libpve-access-control: 5.1-12
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.1.0-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 3.0-22
pve-firmware: 3.2-2
pve-ha-manager: 2.0-9
pve-i18n: 2.3-1
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 4.7.0-3
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

sources.list
Code: 
deb http://ftp.us.debian.org/debian stretch main contrib

deb http://ftp.us.debian.org/debian stretch-updates main contrib

deb http://ftp.debian.org/debian stretch-backports non-free

# security updates
deb http://security.debian.org stretch/updates main contrib

deb http://download.proxmox.com/debian stretch pve-no-subscription

error message from journalctl -xe
Code: 
pvedaemon[11020]: Experimental "my" subs not enabled at /usr/share/perl5/PVE/APIClient/LWP.pm line 278.
pvedaemon[11020]: Compilation failed in require at /usr/share/perl5/PVE/API2/ClusterConfig.pm line 12.
pvedaemon[11020]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/ClusterConfig.pm line 12.
pvedaemon[11020]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 17.
pvedaemon[11020]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 17.
pvedaemon[11020]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
pvedaemon[11020]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
pvedaemon[11020]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
pvedaemon[11020]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
pvedaemon[11020]: Compilation failed in require at /usr/bin/pvedaemon line 11.
pvedaemon[11020]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
systemd[1]: pvedaemon.service: Control process exited, code=exited status=255
 
It seems you have packages from both PVE 5 and PVE 6. For example, libpve-apiclient-perl 3.X is from PVE 6. Depending on the complexity and requirements of your setup, it might be less headache to create a fresh installation (directly with PVE 6?) and restore backups.
 
You must log in or register to reply here.
Top Bottom