I cannot access the WEB GUI. May be a possible certificate error?

R

ryanmar89

New Member
Jul 22, 2022
7
0
1
Does anyone know a fix? I had shut down my system properly to move it into my network rack and now whenever I startup my server, I get a ton of errors saying services cannot start properly.

Code: 
Jul 21 22:37:48 bigboi pveproxy[1444]: worker 2439 started
Jul 21 22:37:48 bigboi pveproxy[2438]: /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 1917.
Jul 21 22:37:48 bigboi pveproxy[2439]: /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 1917.
Jul 21 22:37:53 bigboi pveproxy[2437]: worker exit
Jul 21 22:37:53 bigboi pveproxy[1444]: worker 2437 finished
Jul 21 22:37:53 bigboi pveproxy[1444]: starting 1 worker(s)
Jul 21 22:37:53 bigboi pveproxy[1444]: worker 2440 started
Jul 21 22:37:53 bigboi pveproxy[2440]: /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 1917.
Jul 21 22:37:53 bigboi pveproxy[2438]: worker exit
Jul 21 22:37:53 bigboi pveproxy[2439]: worker exit
Jul 21 22:37:53 bigboi pveproxy[1444]: worker 2439 finished
Jul 21 22:37:53 bigboi pveproxy[1444]: worker 2438 finished
-- Journal begins at Tue 2022-07-12 13:09:04 CDT, ends at Thu 2022-07-21 22:38:13 CDT. --
Jul 21 22:32:15 bigboi pveproxy[1444]: starting 3 worker(s)
Jul 21 22:32:15 bigboi pveproxy[1444]: worker 2207 started
Jul 21 22:32:15 bigboi pveproxy[1444]: worker 2208 started
Jul 21 22:32:15 bigboi pveproxy[1444]: worker 2209 started
Jul 21 22:32:15 bigboi pveproxy[2207]: /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 1917.
Jul 21 22:32:15 bigboi pveproxy[2208]: /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 1917.
Jul 21 22:32:15 bigboi pveproxy[2209]: /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 1917.
Jul 21 22:32:20 bigboi pveproxy[2207]: worker exit
Jul 21 22:32:20 bigboi pveproxy[2208]: worker exit
Jul 21 22:32:20 bigboi pveproxy[2209]: worker exit
Jul 21 22:32:20 bigboi pveproxy[1444]: worker 2209 finished
Jul 21 22:32:20 bigboi pveproxy[1444]: worker 2207 finished
Jul 21 22:32:20 bigboi pveproxy[1444]: worker 2208 finished
Jul 21 22:32:20 bigboi pveproxy[1444]: starting 3 worker(s)
Jul 21 22:32:20 bigboi pveproxy[1444]: worker 2210 started
Jul 21 22:32:20 bigboi pveproxy[1444]: worker 2211 started
Jul 21 22:32:20 bigboi pveproxy[1444]: worker 2212 started
Jul 21 22:32:20 bigboi pveproxy[2210]: /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 1917.
Jul 21 22:32:20 bigboi pveproxy[2211]: /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 1917.
Jul 21 22:32:20 bigboi pveproxy[2212]: /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 1917.
Jul 21 22:32:25 bigboi pveproxy[2210]: worker exit
Jul 21 22:32:25 bigboi pveproxy[2211]: worker exit
Jul 21 22:32:25 bigboi pveproxy[2212]: worker exit
Jul 21 22:32:25 bigboi pveproxy[1444]: worker 2212 finished
Jul 21 22:32:25 bigboi pveproxy[1444]: starting 1 worker(s)
Jul 21 22:32:25 bigboi pveproxy[1444]: worker 2210 finished
Jul 21 22:32:25 bigboi pveproxy[1444]: worker 2211 finished
Jul 21 22:32:25 bigboi pveproxy[1444]: worker 2213 started
Jul 21 22:32:25 bigboi pveproxy[2213]: /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 1917.
Jul 21 22:32:30 bigboi pveproxy[1444]: starting 2 worker(s)
Jul 21 22:32:30 bigboi pveproxy[1444]: worker 2214 started
Jul 21 22:32:30 bigboi pveproxy[1444]: worker 2215 started
Jul 21 22:32:30 bigboi pveproxy[2213]: worker exit
Jul 21 22:32:30 bigboi pveproxy[2214]: /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 1917.
Jul 21 22:32:30 bigboi pveproxy[2215]: /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 1917.
Jul 21 22:32:30 bigboi pveproxy[1444]: worker 2213 finished
Jul 21 22:32:30 bigboi pveproxy[1444]: starting 1 worker(s)
Jul 21 22:32:30 bigboi pveproxy[1444]: worker 2216 started
Jul 21 22:32:30 bigboi pveproxy[2216]: /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 1917.
Jul 21 22:32:35 bigboi pveproxy[2214]: worker exit
Jul 21 22:32:35 bigboi pveproxy[2215]: worker exit
Jul 21 22:32:35 bigboi pveproxy[1444]: worker 2215 finished
Jul 21 22:32:35 bigboi pveproxy[1444]: worker 2214 finished
Jul 21 22:32:35 bigboi pveproxy[1444]: starting 2 worker(s)
Jul 21 22:32:35 bigboi pveproxy[1444]: worker 2217 started
Jul 21 22:32:35 bigboi pveproxy[1444]: worker 2218 started
Jul 21 22:32:35 bigboi pveproxy[2216]: worker exit
Jul 21 22:32:35 bigboi pveproxy[2217]: /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 1917.
Jul 21 22:32:35 bigboi pveproxy[2218]: /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 1917.
Jul 21 22:32:35 bigboi pveproxy[1444]: worker 2216 finished
Jul 21 22:32:35 bigboi pveproxy[1444]: starting 1 worker(s)
Jul 21 22:32:35 bigboi pveproxy[1444]: worker 2219 started
Jul 21 22:32:35 bigboi pveproxy[2219]: /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 1917.
Jul 21 22:32:40 bigboi pveproxy[2217]: worker exit
Jul 21 22:32:40 bigboi pveproxy[2218]: worker exit
Jul 21 22:32:40 bigboi pveproxy[1444]: worker 2218 finished
Jul 21 22:32:40 bigboi pveproxy[1444]: worker 2217 finished
Jul 21 22:32:40 bigboi pveproxy[1444]: starting 2 worker(s)
Jul 21 22:32:40 bigboi pveproxy[1444]: worker 2220 started
Jul 21 22:32:40 bigboi pveproxy[1444]: worker 2221 started
Jul 21 22:32:40 bigboi pveproxy[2219]: worker exit
 
I am trying to get it back up asap but I am unsure where to even start. Here's what showed up at boot.

If there is a way to get rid of the "dependency" for "lvrv" I think that may be the issue as that was a flashdrive that I had mounted temporarily for iso files but even when I start it with it plugged in, it does the same thing.

Screenshot_20220721-224237_Gallery.jpg
 
Last edited:
Actually my bad. the dependency error goes away after plugging in the flash drive during boot but the key errors still show in the log.
 
The main issue is that the configuration filesystem (pmxcfs) doesn't come up as one can see by the pve-cluster.service failure, and such the /etc/pve mountpoint that hosts the TLS CA and certs for all nodes (cluster or standalone) isn't available.

Please post the output of:

Code: 
ls -l /etc/pve
systemctl status pve-cluster

hopefully we can get enough hints from that to solve this.
 
t.lamprecht said:
The main issue is that the configuration filesystem (pmxcfs) doesn't come up as one can see by the pve-cluster.service failure, and such the /etc/pve mountpoint that hosts the TLS CA and certs for all nodes (cluster or standalone) isn't available.

Please post the output of:

Code: 
ls -l /etc/pve
systemctl status pve-cluster

hopefully we can get enough hints from that to solve this.
Click to expand...

Here's the outputs

Code: 
ls -l /etc/pve
total 28
-rw------- 1 root root 1679 Jul 21 23:00 ca.key
-rw-r--r-- 1 root root   41 Jul 21 23:02 ca.srl
drwxr-xr-x 2 root root 4096 Jul 21 23:54 local
-rw-r--r-- 1 root root 1432 Jul 21 23:54 pve-root-ca.pem
-rw------- 1 root root 1679 Jul 21 22:58 pve-ssl.key
-rw-r--r-- 1 root root 1172 Jul 21 23:02 pve-ssl.pem
-rw-r--r-- 1 root root  980 Jul 21 23:02 server.csr


Code: 
 systemctl status pve-cluster
● 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 Fri 2022-07-22 00:24:32 CDT; 4min 6s ago
    Process: 8988 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 10ms

Jul 22 00:24:32 bigboi systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jul 22 00:24:32 bigboi systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jul 22 00:24:32 bigboi systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jul 22 00:24:32 bigboi systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 22 00:24:32 bigboi systemd[1]: Failed to start The Proxmox VE cluster filesystem.
root@bigboi:~#
 
Ok, your mountpoint isn't empty and that's failing pve-cluster to startup.

Do:

Bash: 
mv /etc/pve /etc/pve-OLD
mkdir /etc/pve
systemctl reset-failed pve-cluster
systemctl start pve-cluster
 
  • Like
Reactions: dravis
t.lamprecht said:
Ok, your mountpoint isn't empty and that's failing pve-cluster to startup.

Do:

Bash: 
mv /etc/pve /etc/pve-OLD
mkdir /etc/pve
systemctl reset-failed pve-cluster
systemctl start pve-cluster
Click to expand...
You are a life saver! I cannot believe that worked. One more thing. The server along with the vms have question marks next to all of them but seem to be functional. Is that supposed to happen?

1658471080778.png
 
Glad that worked out!

Well, due to pve-cluster not starting up I think some services that depend on that didn't start either, for the question mark thing it would normally be the pvestatd, so try

systemctl restart pvestatd

To get an overview of failed units check: systemctl list-units --failed (note, some kernel/debugfs things are ok to fail, but if it got pve/proxmox in name it may be more relevant)
 
t.lamprecht said:
Glad that worked out!

Well, due to pve-cluster not starting up I think some services that depend on that didn't start either, for the question mark thing it would normally be the pvestatd, so try

systemctl restart pvestatd

To get an overview of failed units check: systemctl list-units --failed (note, some kernel/debugfs things are ok to fail, but if it got pve/proxmox in name it may be more relevant)
Click to expand...
Yeah that's what it was. Thank you so much!
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom