Cannot start pvedaemon after rebooting.

W

Wanabekeats

Member
Jul 17, 2022
4
0
6
Hi Guys ,I meet this problem when I found that the webUI couldn`t open.
I try to check pve service and found this .
Code: 
[root@pve ~]# systemctl | grep pve
  etc-pve.mount                                                                                                                  loaded active     mounted   /etc/pve
  mnt-pve-mirror.mount                                                                                                           loaded active     mounted   Mount storage 'mirror' under /mnt/pve
  pve-cluster.service                                                                                                            loaded active     running   The Proxmox VE cluster filesystem
  pve-firewall.service                                                                                                           loaded active     running   Proxmox VE firewall
● pve-guests.service                                                                                                             loaded failed     failed    PVE guests
● pve-ha-crm.service                                                                                                             loaded failed     failed    PVE Cluster HA Resource Manager Daemon
● pve-ha-lrm.service                                                                                                             loaded failed     failed    PVE Local HA Resource Manager Daemon
  pve-lxc-syscalld.service                                                                                                       loaded active     running   Proxmox VE LXC Syscall Daemon
  pve-query-machine-capabilities.service                                                                                         loaded active     exited    PVE Query Machine Capabilities
  pvebanner.service                                                                                                              loaded active     exited    Proxmox VE Login Banner
● pvedaemon.service                                                                                                              loaded failed     failed    PVE API Daemon
  pvefw-logger.service                                                                                                           loaded active     running   Proxmox VE firewall logger
  pvenetcommit.service                                                                                                           loaded active     exited    Commit Proxmox VE network changes
● pveproxy.service                                                                                                               loaded failed     failed    PVE API Proxy Server
● pvescheduler.service                                                                                                           loaded failed     failed    Proxmox VE scheduler
● pvestatd.service                                                                                                               loaded failed     failed    PVE Status Daemon
  dev-pve-swap.swap                                                                                                              loaded active     active    /dev/pve/swap
  pve-storage.target                                                                                                             loaded active     active    PVE Storage Target
  pve-daily-update.timer                                                                                                         loaded active     waiting   Daily PVE download activities

I don`t know why too many pve service couldn`t start. So try to check the problem

Code: 
May 28 20:51:41 pve systemd[1]: Starting pvestatd.service - PVE Status Daemon...
░░ Subject: A start job for unit pvestatd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvestatd.service has begun execution.
░░
░░ The job identifier is 104.
May 28 20:51:41 pve pvestatd[4546]: Bareword "PVE::Syscall::fallocate" not allowed while "strict subs" in use at /usr/share/perl5/PVE/Storage/Common.pm line 105, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvestatd.pm line 19, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvestatd.pm line 19, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/bin/pvestatd line 9, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/bin/pvestatd line 9, <DATA> line 960.
May 28 20:51:41 pve systemd[1]: pvestatd.service: Control process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pvestatd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
May 28 20:51:41 pve systemd[1]: pvestatd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvestatd.service has entered the 'failed' state with result 'exit-code'.
May 28 20:51:41 pve systemd[1]: Failed to start pvestatd.service - PVE Status Daemon.
░░ Subject: A start job for unit pvestatd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvestatd.service has finished with a failure.
░░
░░ The job identifier is 104 and the job result is failed.
Code: 
[root@pve ~]# journalctl -xeu pveproxy.service
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 1068.
May 28 20:51:44 pve pveproxy[4603]: Bareword "PVE::Syscall::fallocate" not allowed while "strict subs" in use at /usr/share/perl5/PVE/Storage/Common.pm line 105, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/GuestHelpers.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/GuestHelpers.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 13, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 13, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 960.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
May 28 20:51:44 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 1068 and the job result is failed.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
May 28 20:51:44 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
░░ Subject: A stop job for unit pveproxy.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pveproxy.service has finished.
░░
░░ The job identifier is 1179 and the job result is done.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
May 28 20:51:44 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 1179 and the job result is failed.
I don`t have any idea , what should I do?
 
You either had an incomplete/failed upgrade or a failing disk. There are a few discussions of similar symptoms that may be helpful, i.e.:
N

[SOLVED] Thread 'Issue after update'

I updated my server today from the UI and rebooted, not realizing the download server was unavailable. After poking around in the command line for a while, I realized the issue and changed to one of the other cdn servers and ran the update-distro command. Now, I'm having issues with pve-proxy, pve-guests, and pvedaemon. All three give me the following error:

Code: 
Mar 13 12:52:35 *********** pvedaemon[2372]: Experimental "my" subs not enabled at /usr/share/perl5/PVE/APIClient/LWP.pm line 278.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at...

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Hi,
please share the output of pveversion -v, apt update and apt list --upgradable.
 
bbgeek17 said:
You either had an incomplete/failed upgrade or a failing disk. There are a few discussions of similar symptoms that may be helpful, i.e.:
N

[SOLVED] Thread 'Issue after update'

I updated my server today from the UI and rebooted, not realizing the download server was unavailable. After poking around in the command line for a while, I realized the issue and changed to one of the other cdn servers and ran the update-distro command. Now, I'm having issues with pve-proxy, pve-guests, and pvedaemon. All three give me the following error:

Code: 
Mar 13 12:52:35 *********** pvedaemon[2372]: Experimental "my" subs not enabled at /usr/share/perl5/PVE/APIClient/LWP.pm line 278.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at...

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
HI bbgeek17 ,thank you for your reply ,I read your advice and found one disk had problem, but I`m not sure it is helpful , but thank you.
 
fiona said:
Hi,
please share the output of pveversion -v, apt update and apt list --upgradable.
Click to expand...
pveversion -v
Code: 
pveversion -v
Bareword "PVE::Syscall::fallocate" not allowed while "strict subs" in use at /usr/share/perl5/PVE/Storage/Common.pm line 105, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/API2Tools.pm line 18, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2Tools.pm line 18, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/API2/APT.pm line 25, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/APT.pm line 25, <DATA> line 960.
Compilation failed in require at /usr/bin/pveversion line 7, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/bin/pveversion line 7, <DATA> line 960.

apt update
Code: 
 apt update
Hit:1 https://mirrors.tuna.tsinghua.edu.cn/proxmox/debian bookworm InRelease
Hit:2 https://mirrors.ustc.edu.cn/debian bookworm InRelease                       
Hit:3 https://mirrors.tuna.tsinghua.edu.cn/proxmox/debian bullseye InRelease       
Get:4 https://mirrors.ustc.edu.cn/debian bookworm-updates InRelease [55.4 kB]
Get:5 https://mirrors.ustc.edu.cn/debian-security bookworm-security InRelease [48.0 kB]
Hit:6 http://download.proxmox.com/debian/ceph-quincy bookworm InRelease 
Fetched 103 kB in 2s (67.6 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
121 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split

apt list --upgradable
Code: 
 apt list --upgradable
Listing... Done
base-files/stable 12.4+deb12u11 amd64 [upgradable from: 12.4+deb12u9]
bash/stable 5.2.15-2+b8 amd64 [upgradable from: 5.2.15-2+b7]
busybox/stable 1:1.35.0-4+b4 amd64 [upgradable from: 1:1.35.0-4+b3]
ceph-common/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
ceph-fuse/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
corosync/stable 3.1.9-pve1 amd64 [upgradable from: 3.1.7-pve3]
distro-info-data/stable 0.58+deb12u4 all [upgradable from: 0.58+deb12u3]
fonts-glyphicons-halflings/stable 1.009~3.4.1+dfsg-3+deb12u1 all [upgradable from: 1.009~3.4.1+dfsg-3]
ghostscript/stable,stable-security 10.0.0~dfsg-11+deb12u7 amd64 [upgradable from: 10.0.0~dfsg-11+deb12u6]
initramfs-tools-core/stable 0.142+deb12u3 all [upgradable from: 0.142+deb12u1]
initramfs-tools/stable 0.142+deb12u3 all [upgradable from: 0.142+deb12u1]
libabsl20220623/stable 20220623.1-1+deb12u2 amd64 [upgradable from: 20220623.1-1]
libavif15/stable-security 0.11.1-1+deb12u1 amd64 [upgradable from: 0.11.1-1]
libc-bin/stable 2.36-9+deb12u10 amd64 [upgradable from: 2.36-9+deb12u9]
libc-dev-bin/stable 2.36-9+deb12u10 amd64 [upgradable from: 2.36-9+deb12u9]
libc-devtools/stable 2.36-9+deb12u10 amd64 [upgradable from: 2.36-9+deb12u9]
libc-l10n/stable 2.36-9+deb12u10 all [upgradable from: 2.36-9+deb12u9]
libc6-dev/stable 2.36-9+deb12u10 amd64 [upgradable from: 2.36-9+deb12u9]
libc6/stable 2.36-9+deb12u10 amd64 [upgradable from: 2.36-9+deb12u9]
libcephfs2/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
libcfg7/stable 3.1.9-pve1 amd64 [upgradable from: 3.1.7-pve3]
libcmap4/stable 3.1.9-pve1 amd64 [upgradable from: 3.1.7-pve3]
libcorosync-common4/stable 3.1.9-pve1 amd64 [upgradable from: 3.1.7-pve3]
libcpg4/stable 3.1.9-pve1 amd64 [upgradable from: 3.1.7-pve3]
libfreetype6/stable,stable-security 2.12.1+dfsg-5+deb12u4 amd64 [upgradable from: 2.12.1+dfsg-5+deb12u3]
libglib2.0-0/stable 2.74.6-2+deb12u6 amd64 [upgradable from: 2.74.6-2+deb12u5]
libgs-common/stable,stable-security 10.0.0~dfsg-11+deb12u7 all [upgradable from: 10.0.0~dfsg-11+deb12u6]
libgs10-common/stable,stable-security 10.0.0~dfsg-11+deb12u7 all [upgradable from: 10.0.0~dfsg-11+deb12u6]
libgs10/stable,stable-security 10.0.0~dfsg-11+deb12u7 amd64 [upgradable from: 10.0.0~dfsg-11+deb12u6]
libjs-bootstrap/stable 3.4.1+dfsg-3+deb12u1 all [upgradable from: 3.4.1+dfsg-3]
liblzma-dev/stable,stable-security 5.4.1-1 amd64 [upgradable from: 5.4.1-0.2]
liblzma5/stable,stable-security 5.4.1-1 amd64 [upgradable from: 5.4.1-0.2]
libnss-systemd/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
libpam-systemd/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
libperl5.36/stable,stable-security 5.36.0-7+deb12u2 amd64 [upgradable from: 5.36.0-7+deb12u1]
libproxmox-acme-perl/stable 1.6.0 all [upgradable from: 1.5.1]
libproxmox-acme-plugins/stable 1.6.0 all [upgradable from: 1.5.1]
libproxmox-rs-perl/stable 0.3.5 amd64 [upgradable from: 0.3.4]
libpve-access-control/stable 8.2.2 all [upgradable from: 8.2.0]
libpve-cluster-api-perl/stable 8.1.0 all [upgradable from: 8.0.10]
libpve-cluster-perl/stable 8.1.0 all [upgradable from: 8.0.10]
libpve-common-perl/stable 8.3.1 all [upgradable from: 8.2.9]
libpve-guest-common-perl/stable 5.2.2 all [upgradable from: 5.1.6]
libpve-http-server-perl/stable 5.2.2 all [upgradable from: 5.2.0]
libpve-network-api-perl/stable 0.11.2 all [upgradable from: 0.10.0]
libpve-network-perl/stable 0.11.2 all [upgradable from: 0.10.0]
libpve-notify-perl/stable 8.1.0 all [upgradable from: 8.0.10]
libpve-rs-perl/stable 0.9.4 amd64 [upgradable from: 0.9.1]
libpython3.11-dev/stable 3.11.2-6+deb12u6 amd64 [upgradable from: 3.11.2-6+deb12u5]
libpython3.11-minimal/stable 3.11.2-6+deb12u6 amd64 [upgradable from: 3.11.2-6+deb12u5]
libpython3.11-stdlib/stable 3.11.2-6+deb12u6 amd64 [upgradable from: 3.11.2-6+deb12u5]
libpython3.11/stable 3.11.2-6+deb12u6 amd64 [upgradable from: 3.11.2-6+deb12u5]
libqt5core5a/stable 5.15.8+dfsg-11+deb12u3 amd64 [upgradable from: 5.15.8+dfsg-11+deb12u2]
libqt5dbus5/stable 5.15.8+dfsg-11+deb12u3 amd64 [upgradable from: 5.15.8+dfsg-11+deb12u2]
libqt5network5/stable 5.15.8+dfsg-11+deb12u3 amd64 [upgradable from: 5.15.8+dfsg-11+deb12u2]
libquorum5/stable 3.1.9-pve1 amd64 [upgradable from: 3.1.7-pve3]
librabbitmq4/stable 0.11.0-1+deb12u1 amd64 [upgradable from: 0.11.0-1+b1]
librados2/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
libradosstriper1/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
librbd1/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
librgw2/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
libsubid4/stable 1:4.13+dfsg1-1+deb12u1 amd64 [upgradable from: 1:4.13+dfsg1-1+b1]
libsystemd-shared/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
libsystemd0/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
libudev1/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
libvotequorum8/stable 3.1.9-pve1 amd64 [upgradable from: 3.1.7-pve3]
libxslt1.1/stable,stable-security 1.1.35-1+deb12u1 amd64 [upgradable from: 1.1.35-1]
linux-headers-amd64/stable-security 6.1.140-1 amd64 [upgradable from: 6.1.128-1]
locales/stable 2.36-9+deb12u10 all [upgradable from: 2.36-9+deb12u9]
login/stable 1:4.13+dfsg1-1+deb12u1 amd64 [upgradable from: 1:4.13+dfsg1-1+b1]
net-tools/stable-security 2.10-0.1+deb12u2 amd64 [upgradable from: 2.10-0.1]
novnc-pve/stable 1.6.0-2 all [upgradable from: 1.5.0-1]
passwd/stable 1:4.13+dfsg1-1+deb12u1 amd64 [upgradable from: 1:4.13+dfsg1-1+b1]
perl-base/stable,stable-security 5.36.0-7+deb12u2 amd64 [upgradable from: 5.36.0-7+deb12u1]
perl-modules-5.36/stable,stable-security 5.36.0-7+deb12u2 all [upgradable from: 5.36.0-7+deb12u1]
perl/stable,stable-security 5.36.0-7+deb12u2 amd64 [upgradable from: 5.36.0-7+deb12u1]
proxmox-archive-keyring/stable 3.2 all [upgradable from: 3.1]
proxmox-backup-client/stable 3.4.1-1 amd64 [upgradable from: 3.3.2-1]
proxmox-backup-file-restore/stable 3.4.1-1 amd64 [upgradable from: 3.3.2-2]
proxmox-firewall/stable 0.7.1 amd64 [upgradable from: 0.6.0]
proxmox-headers-6.8/stable 6.8.12-11 all [upgradable from: 6.8.12-8]
proxmox-kernel-6.8/stable 6.8.12-11 all [upgradable from: 6.8.12-8]
proxmox-kernel-helper/stable 8.1.1 all [upgradable from: 8.1.0]
proxmox-mail-forward/stable 0.3.2 amd64 [upgradable from: 0.3.1]
proxmox-ve/stable 8.4.0 all [upgradable from: 8.3.0]
proxmox-widget-toolkit/stable 4.3.11 all [upgradable from: 4.3.4]
pve-cluster/stable 8.1.0 amd64 [upgradable from: 8.0.10]
pve-docs/stable 8.4.0 all [upgradable from: 8.3.1]
pve-edk2-firmware-legacy/stable 4.2025.02-3 all [upgradable from: 4.2023.08-4]
pve-edk2-firmware-ovmf/stable 4.2025.02-3 all [upgradable from: 4.2023.08-4]
pve-edk2-firmware/stable 4.2025.02-3 all [upgradable from: 4.2023.08-4]
pve-esxi-import-tools/stable 0.7.4 amd64 [upgradable from: 0.7.2]
pve-firewall/stable 5.1.1 amd64 [upgradable from: 5.1.0]
pve-firmware/stable 3.15-4 all [upgradable from: 3.14-3]
pve-ha-manager/stable 4.0.7 amd64 [upgradable from: 4.0.6]
pve-headers-5.15/stable 7.4-15 all [upgradable from: 7.4-13]
pve-i18n/stable 3.4.4 all [upgradable from: 3.3.3]
pve-kernel-5.15/stable 7.4-15 all [upgradable from: 7.4-13]
pve-manager/stable 8.4.1 all [upgradable from: 8.3.3]
pve-qemu-kvm/stable 9.2.0-5 amd64 [upgradable from: 9.0.2-5]
pve-xtermjs/stable 5.5.0-2 all [upgradable from: 5.3.0-3]
python3-ceph-argparse/stable 17.2.8-pve2 all [upgradable from: 17.2.7-pve3]
python3-ceph-common/stable 17.2.8-pve2 all [upgradable from: 17.2.7-pve3]
python3-cephfs/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
python3-jinja2/stable 3.1.2-1+deb12u2 all [upgradable from: 3.1.2-1+deb12u1]
python3-rados/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
python3-rbd/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
python3-rgw/stable 17.2.8-pve2 amd64 [upgradable from: 17.2.7-pve3]
python3.11-dev/stable 3.11.2-6+deb12u6 amd64 [upgradable from: 3.11.2-6+deb12u5]
python3.11-minimal/stable 3.11.2-6+deb12u6 amd64 [upgradable from: 3.11.2-6+deb12u5]
python3.11/stable 3.11.2-6+deb12u6 amd64 [upgradable from: 3.11.2-6+deb12u5]
qemu-server/stable 8.3.12 amd64 [upgradable from: 8.3.7]
rsyslog/stable 8.2302.0-1+deb12u1 amd64 [upgradable from: 8.2302.0-1]
systemd-sysv/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
systemd/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
tzdata/stable,stable-updates 2025b-0+deb12u1 all [upgradable from: 2024b-0+deb12u1]
udev/stable-security 252.38-1~deb12u1 amd64 [upgradable from: 252.36-1~deb12u1]
uidmap/stable 1:4.13+dfsg1-1+deb12u1 amd64 [upgradable from: 1:4.13+dfsg1-1+b1]
wget/stable 1.21.3-1+deb12u1 amd64 [upgradable from: 1.21.3-1+b2]
xsltproc/stable,stable-security 1.1.35-1+deb12u1 amd64 [upgradable from: 1.1.35-1]
xz-utils/stable,stable-security 5.4.1-1 amd64 [upgradable from: 5.4.1-0.2]

I get your advice , I have a incomplete/failed upgrade ,should I complete this update ?
 
You must log in or register to reply here.
Top Bottom