Alwin, Same errors in logs about compilation aborted.
# dpkg --configure -a Setting up pve-manager (4.1-33) ... 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 dpkg: dependency problems prevent configuration of proxmox-ve: proxmox-ve depends on pve-manager; however: Package pve-manager is not configured yet. dpkg: error processing package proxmox-ve (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: pve-manager proxmox-ve # apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following packages were automatically installed and are no longer required: libasn1-8-heimdal libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libkrb5-26-heimdal libldb1 libntdb1 libparted0debian1 libroken18-heimdal libsmbclient libtevent0 libtiff4 libupsclient1 libwind0-heimdal python-talloc samba-libs Use 'apt-get autoremove' to remove them. Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 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.1-33) ... 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 dpkg: dependency problems prevent configuration of proxmox-ve: proxmox-ve depends on pve-manager; however: Package pve-manager is not configured yet. dpkg: error processing package proxmox-ve (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: pve-manager proxmox-ve E: Sub-process /usr/bin/dpkg returned an error code (1) On Thu, Apr 21, 2016 at 5:33 PM, Maks <[email protected]> wrote: > Hello all, > > I'm in a bit of a pickle here. I was running a recently upgraded (about a > month ago) pve host and wanted to run update today. It failed on > configuring pve-manager. > I only pull packages from the proxmox repo and security updates from > debian. > # proxmox no subscription > deb http://download.proxmox.com/debian jessie pve-no-subscription > # security updates > deb http://security.debian.org/ jessie/updates main contrib > > > I have the following in journalctl > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: unknown file 'ha/fence.cfg' > at /usr/share/perl5/PVE/Cluster.pm line 760, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in > require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 17, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation > aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 17, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in > require at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation > aborted at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in > require at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation > aborted at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in > require at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation > aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in > require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation > aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in > require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line > 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation > aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line > 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: Compilation failed in > require at /usr/bin/pvedaemon line 11, <DATA> line 751. > Apr 21 17:19:03 activebackup1 pvedaemon[8362]: BEGIN failed--compilation > aborted at /usr/bin/pvedaemon line 11, <DATA> line 751. > Apr 21 17:19:03 activebackup1 systemd[1]: pvedaemon.service: control > process exited, code=exited status=255 > Apr 21 17:19:03 activebackup1 systemd[1]: Failed to start PVE API Daemon. > Apr 21 17:19:03 activebackup1 systemd[1]: Unit pvedaemon.service entered > failed state. > > > I'm sure I'm missing some kind of dependency. Any help is much > appreciated, all of my VMs are down! > > --Maks > _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
