[SOLVED] Error on new install

[proximity]

Just reinstalled on fresh debian 10 install. I get the following error:

Created symlink /etc/systemd/system/multi-user.target.wants/pve-guests.service → /lib/systemd/system/pve-guests.service.
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess 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
Processing triggers for fontconfig (2.13.1-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-5.0.15-1-pve
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for systemd (241-5) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for pve-ha-manager (3.0-2) ...
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)


Jul 19 17:39:17 proxmox pvestatd[23571]: ipcc_send_rec[1] failed: Connection refused
Jul 19 17:39:17 proxmox pvestatd[23571]: ipcc_send_rec[1] failed: Connection refused
Jul 19 17:39:17 proxmox pvestatd[23571]: ipcc_send_rec[2] failed: Connection refused
Jul 19 17:39:17 proxmox pvestatd[23571]: ipcc_send_rec[2] failed: Connection refused
Jul 19 17:39:17 proxmox pvestatd[23571]: ipcc_send_rec[3] failed: Connection refused
Jul 19 17:39:17 proxmox pvestatd[23571]: ipcc_send_rec[3] failed: Connection refused
Jul 19 17:39:17 proxmox pvestatd[23571]: Unable to load access control list: Connection refused
Jul 19 17:39:17 proxmox systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a
Jul 19 17:39:17 proxmox systemd[1]: pvestatd.service: Failed with result 'exit-code'.
Jul 19 17:39:17 proxmox systemd[1]: Failed to start PVE Status Daemon.



Jul 19 17:42:37 proxmox pveproxy[23551]: worker 6120 finished
Jul 19 17:42:37 proxmox pveproxy[23551]: starting 1 worker(s)
Jul 19 17:42:37 proxmox pveproxy[23551]: worker 6124 started
Jul 19 17:42:37 proxmox pveproxy[6121]: worker exit
Jul 19 17:42:37 proxmox pveproxy[6123]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1688.
Jul 19 17:42:37 proxmox pveproxy[6124]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1688.
Jul 19 17:42:37 proxmox pveproxy[23551]: worker 6121 finished
Jul 19 17:42:37 proxmox pveproxy[23551]: starting 1 worker(s)
Jul 19 17:42:37 proxmox pveproxy[23551]: worker 6125 started
Jul 19 17:42:38 proxmox pveproxy[6125]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1688.

 

[oguz]

hi,

did you edit your /etc/hosts file as described in the instructions[0] ?

check if

hostname --ip-address

gives you your ip back. once you fix that, you should be able to run `dpkg --configure -a`

[0]: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster

 

[proximity]

# hostname --ip-address
127.0.1.1 192.168.100.58

 

[proximity]

Strange. I did a new install:

# dpkg --configure -a
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

 

[tom]

Strange. I did a new install:

how do you become root?

see https://wiki.debian.org/NewInBuster

(use "su -")

 

[proximity]

That helps thank you.

Then I needed to comment out one entry in /etc/hosts to be able to run dpkg --configure -a

127.0.0.1 localhost
#127.0.1.1 proxmox.lan proxmox
192.168.100.58 proxmox

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

 

[oguz]

Then I needed to comment out one entry in /etc/hosts to be able to run dpkg --configure -a

glad your problem is solved. you can mark this thread [SOLVED] by editing your first post so other people know what to expect