I blew it up - E: Sub-process /usr/bin/dpkg returned an error code (1)

NeutralEvil

New Member
Nov 10, 2017
7
0
1
45
This is my first post because hours of Googling didn't help. I tried to upgrade and everything still worked until a recent power outage. Now nothing is starting.

Errors were encountered while processing:
pve-cluster
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

When I try to start a VM
root@proxmox:~# qm 102 start
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
 
pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.13.4-1-pve)
pve-manager: not correctly installed (running version: 5.1-36/131401db)
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.2.6-1-pve: 4.2.6-36
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: not correctly installed
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: not correctly installed
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
 
Is apt & dpkg working? If so, then 'apt update && apt full-upgrade', for any new packages. Along the way apt will tell you what packages may be missing or if there are any installation error known to apt. Then try to re-install the not correctly installed, if any left.
 
This is what happens. I've tried to reinstall the packages and they fail.

root@proxmox:~# apt-get upgrade && apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up pve-cluster (5.0-15) ...
insserv: warning: script 'K01mystartup.sh' missing LSB tags and overrides
insserv: warning: script 'mystartup.sh' missing LSB tags and overrides
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-11-10 10:53:26 CST; 7ms ago
Process: 9997 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)

Nov 10 10:53:18 proxmox systemd[1]: Starting The Proxmox VE cluster filesystem...
Nov 10 10:53:26 proxmox pmxcfs[9997]: [main] crit: Unable to get local IP address
Nov 10 10:53:26 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Nov 10 10:53:26 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Nov 10 10:53:26 proxmox systemd[1]: pve-cluster.service: Unit entered failed state.
Nov 10 10:53:26 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent processing triggers for pve-ha-manager:
pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving triggers unprocessed
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-cluster
pve-manager
pve-ha-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@proxmox:~#
 
It's possible. I've seen that advice before and I don't think there's any issues with the config from what I see. Suggestions please? (for the testing of this fix I modified the resolv.conf to only use public DNS

/etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.2.9 proxmox.asdfqwer.info proxmox pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

/etc/resolv.conf
search asdfqwer.info
nameserver 192.168.2.1
nameserver 192.168.2.99
nameserver 8.8.8.8


/etc/network/interfaces
auto lo
iface lo inet loopback

iface eth0 inet manual

auto eth1
iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.2.9
netmask 255.255.255.0
gateway 192.168.2.1
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
bridge_ports eth1
bridge_stp off
bridge_fd 0
 
192.168.2.9 proxmox.asdfqwer.info proxmox pvelocalhost
Are you sure the naming is correct (eg. typos)? Did you change the host name after installation?
 
I have not changed anything in there. I was originally trying to pass through a USB hdd and changed the repos from jessie to stretch and things went boom. Now my /etc/pve folder is empty
 
Does your network card work?
Code:
ip -c -a addr
 
It works. I'm connected to it via ssh. But it's configured with VMBR0 which I don't have any experience with.

root@proxmox:~# ip -c -a addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul t qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 00:1a:64:ca:ff:04 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr1 stat e DOWN group default qlen 1000
link/ether 00:1a:64:ca:ff:06 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP grou p default qlen 1000
link/ether 00:1a:64:ca:ff:04 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.9/24 brd 192.168.2.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::21a:64ff:feca:ff04/64 scope link
valid_lft forever preferred_lft forever
5: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:1a:64:ca:ff:06 brd ff:ff:ff:ff:ff:ff
 
What does syslog/kernel.log show?

You can check what files do not verify with the md5sum in the deb metadata.
Code:
dpkg --verify
The only currently supported output format is rpm, which consists of a line for every path that failed any check. The lines start with 9 characters to report each specific check result, a ‘?’ implies the check could not be done (lack of support, file permissions, etc), ‘.’ implies the check passed, and an alphanumeric character implies a specific check failed; the md5sum verification failure (the file contents have changed) is denoted with a ‘5’ on the third character. The line is followed by a space and an attribute character (currently ‘c’ for conffiles), another space and the pathname.

Code:
dpkg --audit
Performs database sanity and consistency checks for package-name or all packages if omitted (per package checks since dpkg 1.17.10). For example, searches for packages that have been installed only partially on your system or that have missing, wrong or obsolete control data or files. dpkg will suggest what to do with them to get them fixed.

Use this to check which package the files from the failed check belong too.
Code:
dpkg -S <path/file>
-S, --search filename-search-pattern...
Search for a filename from installed packages.
Try to reinstall all the packages that are not correctly installed, this might resolve the situation with the package pve-cluster failing to install.
 
So given the complete failure here, I'm thinking maybe wiping it and doing a fresh install?
I've got my qcow2 files copied offsite.
Tried to remove and reinstall the packages and it's got more errors now.





root@proxmox:~# tail -25 /var/log/syslog
Nov 15 07:33:06 proxmox systemd[1]: Created slice User Slice of root.
Nov 15 07:33:06 proxmox systemd[1]: Starting User Manager for UID 0...
Nov 15 07:33:06 proxmox systemd[1]: Started Session 144 of user root.
Nov 15 07:33:06 proxmox systemd[786]: Listening on GnuPG network certificate management daemon.
Nov 15 07:33:06 proxmox systemd[786]: Reached target Paths.
Nov 15 07:33:06 proxmox systemd[786]: Listening on GnuPG cryptographic agent (access for web browsers).
Nov 15 07:33:06 proxmox systemd[786]: Listening on GnuPG cryptographic agent and passphrase cache.
Nov 15 07:33:06 proxmox systemd[786]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Nov 15 07:33:06 proxmox systemd[786]: Reached target Timers.
Nov 15 07:33:06 proxmox systemd[786]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Nov 15 07:33:06 proxmox systemd[786]: Reached target Sockets.
Nov 15 07:33:06 proxmox systemd[786]: Reached target Basic System.
Nov 15 07:33:06 proxmox systemd[786]: Reached target Default.
Nov 15 07:33:06 proxmox systemd[786]: Startup finished in 53ms.
Nov 15 07:33:06 proxmox systemd[1]: Started User Manager for UID 0.
Nov 15 07:34:00 proxmox systemd[1]: Starting Proxmox VE replication runner...
Nov 15 07:34:01 proxmox pvesr[857]: ipcc_send_rec[1] failed: Connection refused
Nov 15 07:34:01 proxmox pvesr[857]: ipcc_send_rec[2] failed: Connection refused
Nov 15 07:34:01 proxmox pvesr[857]: ipcc_send_rec[3] failed: Connection refused
Nov 15 07:34:01 proxmox cron[1181]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Nov 15 07:34:01 proxmox pvesr[857]: Unable to load access control list: Connection refused
Nov 15 07:34:01 proxmox systemd[1]: pvesr.service: Main process exited, code=exited, status=111/n/a
Nov 15 07:34:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Nov 15 07:34:01 proxmox systemd[1]: pvesr.service: Unit entered failed state.
Nov 15 07:34:01 proxmox systemd[1]: pvesr.service: Failed with result 'exit-code'.

root@proxmox:~# dpkg --verify
??5?????? c /etc/apt/sources.list.d/pve-enterprise.list
??5?????? c /etc/init.d/pve-manager
??5?????? c /etc/perl/sitecustomize.pl
??5?????? c /etc/issue

root@proxmox:~# dpkg --audit
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
pve-cluster Cluster Infrastructure for Proxmox Virtual Environment
pve-manager Proxmox Virtual Environment Management Tools

The following packages have been triggered, but the trigger processing
has not yet been done. Trigger processing can be requested using
dselect or dpkg --configure --pending (or dpkg --triggers-only):
pve-ha-manager Proxmox VE HA Manager

root@proxmox:~# dpkg --configure pve-cluster
Setting up pve-cluster (5.0-15) ...
insserv: warning: script 'K01mystartup.sh' missing LSB tags and overrides
insserv: warning: script 'mystartup.sh' missing LSB tags and overrides
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2017-11-15 07:37:16 CST; 7ms ago
Process: 954 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)

Nov 15 07:37:16 proxmox systemd[1]: Starting The Proxmox VE cluster filesystem...
Nov 15 07:37:16 proxmox pmxcfs[954]: [main] crit: Unable to get local IP address
Nov 15 07:37:16 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Nov 15 07:37:16 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Nov 15 07:37:16 proxmox systemd[1]: pve-cluster.service: Unit entered failed state.
Nov 15 07:37:16 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pve-cluster
root@proxmox:~# dpkg --configure pve-manager
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
root@proxmox:~# dpkg -S /etc/apt/sources.list.d/pve-enterprise.list
pve-manager: /etc/apt/sources.list.d/pve-enterprise.list
root@proxmox:~# dpkg -S /etc/perl/sitecustomize.pl
perl: /etc/perl/sitecustomize.pl
root@proxmox:~# dpkg -S /etc/issue
base-files: /etc/issue