One thing i noticed is during the upgrade, it mentioned that pvemanager failed:
Setting up pve-manager (7.1-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
I just upgraded today from 7.1-10 to 7.1-11, and I noticed that pvedaemon is now freaking out since the upgrade. I have tried it on 2 of my 5 hosts, and both hosts have this issue, so i stopped the upgrade process.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 25.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 25.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Mar 28 10:30:59 pvedr02 systemd[1]: pvedaemon.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Mar 28 10:30:59 pvedr02 systemd[1]: Reload failed for PVE API Daemon.
I had to downgrade pve-manager to 7.1-10 to get things to work again.
apt-get install pve-manager=7.1-10
Setting up pve-manager (7.1-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
I just upgraded today from 7.1-10 to 7.1-11, and I noticed that pvedaemon is now freaking out since the upgrade. I have tried it on 2 of my 5 hosts, and both hosts have this issue, so i stopped the upgrade process.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 25.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 25.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Mar 28 10:30:59 pvedr02 pvedaemon[824243]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Mar 28 10:30:59 pvedr02 systemd[1]: pvedaemon.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Mar 28 10:30:59 pvedr02 systemd[1]: Reload failed for PVE API Daemon.
I had to downgrade pve-manager to 7.1-10 to get things to work again.
apt-get install pve-manager=7.1-10
Last edited:
