fresh installation PVE 5.2, bunch of bugs: tipcc_send_rec [1] failed: Connection refused

[clgies]

hi,

after a fresh intstallation of Proxmox 5.2 (pve-manager / 5.2-10 / 6f892b40 (running kernel: 4.15.17-1-pve) I get a bunch of bugs:

Here is the first error:

Command: "qm list"

tipcc_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

/var/log/syslog

Oct 31 16:00:42 pve pvestatd[1627]: status update error: Connection refused
Oct 31 16:00:44 pve pveproxy[7615]: worker exit
Oct 31 16:00:44 pve pveproxy[1697]: worker 7615 finished
Oct 31 16:00:44 pve pveproxy[1697]: starting 1 worker(s)
Oct 31 16:00:44 pve pveproxy[1697]: worker 7616 started
Oct 31 16:00:44 pve pveproxy[7616]: /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 1642.
Oct 31 16:00:44 pve pveproxy[15688]: ipcc_send_rec[1] failed: Connection refused
Oct 31 16:00:44 pve pveproxy[15688]: ipcc_send_rec[2] failed: Connection refused
Oct 31 16:00:44 pve pveproxy[15688]: ipcc_send_rec[3] failed: Connection refused
Oct 31 16:00:49 pve pveproxy[7616]: worker exit
Oct 31 16:00:49 pve pveproxy[1697]: worker 7616 finished

seems, that pveproxies worker process doesn't work properly ?

every hint is welcome

thanks in advance.

claus

 

[dcsapak]

what does 'systemctl status pve-cluster' say?

 

[clgies]

The source of my problems was the renaming of the host (via hostnamectl set-hostname). Not a good idea

I have fixed all resulting errors (delete the old node, create a new node and rebuild the certificate).

However, I did not update the configuration in the database (sqlite3 /var/lib/pve-cluster/config.db) due to time constraints and did a clean installation.