[SOLVED] Proxmox VE: Installation 8.0: Errors were encountered while processing: pve-manager, proxmox-ve

H

hellfire

Renowned Member
Proxmox Subscriber
Aug 17, 2016
83
51
83
47
Hi,

I'm installing Proxmox VE on top of Debian Bookworm according to the official wiki page:

https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm

At the end of the step ...

Code: 
apt install proxmox-ve postfix open-iscsi chrony

I get ...

Code: 
# repeated command execution
apt install proxmox-ve postfix open-iscsi chrony  -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
proxmox-ve is already the newest version (8.0.2).
postfix is already the newest version (3.7.6-0+deb12u2).
open-iscsi is already the newest version (2.1.8-1).
chrony is already the newest version (4.3-2+deb12u1).
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.
Setting up pve-manager (8.0.4) ...
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
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 (>= 8.0.4); 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)

Looking at line 145 of /usr/bin/deb-systemd-invoke shows me that pvestatd can not be started ...

Code: 
# journalctl -u pvestatd
Okt 12 16:36:47 kvm15-vitracom systemd[1]: Starting pvestatd.service - PVE Status Daemon...
Okt 12 16:36:47 kvm15-vitracom pvestatd[2277]: ipcc_send_rec[1] failed: Connection refused
Okt 12 16:36:47 kvm15-vitracom pvestatd[2277]: ipcc_send_rec[2] failed: Connection refused
Okt 12 16:36:47 kvm15-vitracom pvestatd[2277]: ipcc_send_rec[3] failed: Connection refused
Okt 12 16:36:47 kvm15-vitracom pvestatd[2277]: Unable to load access control list: Connection refused
Okt 12 16:36:47 kvm15-vitracom pvestatd[2277]: ipcc_send_rec[1] failed: Connection refused
Okt 12 16:36:47 kvm15-vitracom pvestatd[2277]: ipcc_send_rec[2] failed: Connection refused
Okt 12 16:36:47 kvm15-vitracom pvestatd[2277]: ipcc_send_rec[3] failed: Connection refused
Okt 12 16:36:47 kvm15-vitracom systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a
Okt 12 16:36:47 kvm15-vitracom systemd[1]: pvestatd.service: Failed with result 'exit-code'.
Okt 12 16:36:47 kvm15-vitracom systemd[1]: Failed to start pvestatd.service - PVE Status Daemon.

Trying to start pvestatd manually gives the same ...

Code: 
/usr/bin/pvestatd 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

... trying to dig deeper ...

Ok. Found it:

https://forum.proxmox.com/threads/unable-to-load-access-control-list-connection-refused.72245/

For short: I didn't replace the ip address in /etc/hosts with the real ip address.

Problem:

Code: 
hostname --ip-address
127.0.1.1

This must not give 127.0.1.1 as result but the real/public Proxmox Server IP-Address.

Solution:

Code: 
cat /etc/hosts | sed -r -e 's/127.0.1.1/$REAL_PROXMOX_IP_ADDRESS/' >/etc/hosts.tmp && \
   cat /etc/hosts.tmp >/etc/hosts && rm -f /etc/hosts.tmp
 
Last edited:
Thank you for the information provided!

Can you please post the output of apt update command?
 
You must log in or register to reply here.
Top Bottom