Failure in pveproxy

[m-electronics]

I have installed Proxmox VE 6.4 on a dedicated server without failures. After the reboot I don´t come on the WebUI of PVE. The "systemctl status pveproxy" says this

Feb 17 11:21:28 proxmox.localdomain pveproxy[4437]: worker exit
Feb 17 11:21:28 proxmox.localdomain pveproxy[4440]: /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.
Feb 17 11:21:28 proxmox.localdomain pveproxy[1232]: worker 4436 finished
Feb 17 11:21:28 proxmox.localdomain pveproxy[1232]: starting 1 worker(s)
Feb 17 11:21:28 proxmox.localdomain pveproxy[1232]: worker 4441 started
Feb 17 11:21:28 proxmox.localdomain pveproxy[4441]: /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.
Feb 17 11:21:28 proxmox.localdomain pveproxy[1232]: worker 4437 finished
Feb 17 11:21:28 proxmox.localdomain pveproxy[1232]: starting 1 worker(s)
Feb 17 11:21:28 proxmox.localdomain pveproxy[1232]: worker 4442 started
Feb 17 11:21:28 proxmox.localdomain pveproxy[4442]: /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.

When I was going to update the certs with the command "pvecm updatecerts --force" this failure message comes out

root@proxmox ~ # pvecm updatecerts --force
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

What I can do here?

 

[t.lamprecht]

Feb 17 11:21:28 proxmox.localdomain pveproxy[4440]: /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.

That's a symptom and not the cause, your pve-cluster service is not running, whyever that is, so the configuration filesystem mounted on /etc/pve cannot be used.

What I can do here?

More info please, this is normally not caused by just an installation + reboot alone.

For a basic assessment the following info would be good to have

pveversion -v
systemctl status pve-cluster
journalctl -b -u pve-cluster

 

[m-electronics]

pveversion -v

proxmox-ve: 6.4-1 (running kernel: 5.4.162-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-12
pve-kernel-helper: 6.4-12
pve-kernel-5.4.162-1-pve: 5.4.162-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2

"systemctl status pve-cluster"

Feb 17 12:14:04 proxmox.localdomain systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 12:14:04 proxmox.localdomain systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Feb 17 12:14:04 proxmox.localdomain systemd[1]: Stopped The Proxmox VE cluster filesystem.
Feb 17 12:14:04 proxmox.localdomain systemd[1]: pve-cluster.service: Start request repeated too quickly.
Feb 17 12:14:04 proxmox.localdomain systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Feb 17 12:14:04 proxmox.localdomain systemd[1]: Failed to start The Proxmox VE cluster filesystem.

"journalctl -b -u pve-cluster"

Feb 17 12:07:09 proxmox.localdomain systemd[1]: Starting The Proxmox VE cluster filesystem...
Feb 17 12:07:09 proxmox.localdomain pmxcfs[1010]: [main] crit: Unable to get local IP address
Feb 17 12:07:09 proxmox.localdomain pmxcfs[1010]: [main] crit: Unable to get local IP address
Feb 17 12:07:09 proxmox.localdomain systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Feb 17 12:07:09 proxmox.localdomain systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Feb 17 12:07:09 proxmox.localdomain systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Feb 17 12:07:09 proxmox.localdomain systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 12:07:09 proxmox.localdomain systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
Feb 17 12:07:09 proxmox.localdomain systemd[1]: Stopped The Proxmox VE cluster filesystem.
Feb 17 12:07:09 proxmox.localdomain systemd[1]: Starting The Proxmox VE cluster filesystem...
Feb 17 12:07:09 proxmox.localdomain pmxcfs[1125]: [main] crit: Unable to get local IP address
Feb 17 12:07:09 proxmox.localdomain pmxcfs[1125]: [main] crit: Unable to get local IP address
Feb 17 12:07:09 proxmox.localdomain systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Feb 17 12:07:09 proxmox.localdomain systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Feb 17 12:07:09 proxmox.localdomain systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: Stopped The Proxmox VE cluster filesystem.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: Starting The Proxmox VE cluster filesystem...
Feb 17 12:07:10 proxmox.localdomain pmxcfs[1127]: [main] crit: Unable to get local IP address
Feb 17 12:07:10 proxmox.localdomain pmxcfs[1127]: [main] crit: Unable to get local IP address
Feb 17 12:07:10 proxmox.localdomain systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Feb 17 12:07:10 proxmox.localdomain systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
Feb 17 12:07:10 proxmox.localdomain systemd[1]: Stopped The Proxmox VE cluster filesystem.

That are the results.

 

[t.lamprecht]

[main] crit: Unable to get local IP address

Was the hostname changed without ensuring that it resolves to the non-local IP of that node?

In any case, it seems the /etc/hosts (or your local DNS) is missing an entry, so pve-cluster cannot resolve the nodename to a static IP on startup and bails out.

As your hostname is proxmox adding a line like the following (fix the IP!) to /etc/hosts should help:

192.168.123.456 proxmox proxmox.localdomain

After that a reboot would be the simplest solution, albeit restarting pve-cluster, pveproxy, pvedaemon and pvestatd should also do the trick.

 

[m-electronics]

Can we write in German also?
This Problem with

Unable to find local ip address

I don´t have jet. But jet I have so many connection errors on the WebUI and I must reload the site then cames the "Certificate is unsecure" Warning from the browser everytime. That is very strange.

 

[m-electronics]

Like this failure message

Or so