[SOLVED] BIG PROBLEM: Nothing is working after apt-get upgrade....

M

mcflym

Renowned Member
Jul 10, 2013
195
10
83
Well... I have a big big problem... what I just did was an apt-get update and apt-get upgrade...

There is/was an error at the end:

Code: 
root@proxmox:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and a                                                                                                                      re no longer required:
  libnvpair1 libzfs2
Use 'apt-get autoremove' to remove them.
Done
The following packages have been kept back:
  libpve-common-perl proxmox-ve pve-container pve-manager qemu-server
0 upgraded, 0 newly installed, 0 to remove and 5 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-1) ...
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)

No I have the following problem:

iKVM_capture.jpg

Web-GUI isn't working anymore
Wrong IP-Settings (192.168.2.200) but ping and putty (to the former proxmox IP Address 192.168.20.200) is working
VM don't start

Everything is crashed.... DAMN!

Code: 
root@proxmox:~# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
   Active: failed (Result: exit-code) since Sat 2017-03-04 12:26:10 CET; 4min 4s ago
  Process: 1884 ExecStart=/usr/bin/pvedaemon start (code=exited, status=2)

Mar 04 12:26:10 proxmox pvedaemon[1884]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Mar 04 12:26:10 proxmox pvedaemon[1884]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Mar 04 12:26:10 proxmox pvedaemon[1884]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Mar 04 12:26:10 proxmox pvedaemon[1884]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 04 12:26:10 proxmox pvedaemon[1884]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 04 12:26:10 proxmox pvedaemon[1884]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Mar 04 12:26:10 proxmox pvedaemon[1884]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Mar 04 12:26:10 proxmox systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Mar 04 12:26:10 proxmox systemd[1]: Failed to start PVE API Daemon.
Mar 04 12:26:10 proxmox systemd[1]: Unit pvedaemon.service entered failed state.

Code: 
root@proxmox:~# journalctl -xn
-- Logs begin at Sat 2017-03-04 12:21:51 CET, end at Sat 2017-03-04 12:29:51 CET. --
Mar 04 12:26:10 proxmox pvedaemon[1884]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Mar 04 12:26:10 proxmox pvedaemon[1884]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Mar 04 12:26:10 proxmox systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Mar 04 12:26:10 proxmox systemd[1]: Failed to start PVE API Daemon.
-- Subject: Unit pvedaemon.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pvedaemon.service has failed.
--
-- The result is failed.
Mar 04 12:26:10 proxmox systemd[1]: Unit pvedaemon.service entered failed state.
Mar 04 12:27:01 proxmox cron[1728]: (*system*pveupdate) RELOAD (/etc/cron.d/pveupdate)
Mar 04 12:27:06 proxmox postfix/qmgr[1715]: CAF4D40841: from=<root@proxmox.fair-music.de>, size=1801, nrcpt=1 (queue active)
Mar 04 12:27:06 proxmox postfix/smtp[1897]: CAF4D40841: host mx-ha03.web.de[212.227.15.17] refused to talk to me: 554-web.de (mxweb001) Nemesis ESMTP Service not available 554-No SMTP service 554-IP
Mar 04 12:27:06 proxmox postfix/smtp[1897]: CAF4D40841: to=<jo2001@web.de>, relay=mx-ha02.web.de[212.227.17.8]:25, delay=1110, delays=1109/0.01/0.13/0, dsn=4.0.0, status=deferred (host mx-ha02.web.d
Mar 04 12:29:51 proxmox systemd-timesyncd[926]: interval/delta/delay/jitter/drift 512s/+0.004s/0.019s/0.002s/+3ppm

At Startup:
iKVM_capture (1).jpg

iKVM_capture (3).jpg
 
Last edited:
I have another Proxmox machine which get the same error after apt-get upgrade... But I didn't restart it yet and I won't until there is a solution for this :(

What did you do?????
 
Made a apt-get dist-upgrade and Web-GUI is working again...

BUT: The iscsi-errors and the wrong IP-Address is still shown?!

AND

One of my VM won't start up (Errors while deactivating autostartup and VNC):
Code: 
can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout (500)
TASK ERROR: command '/bin/nc6 -l -p 5900 -w 10 -e '/usr/sbin/qm vncproxy 102 2>/dev/null'' failed: exit code 1

FYI: There is a PCIE passthrough (SAS Controller) to this VM

After several restarts and deactivating autostart via console it's working now but with a lot of headaches. I think there is an issue within the upgrade?
 
Last edited:
mcflym said:
restarts and deactivating autostart via console it's working now but with a lot of headaches. I think there is an issue within the upgrade?
Click to expand...

Never do 'apt-get upgrade' - instead, always run 'apt-get dist-upgrade'.
 
You must log in or register to reply here.
Top Bottom