[SOLVED] unable to start pvedeamon after update

G

Giacomo Vallini

Active Member
May 20, 2019
12
6
43
37
Hi, this morning i updated the server packages of both the nodes of my cluster.

Now on my second node, i can't reach virtual machines by gui, or start them by cli. I can reach the node's console.

The syslog error is:

Code: 
Sep  8 09:43:53 srv3 pvedaemon[6748]: no such standard option 'prune-backups'
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/share/perl5/PVE/VZDump/Plugin.pm line 11.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/VZDump/Plugin.pm line 11.
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/share/perl5/PVE/API2/Qemu.pm line 34.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Qemu.pm line 34.
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 16.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 19.
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 21.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 21.
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 14.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 14.
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep  8 09:43:53 srv3 pvedaemon[6748]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Sep  8 09:43:53 srv3 pvedaemon[6748]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Sep  8 09:43:53 srv3 systemd[1]: pvedaemon.service: Control process exited, code=exited, status=255/EXCEPTION
Sep  8 09:43:53 srv3 systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Sep  8 09:43:53 srv3 systemd[1]: Failed to start PVE API Daemon.
Sep  8 09:43:53 srv3 systemd[1]: pvedaemon.service: Service RestartSec=100ms expired, scheduling restart.
Sep  8 09:43:53 srv3 systemd[1]: pvedaemon.service: Scheduled restart job, restart counter is at 5.
Sep  8 09:43:53 srv3 systemd[1]: Stopped PVE API Daemon.
Sep  8 09:43:53 srv3 systemd[1]: pvedaemon.service: Start request repeated too quickly.
Sep  8 09:43:53 srv3 systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Sep  8 09:43:53 srv3 systemd[1]: Failed to start PVE API Daemon.

Can someone help me?
 
I just upgraded 3 servers to 6.3-3 and on two of the servers I'm getting "communication refused(595)" and from the cmd line on the two servers and most commands qm, pvesh , etc.. I get the

no such standard option 'prune-backups'
Compilation failed in require at /usr/share/perl5/PVE/VZDump/Plugin.pm line 11.

message, I tried the apt dist-upgrade and get

The following packages have been kept back:
libpve-storage-perl pve-container pve-manager
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

Any ideas
 
Had to create an account just to thank OP. I was fooling around and decided to update all the packages, I do that on my desktop machines frequently w/ apt-get update / upgrade. I found my ProxMox server was no longer accessible via browser, and checking the which I had been happily using for over a year. Running systemctl status 'pve*' showed numerous errors. I was afraid I hosed the whole thing, but found this post and tried apt dist-upgrade then rebooted, which solved got everything back up!

Thank you!
 
You must log in or register to reply here.
Top Bottom
Back