proxmox install @debian buster - instalation ends with error, ipcc_send_rec[3] failed: Connection refused

[ivans]

hello

instalation pve-manager at fresh installed debian buster system ends with error

....
Setting up pve-manager (6.2-11) ...
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
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)


# systemctl status pvestatd.service
â pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-09-04 14:38:07 CEST; 8s ago
Process: 18383 ExecStart=/usr/bin/pvestatd start (code=exited, status=111)

Sep 04 14:38:07 myhost pvestatd[18383]: ipcc_send_rec[1] failed: Connection refused
Sep 04 14:38:07 myhost pvestatd[18383]: ipcc_send_rec[1] failed: Connection refused
Sep 04 14:38:07 myhost pvestatd[18383]: ipcc_send_rec[2] failed: Connection refused
Sep 04 14:38:07 myhost pvestatd[18383]: ipcc_send_rec[2] failed: Connection refused
Sep 04 14:38:07 myhost pvestatd[18383]: ipcc_send_rec[3] failed: Connection refused
Sep 04 14:38:07 myhost pvestatd[18383]: ipcc_send_rec[3] failed: Connection refused
Sep 04 14:38:07 myhost pvestatd[18383]: Unable to load access control list: Connection refused
Sep 04 14:38:07 myhost systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a
Sep 04 14:38:07 myhost systemd[1]: pvestatd.service: Failed with result 'exit-code'.
Sep 04 14:38:07 myhost systemd[1]: Failed to start PVE Status Daemon.



# cat /etc/hosts
10.10.1.21 myhost.mydomain.com myhost
#and some commented lines

# hostname --ip-address
10.10.1.21

~# telnet myhost 22
Trying 10.10.1.21...
Connected to 10.10.1.21.
Escape character is '^]'.
SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2

# iptables -L -v -n
Chain INPUT (policy ACCEPT 1851K packets, 566M bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 1627K packets, 127M bytes)
pkts bytes target prot opt in out source destination


I've removed all other IP's and unneeded interfaces, IP is assigned at vmbr0
IPv6 I've disabled

I've no more ideas what to try, can you please give me a hint ?

 

[Stoiko Ivanov]

* what's the output of `uname -n`?
* is the pve-cluster.service running? does it help if you restart it? `systemctl status pve-cluster`

 

[ivans]

# uname -n
myhost


# systemctl status pve-cluster
â 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 2020-09-04 15:00:02 CEST; 53min ago
Process: 24795 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Sep 04 15:00:02 myhost systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Sep 04 15:00:02 myhost systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Sep 04 15:00:02 myhost systemd[1]: Stopped The Proxmox VE cluster filesystem.
Sep 04 15:00:02 myhost systemd[1]: pve-cluster.service: Start request repeated too quickly.
Sep 04 15:00:02 myhost systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Sep 04 15:00:02 myhost systemd[1]: Failed to start The Proxmox VE cluster filesystem.

 

[ivans]

journalctl -xe
-- Subject: A start job for unit corosync.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit corosync.service has finished successfully.
--
-- The job identifier is 193244.
Sep 04 15:54:49 myhost pveproxy[26801]: worker exit
Sep 04 15:54:49 myhost pveproxy[3944]: worker 26801 finished
Sep 04 15:54:49 myhost pveproxy[3944]: starting 1 worker(s)
Sep 04 15:54:49 myhost pveproxy[3944]: worker 26825 started
Sep 04 15:54:49 myhost pveproxy[26802]: worker exit
Sep 04 15:54:49 myhost pveproxy[26803]: worker exit
Sep 04 15:54:49 myhost pveproxy[26825]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/p
Sep 04 15:54:49 myhost pveproxy[3944]: worker 26803 finished
Sep 04 15:54:49 myhost pveproxy[3944]: worker 26802 finished
Sep 04 15:54:49 myhost pveproxy[3944]: starting 2 worker(s)
Sep 04 15:54:49 myhost pveproxy[3944]: worker 26826 started
Sep 04 15:54:49 myhost pveproxy[3944]: worker 26827 started
Sep 04 15:54:49 myhost pveproxy[26826]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/p
Sep 04 15:54:49 myhost pveproxy[26827]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/p
Sep 04 15:54:54 myhost pveproxy[26825]: worker exit
Sep 04 15:54:54 myhost pveproxy[3944]: worker 26825 finished
Sep 04 15:54:54 myhost pveproxy[3944]: starting 1 worker(s)
Sep 04 15:54:54 myhost pveproxy[3944]: worker 26830 started
Sep 04 15:54:54 myhost pveproxy[26826]: worker exit
....

 

[Tommy]

I have the same problem. Did you find a solution?

 

[Stoiko Ivanov]

did not get back to replying to the original poster...

If the pve-cluster service is not running I'd check the corosync service for messages (in a cluster) or take a closer look at the pmxcfs /pve-cluster logs:
journalctl -u corosync -u pve-cluster

 

[Tommy]

I first tried with the installer, but only got a white screen. The Debian Install worked, but it seems that the Proxmox Modules are not fully configured. apt-get install gives me:

Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.

journalctl -u corosync -u pve-cluster

gives no result, but journalctl -xe gives messages like

 /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/p

regards
Thomas

 

[Stoiko Ivanov]

I first tried with the installer, but only got a white screen. The Debian Install worked, but it seems that the Proxmox Modules are not fully configured. apt-get install gives me:

did installing the proxmox-ve metapackage work?
(what's the output of `apt update`, `apt install proxmox-ve`)?

 

[Tommy]

apt install proxmox-vegives:

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
proxmox-ve ist schon die neueste Version (6.3-1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 4 nicht aktualisiert.
2 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
pve-manager (6.3-3) wird eingerichtet ...
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: Fehler beim Bearbeiten des Paketes pve-manager (--configure):
 »installiertes pve-manager-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proxmox-ve:
 proxmox-ve hängt ab von pve-manager; aber:
  Paket pve-manager ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes proxmox-ve (--configure):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert
Fehler traten auf beim Bearbeiten von:
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

pve-manager is not to be configured, journalctl -xe gives pveproxy[1315]: /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 1775.

 

[Stoiko Ivanov]

Please try starting the cluster-filesystem (this is where the ssl-key/cert for pveproxy is) and check why it fails to start - post the logs since the time you tried starting it:

systemctl restart pve-cluster
journalctl --since '-10m'

EDIT: also - please check that you have an entry in /etc/hosts pointing from an IP configured on your system to the hostname of the node - as a test:

ping -c 2 $(uname -n)

needs to work successfully

 

[laca77]

Hello
.
I had the same problem, but i found a workaround:

My hostname is cn01. In the /etc/hosts i have this line:
127.0.1.1 cn01

So i changed the localhost IP to the real IP of the server:

192.168.1.1 cn01

After that the install process was able to finish the install.