[SOLVED] Can't login into GUI - ipcc_send_rec Error

[kevinsah]

Hi everyone!

I have a strange error.
I am not able to start or stop VMs. This error came from nowhere.
These strange errors happend from nowhere. I have no clue where it does come from, please help me!

Output from some commands:
qm start 112
root@proxmox-pve:~# qm start 112 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


qm list
root@proxmox-pve:~# qm list 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


ls -l /etc/pve
root@proxmox-pve:~# ls -l /etc/pve
total 0

Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 5.0.15-1-pve

I can show more logs, if needed

 

[kevinsah]

Hi everyone!

I have a strange error.
I am not able to start or stop VMs. This error came from nowhere.
These strange errors happend from nowhere. I have no clue where it does come from, please help me!

Output from some commands:
qm start 112
root@proxmox-pve:~# qm start 112 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


qm list
root@proxmox-pve:~# qm list 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


ls -l /etc/pve
root@proxmox-pve:~# ls -l /etc/pve
total 0

Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 5.0.15-1-pve

I can show more logs, if needed

Update: This error seems to have happend because I changed hostname (Via hostnamectl...)

 

[Stoiko Ivanov]

Update: This error seems to have happend because I changed hostname (Via hostnamectl...)

yes - this can happen if you just change the hostname - usually, when you want to rename a host the following is necessary:
* change the name in '/etc/hostname' (that should proably happen with hostnamectl as well)
* change the entry in '/etc/hosts' (the hostname needs to resolve to an ip, which is configured on your machine
* test by running `ping $(uname -n)`

I usually also reboot the host afterwards to be sure that this will also work after the next upgrade but ymmv

after you've entered the correct entry in '/etc/hosts' you should restart pve-cluster.service (if you don't want to reboot)

I hope this helps!