Cannot start pvedaemon after updating and rebooting.

M

Maximc

New Member
Dec 20, 2024
2
0
1
Rebooted PC.
Think it might be because of last updates I did. I use the script at: https://github.com/BassT23/Proxmox
running the update command now gives this:

Code: 
[Info] Updating Host : 192.168.1.254 | (proxmox1)

--- APT UPDATE ---
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://security.debian.org/debian-security bookworm-security InRelease
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Reading package lists...

--- APT UPGRADE ---
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

--- APT CLEANING ---
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

--- Check Status for Welcome-Screen ---
---          Finished check         ---


Attempt to reload PVE/QMPClient.pm aborted.
Compilation failed in require at /usr/share/perl5/PVE/QemuServer/Monitor.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuServer/Monitor.pm line 8.
Compilation failed in require at /usr/share/perl5/PVE/QemuConfig.pm line 12.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 12.
Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 12.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 21.
Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 23.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 23.
Compilation failed in require at /usr/share/perl5/PVE/API2/LXC/Status.pm line 24.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/LXC/Status.pm line 29.
Compilation failed in require at /usr/share/perl5/PVE/CLI/pct.pm line 24.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pct.pm line 24.
Compilation failed in require at /usr/sbin/pct line 6.
BEGIN failed--compilation aborted at /usr/sbin/pct line 6.
Missing right curly or square bracket at /usr/share/perl5/IO/Multiplex.pm line 941, at end of line
syntax error at /usr/share/perl5/IO/Multiplex.pm line 941, at EOF
Compilation failed in require at /usr/share/perl5/PVE/QMPClient.pm line 6, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QMPClient.pm line 6, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/QemuServer.pm line 52, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuServer.pm line 52, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/API2/Qemu/Agent.pm line 8, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Qemu/Agent.pm line 8, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/CLI/qm.pm line 30, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/qm.pm line 30, <DATA> line 960.
Compilation failed in require at /usr/sbin/qm line 6, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/sbin/qm line 6, <DATA> line 960.
Finished, All Updates Done.

All fine, have a nice day

Then I run the start, and check the command "journalctl -xeu pvedaemon.service"


Code: 
root@proxmox1:~# systemctl start pvedaemon.service
Job for pvedaemon.service failed because the control process exited with error code.
See "systemctl status pvedaemon.service" and "journalctl -xeu pvedaemon.service" for details.
root@proxmox1:~# journalctl -xeu pvedaemon.service
Dec 20 01:21:48 proxmox1 pvedaemon[29086]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 15.
Dec 20 01:21:48 proxmox1 pvedaemon[29086]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 15.
Dec 20 01:21:48 proxmox1 pvedaemon[29086]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Dec 20 01:21:48 proxmox1 pvedaemon[29086]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Dec 20 01:21:48 proxmox1 pvedaemon[29086]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Dec 20 01:21:48 proxmox1 pvedaemon[29086]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Dec 20 01:21:48 proxmox1 systemd[1]: pvedaemon.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 pvedaemon.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
Dec 20 01:21:48 proxmox1 systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Dec 20 01:21:48 proxmox1 systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 14063 and the job result is failed.
Dec 20 01:21:49 proxmox1 systemd[1]: pvedaemon.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 pvedaemon.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 20 01:21:49 proxmox1 systemd[1]: Stopped pvedaemon.service - PVE API Daemon.
░░ Subject: A stop job for unit pvedaemon.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pvedaemon.service has finished.
░░
░░ The job identifier is 14163 and the job result is done.
Dec 20 01:21:49 proxmox1 systemd[1]: pvedaemon.service: Start request repeated too quickly.
Dec 20 01:21:49 proxmox1 systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Dec 20 01:21:49 proxmox1 systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 14163 and the job result is failed.

What else you might need, my apt source list and pveversion info:

Code: 
root@proxmox1:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-5-pve)
pve-manager: 8.3.2 (running version: 8.3.2/3e76eec21c4a14a7)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-5
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.8-4-pve-signed: 6.8.8-4
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
ceph-fuse: 17.2.7-pve2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
root@proxmox1:~# head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/*
==> /etc/apt/sources.list <==
deb http://deb.debian.org/debian bookworm main contrib
deb http://deb.debian.org/debian bookworm-updates main contrib
deb http://security.debian.org/debian-security bookworm-security main contrib

==> /etc/apt/sources.list.d/ceph.list <==
# deb http://download.proxmox.com/debian/ceph-quincy bookworm enterprise
# deb http://download.proxmox.com/debian/ceph-quincy bookworm no-subscription
# deb http://download.proxmox.com/debian/ceph-reef bookworm enterprise
# deb http://download.proxmox.com/debian/ceph-reef bookworm no-subscription

==> /etc/apt/sources.list.d/pve-enterprise.list <==
# deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise

==> /etc/apt/sources.list.d/pve-install-repo.list <==
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

==> /etc/apt/sources.list.d/pvetest-for-beta.list <==
# deb http://download.proxmox.com/debian/pve bookworm pvetest

Any help/guidance would be appreciated. Yes I need to make backups in the future sorry..
 
Hi,

please also post the output of tail -vn+0 /etc/apt/sources.list; tail -vn+0 /etc/apt/sources.list.d/*.
You can try reinstalling the broken packages via apt update && apt reinstall -y pve-manager pve-container qemu-server and see if that fixes it.

I'd suggest next time just either using apt update && apt dist-upgrade or the web interface to upgrade - instead of running random script of the internet, which often break things :)
 
  • Like
Reactions: aref.ghazouani and Kingneutron
the tail of the apt is already in the original post if you scroll down, sorry it is a bit hidden

Code: 
root@proxmox1:~# apt update && apt reinstall -y pve-manager pve-container qemu-server
Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Hit:2 http://deb.debian.org/debian bookworm InRelease
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Get:5 http://security.debian.org/debian-security bookworm-security/main amd64 Packages [236 kB]
Fetched 339 kB in 6s (57.7 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/979 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 80074 files and directories currently installed.)
Preparing to unpack .../pve-container_5.2.3_all.deb ...
Unpacking pve-container (5.2.3) over (5.2.3) ...
Preparing to unpack .../qemu-server_8.3.3_amd64.deb ...
Unpacking qemu-server (8.3.3) over (8.3.3) ...
Preparing to unpack .../pve-manager_8.3.2_all.deb ...
Unpacking pve-manager (8.3.2) over (8.3.2) ...
Setting up pve-container (5.2.3) ...
Setting up qemu-server (8.3.3) ...
Setting up pve-manager (8.3.2) ...
Job for pvedaemon.service failed because the control process exited with error code.
See "systemctl status pvedaemon.service" and "journalctl -xeu pvedaemon.service" for details.
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xeu pvestatd.service" for details.
Job for pvescheduler.service failed because the control process exited with error code.
See "systemctl status pvescheduler.service" and "journalctl -xeu pvescheduler.service" for details.
Processing triggers for pve-ha-manager (4.0.6) ...
Processing triggers for man-db (2.11.2-2) ...

Here no succes.
 
You must log in or register to reply here.
Top Bottom