[SOLVED] Update Failed

W

Wojciech Szpunar

New Member
Jun 3, 2016
20
0
1
43
Hey Guys,

I was doing routing apt-get update && apt-get upgrade on my test node here and upgrade failed.
Is there a faulty upgrade ?


Setting up pve-manager (4.2-23) ...
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
Processing triggers for libc-bin (2.19-18+deb8u6) ...
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@proxmox3:~# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: active (running) (Result: exit-code) since Wed 2016-09-21 13:33:03 BST; 2 days ago
Process: 22303 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=2)
Main PID: 21815 (pvedaemon)
CGroup: /system.slice/pvedaemon.service
├─21815 pvedaemon
├─22003 pvedaemon worker
├─22004 pvedaemon worker
└─22005 pvedaemon worker

Sep 23 14:18:56 proxmox3 pvedaemon[22303]: Compilation failed in require at /usr/share/perl5/PVE/API2/Nodes.pm line 41.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Nodes.pm line 41.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Sep 23 14:18:56 proxmox3 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Sep 23 14:18:56 proxmox3 systemd[1]: Reload failed for PVE API Daemon.
root@proxmox3:~# journalctl -xn
-- Logs begin at Wed 2016-09-21 10:40:13 BST, end at Fri 2016-09-23 14:19:01 BST. --
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Nodes.pm line 41.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Sep 23 14:18:56 proxmox3 pvedaemon[22303]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Sep 23 14:18:56 proxmox3 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Sep 23 14:18:56 proxmox3 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.
Sep 23 14:19:01 proxmox3 cron[569]: (*system*pveupdate) RELOAD (/etc/cron.d/pveupdate)
 
Now I have rebooted this node and seems like after reboot PVE do not start at all.
All services are down:


netstat -alptn
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1485/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 1675/master
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1320/rpcbind
tcp 0 0 0.0.0.0:51921 0.0.0.0:* LISTEN 1330/rpc.statd
tcp 0 0 192.168.106.234:22 192.168.106.127:42518 ESTABLISHED 1755/0
tcp6 0 0 :::22 :::* LISTEN 1485/sshd
tcp6 0 0 :::25 :::* LISTEN 1675/master
tcp6 0 0 :::45451 :::* LISTEN 1330/rpc.statd
tcp6 0 0 :::111 :::* LISTEN 1320/rpcbind
 
Seems like there is a problem with missing Perl Library:

root@proxmox3:~# /usr/bin/pvedaemon start
Can't locate PVE/Diskmanage.pm in @INC (you may need to install the PVE::Diskmanage module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl) at /usr/share/perl5/PVE/API2/Ceph.pm line 20.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Ceph.pm line 20.
Compilation failed in require at /usr/share/perl5/PVE/API2/Nodes.pm line 41.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Nodes.pm line 41.
Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Compilation failed in require at /usr/bin/pvedaemon line 11.
BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
 
Hi,
I got the same problem but after I use dselect to do my upgrade and all stages pass perfectly (I use community version not enterprise)
 
You must log in or register to reply here.
Top Bottom