Code:
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--unpack):
subprocess installed post-installation script returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@vt1:~# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: active (running) (Result: exit-code) since Mon 2017-01-23 16:01:37 CST; 1 years 6 months ago
Process: 12101 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=2)
Main PID: 1305 (pvedaemon)
CGroup: /system.slice/pvedaemon.service
├─1305 pvedaemon
├─5147 pvedaemon worker
├─5148 pvedaemon worker
└─5149 pvedaemon worker
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/share/perl5/PVE/Storage.pm line 20.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage.pm line 20.
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Aug 13 19:27:48 vt1 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Aug 13 19:27:48 vt1 systemd[1]: Reload failed for PVE API Daemon.
root@vt1:~# journalctl -xn
-- Logs begin at Mon 2018-08-13 14:23:27 CDT, end at Mon 2018-08-13 19:28:19 CDT. --
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Aug 13 19:27:48 vt1 pvedaemon[12101]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Aug 13 19:27:48 vt1 pvedaemon[12101]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Aug 13 19:27:48 vt1 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Aug 13 19:27:48 vt1 systemd[1]: Reload failed for PVE API Daemon.
-- Subject: Unit pvedaemon.service has finished reloading its configuration
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pvedaemon.service has finished reloading its configuration
--
-- The result is failed.
Aug 13 19:28:19 vt1 sshd[12315]: Connection closed by 59.78.98.101 [preauth]If I restart the server will it fail to come up? Is there something I can do to fix this service?
