issues while upgrade from proxmox 8.4 to 9

J

jossme

New Member
Aug 21, 2025
4
0
1
Hi to all guys. I'm new here. This is the first time i need your help for a problem i have in upgrading my proxmox distro.
my fault has been to not read deeply this guide and follow a youtube guy saying how was simple to upgrade proxmox.
So , in short what i dit ( try to remeber ) was to change a couple o files , specifically
/etc/apt/sources.list
-in this file i commented all lines starting with deb
-add new line with deb http://download.proxmox.com/debian/pve trixie pve-no-subscription
/etc/apt/sources.list.d/ceph.list
-in this file i commented all lines starting with deb
after that i tryied these commands
- apt update
- apt dist-upgrade

All seemed to go well until i noted some

FAILD message about pvedaemon.service , pveproxy.service, pvestatd.service, pvescheduler.service
so at the end i tryied to see journal with
Code: 
journalctl -xeu pvedaemon.service and  i got 
Aug 20 14:30:55 pve pveproxy[223477]: Attempt to reload PVE/HA/Config.pm aborted.
Aug 20 14:30:55 pve pveproxy[223477]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 14.
Aug 20 14:30:55 pve pveproxy[223477]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 14.
Aug 20 14:30:55 pve pveproxy[223477]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 15.
Aug 20 14:30:55 pve pveproxy[223477]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 15.
Aug 20 14:30:55 pve pveproxy[223477]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 13.
Aug 20 14:30:55 pve pveproxy[223477]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 13.
Aug 20 14:30:55 pve pveproxy[223477]: Compilation failed in require at /usr/bin/pveproxy line 11.
Aug 20 14:30:55 pve pveproxy[223477]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Aug 20 14:30:55 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=17/n/a
Aug 20 14:30:55 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Aug 20 14:30:55 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
Aug 20 14:30:55 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Aug 20 14:30:55 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Aug 20 14:30:55 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Aug 20 14:30:55 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Aug 20 14:30:55 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
so , this start my nightmare
pve was not working. what's grong. ?? I tryied to investigate launching a couple of commands and found that :
Code: 
cat /etc/osrelease
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Code: 
uname -a
Linux pve 6.8.12-9-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 (2025-03-16T19:18Z) x86_64 GNU/Linux
so i decide bookworm is still my current release , so i launch

Code: 
root@pve: proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
6.8.12-13-pve
6.8.12-9-pve

Pinned kernel:

root@pve: proxmox-boot-tool kernel pin 6.8.12-9-pve
root@pve: reboot

now i further investigate and i found that all proxmox packages has been update to trixie version like
libpve-common-perl/now 9.0.9 all [installed,local] ..for example

while other packages ( the one related to ceph and security that i commented repo ) still is in bookworm
ceph-common 17.2.8-pve2
ceph-fuse 17.2.8-pve2
libcephfs2 17.2.8-pve2
librados2 17.2.8-pve2
libradosstriper1 17.2.8-pve2
librbd1 17.2.8-pve2
librgw2 17.2.8-pve2
python3-ceph-argparse 17.2.8-pve2
python3-ceph-common 17.2.8-pve2
python3-cephfs 17.2.8-pve2
python3-rados 17.2.8-pve2
python3-rbd 17.2.8-pve2
python3-rgw 17.2.8-pve2

so i thought these mix of installed packages could be the problem for starting services.
can any one help me how solve this problem , nomalize the system restarting services and then upgrade to 9, ?
for now i pinned the current kernel so i can boot and make all other ordinary stauff.
 
Hi!

Which command have you used to upgrade the packages? It is important to always use apt dist-upgrade instead of apt upgrade as described in [0], because among other things the latter will make packages stay on a lower versioned package instead of resolving the package dependencies correctly.

jossme said:
/etc/apt/sources.list
-in this file i commented all lines starting with deb
-add new line with deb http://download.proxmox.com/debian/pve trixie pve-no-subscription
Click to expand...

You also need to replace bookworm with trixie for the Debian repositories themselves instead of commenting those out, that is you should add the Debian Trixie repositories next to the PVE 9 / Trixie repositories. Also check the files in /etc/apt/sources.d/ whether those contain any other bookworm-based repositories.

You can check pveversion -v for a list of the packages, they should at least show at the start:

Code: 
proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve)
pve-manager: 9.0.5 (running version: 9.0.5/9c5600b249dbfd2f)

Hope that helps upgrading your system!

[0] https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates
 
Hi , thanks for replay me.
after i changed repos i used
apt update
apt dist-upgrade
thanks for this command i didn' know

Code: 
pveversion -v
running this command i got
Code: 
proxmox-ve: 8.4.0 (running kernel: 6.8.12-9-pve)
pve-manager: 8.4.11 (running version: 8.4.11/14a32011146091ed)
proxmox-kernel-helper: 9.0.3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.14: 6.14.8-2
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
but with your suggestion i not solve my issue.

as i said i think i have some packages from trixie and other from bookwork.
what i want to know if I can remove trixie pakages and then reinstall these in bookworm and after that ( with system nomalized) retry to upgrade correctly to trixie...
what i don't know is what are the packages i have to remove ( withi their dependencies) ..

there is a place ( log or where i can find the primary trixie packages installed)
also could you confirm this could be the right approach ? or what else.
thanks
 
Last edited:
hi guys,
I come back to gently ask someone help to solve my trouble.
this guide is not enough to make mi undestand where i made a mistake

I would like to know if changing the correct repos ( for trixie) as i read in documentation , i mean these files

Code: 
cat > /etc/apt/sources.list.d/proxmox.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

cat > /etc/apt/sources.list.d/ceph.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/ceph-squid
Suites: trixie
Components: no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

and relaunch the commands
apt update
apt dist-upgrade

do the upgrade try to restore the missing file, and because of this, ri-align the pve system.
Or do i have to expect something wrong ?
 
hi , guys
often the olny hands that help you are the ones at the bottom of your arms.

that's to say that after checking and double checking and re-checking you (me) didn't see what is in front of your eyes.

in my case i was insisting to check the content of the two files /ect/apt/sources.list.d/ceph.sources and /ect/apt/sources.list.d/proxmox.sources
but i didn't noted i've not change the content of /etc/apt/source.list ....( that must contain the trixie repositories )
so i changed the content in
deb http://deb.debian.org/debian trixie main contrib
deb http://deb.debian.org/debian trixie-updates main contrib
deb http://security.debian.org/debian-security trixie-security main contrib

and then i re-launch
apt full-upgrade

this time all goes well ...and now i have proxmox to 9.0.5 version.
thank for your little support
 
You must log in or register to reply here.
Top Bottom