I've ran an update on 2 nodes, and both have failed in exactly the same way.
pvemanager is now no longer running, and won't restart.
Really stuck here now, so any help would be greatly appreciated.
Code:
root@vm1:/etc/pve# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
proxmox-ve pve-container pve-manager qemu-server
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-manager (4.4-5) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@vm1:/etc/pve#
Code:
root@vm1:/etc/pve# systemctl status pvedaemon.service
â— pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: active (running) (Result: exit-code) since Fri 2017-02-03 17:57:35 GMT; 3h 25min ago
Process: 32511 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=2)
Main PID: 1751 (pvedaemon)
CGroup: /system.slice/pvedaemon.service
├─1751 pvedaemon
├─1752 pvedaemon worker
├─1753 pvedaemon worker
└─1754 pvedaemon worker
Feb 03 21:22:48 vm1 pvedaemon[32511]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA...ne 751.
Feb 03 21:22:48 vm1 pvedaemon[32511]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <...ne 751.
Feb 03 21:22:48 vm1 pvedaemon[32511]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 21:22:48 vm1 pvedaemon[32511]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 21:22:48 vm1 pvedaemon[32511]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <...ne 751.
Feb 03 21:22:48 vm1 pvedaemon[32511]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line ...ne 751.
Feb 03 21:22:48 vm1 pvedaemon[32511]: Compilation failed in require at /usr/bin/pvedaemon line 11, <DATA> line 751.
Feb 03 21:22:48 vm1 pvedaemon[32511]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11, <DATA> line 751.
Feb 03 21:22:48 vm1 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Feb 03 21:22:48 vm1 systemd[1]: Reload failed for PVE API Daemon.
Hint: Some lines were ellipsized, use -l to show in full.
root@vm1:/etc/pve#
pvemanager is now no longer running, and won't restart.
Really stuck here now, so any help would be greatly appreciated.