ipcc_send_rec error on debian buster fresh install

[aoemaster]

I am trying to install proxmox on top of a debian buster fresh install.

Here is pvereport (too long for the forum) : https://pastebin.com/raw/dtCbfP1z
Here are some commands results :

root@cube:~# apt install proxmox-ve postfix open-iscsi
[...]
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
Created symlink /etc/systemd/system/multi-user.target.wants/pvedaemon.service → /lib/systemd/system/pvedaemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pveproxy.service → /lib/systemd/system/pveproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/spiceproxy.service → /lib/systemd/system/spiceproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pvestatd.service → /lib/systemd/system/pvestatd.service.
Created symlink /etc/systemd/system/getty.target.wants/pvebanner.service → /lib/systemd/system/pvebanner.service.
Created symlink /etc/systemd/system/timers.target.wants/pvesr.timer → /lib/systemd/system/pvesr.timer.
Created symlink /etc/systemd/system/timers.target.wants/pve-daily-update.timer → /lib/systemd/system/pve-daily-update.timer.
Created symlink /etc/systemd/system/sysinit.target.wants/pvenetcommit.service → /lib/systemd/system/pvenetcommit.service.
Created symlink /etc/systemd/system/pve-manager.service → /lib/systemd/system/pve-guests.service.
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 mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.3.13-1-pve
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
No /etc/kernel/pve-efiboot-uuids found, skipping ESP sync.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for systemd (241-7~deb10u2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.1+dfsg-1) ...
Processing triggers for pve-ha-manager (3.0-8) ...
Errors were encountered while processing:
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@cube:~# hostname --ip-address
127.0.1.1 192.168.0.18

root@cube:~# journalctl -xe | tail
Jan 18 13:12:18 cube pveproxy[30439]: worker exit
Jan 18 13:12:18 cube pveproxy[15623]: worker 30439 finished
Jan 18 13:12:18 cube pveproxy[15623]: starting 1 worker(s)
Jan 18 13:12:18 cube pveproxy[15623]: worker 30444 started
Jan 18 13:12:18 cube pveproxy[30444]: /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 1699.
Jan 18 13:12:18 cube pveproxy[30440]: worker exit
Jan 18 13:12:18 cube pveproxy[15623]: worker 30440 finished
Jan 18 13:12:18 cube pveproxy[15623]: starting 1 worker(s)
Jan 18 13:12:18 cube pveproxy[15623]: worker 30445 started
Jan 18 13:12:18 cube pveproxy[30445]: /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 1699.

root@cube:~# ls -al /etc/pve/
total 8
drwxr-xr-x 2 root root 4096 Jan 18 12:46 .
drwxr-xr-x 95 root root 4096 Jan 18 13:11 ..

root@cube:~# pvecm nodes
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
root@cube:~# pvecm status
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

root@cube:~# 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 Sat 2020-01-18 13:11:59 CET; 16min ago
Process: 30428 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Jan 18 13:11:59 cube systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jan 18 13:11:59 cube systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jan 18 13:11:59 cube systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jan 18 13:11:59 cube systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jan 18 13:11:59 cube systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jan 18 13:11:59 cube systemd[1]: Failed to start The Proxmox VE cluster filesystem.

 

[Dominic]

Are you sure that you have the correct repositories? What is the output of the following commands?

 apt update

cat /etc/hosts

 

[aoemaster]

Removing 127.0.1.1 line from /etc/hosts solved everything.
Maybe this should be documented here : https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster

 

[FibreFoX]

Removing 127.0.1.1 line from /etc/hosts solved everything.
Maybe this should be documented here : https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster

Thank you so much, I'm having a server provided by Strato, and that 127.0.1.1 line (which I ignored at first) was there by default.

 

[Dominic]

Great that you could solve the problem! I've just edited the relevant wiki page to make this topic clearer. Feedback would be appreciated

 

[FibreFoX]

@Dominic Thanks for the page edit, this is really helpful for others too. But maybe it is better to have this at the "Troubleshooting"-area, where you could include that `ipcc_send_rec[1] failed: Connection refused` fragment, as some users might see it there better.
How do you think about it? Even if it stays at the current state, that will help a ton of users with crazy default configuration

 

[Dominic]

@FibreFoX Thank you! I added a small note about the error to the troubleshooting area.