Unable to load access control list: Connection refused

[Lucaaa]

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.

okay

 

[Lucaaa]

uninstalled, what I have to do now

 

[Lucaaa]

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.

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:50:39 CEST; 5s ago
Process: 5866 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

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

 

[Lucaaa]

uninstalled

 

[Lucaaa]

now?

 

[Lucaaa]

what i have to do?

 

[oguz]

please stop spamming...

i've already told you what to do. you need to correct your /etc/hosts and restart the pve-cluster service.

if the service isn't restarting properly, check the output of journalctl -xe like it suggests you. read the error messages and search in the forum.

 

[Lucaaa]

please stop spamming...

i've already told you what to do. you need to correct your /etc/hosts and restart the pve-cluster service.

if the service isn't restarting properly, check the output of journalctl -xe like it suggests you. read the error messages and search in the forum.

I corrected, I have just

127.0.0.1 localhost.localdomain localhost
192.168.1.4 lucadev.tk lucadev localhost

now
but not working the restart

 

[Lucaaa]

Jul 01 16:12:33 lucadev pveproxy[9556]: worker exit
Jul 01 16:12:33 lucadev pveproxy[9557]: worker exit
Jul 01 16:12:33 lucadev pveproxy[1861]: worker 9556 finished
Jul 01 16:12:33 lucadev pveproxy[1861]: worker 9557 finished
Jul 01 16:12:33 lucadev pveproxy[1861]: starting 2 worker(s)
Jul 01 16:12:33 lucadev pveproxy[1861]: worker 9598 started
Jul 01 16:12:33 lucadev pveproxy[1861]: worker 9599 started
Jul 01 16:12:33 lucadev pveproxy[9598]: /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 1727.
Jul 01 16:12:33 lucadev pveproxy[9599]: /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 1727.
Jul 01 16:12:33 lucadev pveproxy[9558]: worker exit
Jul 01 16:12:33 lucadev pveproxy[1861]: worker 9558 finished
Jul 01 16:12:33 lucadev pveproxy[1861]: starting 1 worker(s)
Jul 01 16:12:33 lucadev pveproxy[1861]: worker 9600 started
Jul 01 16:12:33 lucadev pveproxy[9600]: /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 1727.
Jul 01 16:12:34 lucadev systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jul 01 16:12:34 lucadev systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-cluster.service has entered the 'failed' state with result 'exit-code'.
Jul 01 16:12:34 lucadev systemd[1]: Failed to start The Proxmox VE cluster filesystem.

 

[Lucaaa]

The problem is here:

/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)

 

[oguz]

try rebooting your node.

you're spamming the forum too much, your account is an hour old with 20 posts. please tone it down. don't successively post every couple of minutes...

this is a common misconfiguration, just search in the forum for the error message and you will find answers to this exact issue.

 

[Lucaaa]

/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)


How to fix this?

 

[Lucaaa]

...

 

[Lucaaa]

anyone?

 

[Lucaaa]

please

 

[aaron]

Do you have files in /etc/pve already? Move them somewhere else and then restart the pve-cluster service with systemctl restart pve-cluster.service

 

[Lucaaa]

Do you have files in /etc/pve already? Move them somewhere else and then restart the pve-cluster service with systemctl restart pve-cluster.service

I have a directory called local

 

[Lucaaa]

Thanks, you solved!

 

[MoxProxxer]

Same problem here. Installed from your official ISO on my machine at home.
Gave it during installation the name rigel.home.org, was still pve.localdomain in /etc/hosts

So changed /etc/hosts to

root@pve:/etc# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.2.20 rigel.home.org rigel

And rebooted the machine. Guess what: machine comes up, again named "PVE", the web frontend is not accessible anymore, but I can SSH into it. Then I thought maybe

root@pve:/etc# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.2.20 rigel.home.org rigel pvelocalhost

because instructions unclear, tried to restart

░░ The job identifier is 5215 and the job result is done.
Aug 07 13:28:24 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Aug 07 13:28:24 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pve-cluster.service has entered the 'failed' state with result 'exit-code'.
Aug 07 13:28:24 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
░░ Subject: A start job for unit pve-cluster.service has failed

There are quite some of these in the logs, but that shouldn't matter much - should it?

Aug 07 13:28:19 pve pveproxy[2151]: /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 1891.
...
Aug 07 13:28:19 pve pveproxy[2152]: /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 1891.

Be it as it may, my PVE7 playground is broken now. Luckily it's just a playground. Won't touch the 6.4 production PVEs for sure.

 

[MoxProxxer]

Also solved. /etc/hostname remained "pve". Changing that and many things start to work automagically.
It's a little unfortunate - especially when the correct name was given during the installation.