Unable to load access control list: Connection refused

L

Lucaaa

Member
Jul 1, 2020
35
0
11
25
I've problem with the access to the gui of proxmox and i can't use the terminal, because all that I type of proxmox says

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

service pve-cluster restart
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
 
hi,

please post cat /etc/hosts
 
remove the line starting with 127.0.1.1 and do systemctl restart pve-cluster afterwards, it should be fixed

edit: i forgot, add another entry for your IP address of PVE.

check with hostname --ip-address, it needs to return the IP of proxmox
 
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.

● 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 Wed 2020-07-01 15:25:52 CEST; 8s ago
Process: 2911 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Jul 01 15:25:52 lucadev systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jul 01 15:25:52 lucadev systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jul 01 15:25:52 lucadev systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jul 01 15:25:52 lucadev systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jul 01 15:25:52 lucadev systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 01 15:25:52 lucadev systemd[1]: Failed to start The Proxmox VE cluster filesystem.
 
/etc/hosts should look like this:

Code: 
127.0.0.1 localhost.localdomain localhost
192.168.x.x pve.yourdomain.com pve pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

replace the IP, domain and hostname of the node as necessary...

after that run hostname --ip-address and it should return the 192.168.x.x (or your version of it)
 
also, you have cloud-init configured on your PVE host? that can't end well.... it will keep changing the /etc/hosts
 
127.0.0.1 localhost.localdomain localhost
192.168.1.4 pve.lucadev.tk pve pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

---

hostname --ip-address
hostname: Name or service not known
 
i don't have cloud init configured, but i see this
# Your system has configured 'manage_etc_hosts' as True.
# As a result, if you wish for changes to this file to persist
# then you will need to either
# a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl
# b.) change or remove the value of 'manage_etc_hosts' in
in the /etc/hosts
 
Lucaaa said:
127.0.0.1 localhost.localdomain localhost
192.168.1.4 pve.lucadev.tk pve pvelocalhost

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

---

hostname --ip-address
hostname: Name or service not known
Click to expand...

replace the pve in my example with your actual hostname from /etc/hostname


Lucaaa said:
i don't have cloud init configured, but i see this
# Your system has configured 'manage_etc_hosts' as True.
# As a result, if you wish for changes to this file to persist
# then you will need to either
# a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl
# b.) change or remove the value of 'manage_etc_hosts' in
in the /etc/hosts
Click to expand...
is your machine from a hoster? maybe your hoster has it configured.
 
But i still have this
systemctl restart pve-cluster
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
 
systemctl status pve-cluster.service
● 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 Wed 2020-07-01 15:43:55 CEST; 9s ago
Process: 5071 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Jul 01 15:43:55 lucadev systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jul 01 15:43:55 lucadev systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jul 01 15:43:55 lucadev systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jul 01 15:43:55 lucadev systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jul 01 15:43:55 lucadev systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 01 15:43:55 lucadev systemd[1]: Failed to start The Proxmox VE cluster filesystem.
 
if i do
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
 
If i do
/usr/bin/pmxcfs
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
[main] crit: fuse_mount error: File exists
[main] notice: exit proxmox configuration filesystem (-1)
 
you need to get pve-cluster running for all of that to work.

cockpit is interfering with your hostname. that's why it's failing.

uninstall cockpit, put it in a VM instead if you have to use it.
 
You must log in or register to reply here.
Top Bottom