Hi,
Today I found my VMs not responding, so started to investigate. After finding no fault I decided to restart PVE which presented this issue. Host boots but won't start the VE, so no VMs or GUI is available, only access through SSH. Syslog is repeating this same messages over and over...
Edit: I also noticed that the folder '/etc/pve/local/' is missing, so that error is legit, question is why and if that is related to VE not having started, or part of the cause for it?
And yes, despite the message about IP address, it has one, same as always, and is reachable on the network as it should be...
Having been pleased with the configuration and performance, I haven't done any changes in weeks, apart from patching it and occasional restarts when warranted. All patches are from stable channels. Please help.
Update:
I eventually found this thread, https://forum.proxmox.com/threads/e...key-key_file-or-key-at-usr-share-perl5.48943/ in which incorrect hostname had been entered in /etc/hosts. I knew mine was not touched since installation, but checked it anyways and [yawdrop] - the netbios part of the hostname was missing! After adding and rebooting, things are back to normal (I hope). Unsettling that this just dissapeared, no one else either has access or my credentials. Either way, problem solved.
Today I found my VMs not responding, so started to investigate. After finding no fault I decided to restart PVE which presented this issue. Host boots but won't start the VE, so no VMs or GUI is available, only access through SSH. Syslog is repeating this same messages over and over...
Code:
Sep 5 09:27:34 pve pveproxy[2677]: worker exit
Sep 5 09:27:34 pve pveproxy[908]: worker 2677 finished
Sep 5 09:27:34 pve pveproxy[908]: starting 2 worker(s)
Sep 5 09:27:34 pve pveproxy[908]: worker 2682 started
Sep 5 09:27:34 pve pveproxy[908]: worker 2683 started
Sep 5 09:27:34 pve pveproxy[2682]: /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.
Sep 5 09:27:34 pve pveproxy[2683]: /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.
Sep 5 09:27:34 pve pveproxy[2678]: worker exit
Sep 5 09:27:34 pve pveproxy[908]: worker 2678 finished
Sep 5 09:27:34 pve pveproxy[908]: starting 1 worker(s)
Sep 5 09:27:34 pve pveproxy[908]: worker 2684 started
Sep 5 09:27:34 pve pveproxy[2684]: /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.
Sep 5 09:27:38 pve pmxcfs[2679]: [main] crit: Unable to get local IP address
Sep 5 09:27:38 pve pmxcfs[2679]: [main] crit: Unable to get local IP address
Sep 5 09:27:38 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Sep 5 09:27:38 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Sep 5 09:27:38 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 5 09:27:38 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Sep 5 09:27:38 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 254.
Sep 5 09:27:38 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Sep 5 09:27:38 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
root@pve:~#
Code:
root@pve:~# journalctl -b -u pve-cluster
-- Journal begins at Wed 2021-08-11 15:15:39 CEST, ends at Sun 2021-09-05 09:48:08 CEST. --
Sep 05 09:00:02 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Sep 05 09:00:14 pve pmxcfs[785]: [main] crit: Unable to get local IP address
Sep 05 09:00:14 pve pmxcfs[785]: [main] crit: Unable to get local IP address
Sep 05 09:00:14 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Sep 05 09:00:14 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Sep 05 09:00:14 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 05 09:00:14 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
Sep 05 09:00:14 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Sep 05 09:00:14 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Sep 05 09:00:20 pve pmxcfs[898]: [main] crit: Unable to get local IP address
Sep 05 09:00:20 pve pmxcfs[898]: [main] crit: Unable to get local IP address
Sep 05 09:00:20 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Sep 05 09:00:20 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Sep 05 09:00:20 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 05 09:00:21 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
Sep 05 09:00:21 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.And yes, despite the message about IP address, it has one, same as always, and is reachable on the network as it should be...
Having been pleased with the configuration and performance, I haven't done any changes in weeks, apart from patching it and occasional restarts when warranted. All patches are from stable channels. Please help.
Update:
I eventually found this thread, https://forum.proxmox.com/threads/e...key-key_file-or-key-at-usr-share-perl5.48943/ in which incorrect hostname had been entered in /etc/hosts. I knew mine was not touched since installation, but checked it anyways and [yawdrop] - the netbios part of the hostname was missing! After adding and rebooting, things are back to normal (I hope). Unsettling that this just dissapeared, no one else either has access or my credentials. Either way, problem solved.
Last edited:
