[SOLVED] failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm

S

sjoshua270

New Member
Jan 25, 2022
7
0
1
31
I'm having trouble running apt upgrade on my PVE instance.
The error I get is:
Code: 
dpkg: error processing package pve-manager (--configure):
 installed pve-manager package post-installation script subprocess returned error exit status 1

I've checked journalctl -xe, and the output has a ton of these:
Code: 
Jan 25 09:37:39 pve pveproxy[1941]: starting 1 worker(s)
Jan 25 09:37:39 pve pveproxy[1941]: worker 2333 started
Jan 25 09:37:39 pve pveproxy[2333]: /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.
Jan 25 09:37:40 pve pveproxy[2331]: worker exit

Any ideas?
 
A little history of activity:
I recently updated docker-compose and ran out of space while trying to run apt upgrade later on. To resolve that, I looked at my docker containers and was able to remove about 9GB of space by removing running containers and using docker system prune -a --volumes. After that, I rebooted and ran apt update. No problems. apt upgrade, and here we are. This is my media center server, so I would really love to get it up and running.
 
What's the output of systemctl status pve-cluster.service and df -h?
 
systemctl status pve-cluster.service
Code: 
● 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 Tue 2022-01-25 09:39:33 EST; 19min ago
    Process: 2529 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 6ms

Jan 25 09:39:33 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jan 25 09:39:33 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jan 25 09:39:33 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jan 25 09:39:33 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jan 25 09:39:33 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.

df -h
Code: 
Filesystem            Size  Used Avail Use% Mounted on
udev                  7.8G     0  7.8G   0% /dev
tmpfs                 1.6G  1.2M  1.6G   1% /run
/dev/mapper/pve-root   29G  9.1G   19G  33% /
tmpfs                 7.8G     0  7.8G   0% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
/dev/sda2             511M  328K  511M   1% /boot/efi
local-zfs             366G  128K  366G   1% /local-zfs
local-zfs/media       389G   24G  366G   6% /local-zfs/media
tmpfs                 1.6G     0  1.6G   0% /run/user/0
 
Looks like pve-cluster failed and pmxcfs is not mounted (/etc/pve).

Try running systemctl restart pve-cluster.service.
 
systemctl restart pve-cluster.service
Code: 
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
Code: 
● 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 Tue 2022-01-25 10:03:43 EST; 10s ago
    Process: 3543 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 6ms

Jan 25 10:03:43 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jan 25 10:03:43 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jan 25 10:03:43 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jan 25 10:03:43 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jan 25 10:03:43 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.

journalctl -xe
Code: 
Jan 25 10:05:22 pve pveproxy[1941]: starting 1 worker(s)
Jan 25 10:05:22 pve pveproxy[1941]: worker 3607 finished
Jan 25 10:05:22 pve pveproxy[1941]: worker 3609 started
Jan 25 10:05:22 pve pveproxy[3609]: /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.
^^^ Over and over again with different worker numbers
 
Is this a cluster or a standalone node?

You mentioned running apt upgrade. We recommend using apt full-upgrade as a simple upgrade can lead to issues.
 
Please provide your /etc/hosts file.
 
That's the issue. Please remove the second line and add an additional one that maps your IP address, for example 192.168.0.10 to your host:
192.168.0.10 pve.<domain> pve

Replace the IP address with your configured one (ip a) and `pve` with whatever is configured in /etc/hostname.
 
I have same problem and I did the same steps as suggested by mira but still issue not resolved.

root@OE:/etc/pve# 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 Fri 2023-10-06 13:51:10 IST; 24min ago
Process: 4558 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
CPU: 8ms

Oct 06 13:51:10 OE systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Oct 06 13:51:10 OE systemd[1]: Stopped The Proxmox VE cluster filesystem.
Oct 06 13:51:10 OE systemd[1]: pve-cluster.service: Start request repeated too quickly.
Oct 06 13:51:10 OE systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Oct 06 13:51:10 OE systemd[1]: Failed to start The Proxmox VE cluster filesystem.
root@OE:/etc/pve# df -h
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 291M 2.9G 10% /run
/dev/mapper/pve-root 94G 94G 0 100% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 511M 328K 511M 1% /boot/efi
tmpfs 3.2G 0 3.2G 0% /run/user/0
root@OE:/etc/pve# systemctl restart pve-cluster.service
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.
root@OE:/etc/pve# /etc/hosts
-bash: /etc/hosts: Permission denied
root@OE:/etc/pve# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.50 OE.ojasenterprises.co.in OE
 
Neobin said:
Your root is full...
You can find quite a few threads here regarding this, including how to proceed/fix.
Click to expand...
I have the same exact issue (like the replies in this post)
I actually had a single node working perfectly for months and suddenly this happened

My root is at 75%, still 11GB available

I'm also getting issues with the network, I can ping even external sources and DNS but cannot access the GUI, apt update (gets stuck in waiting for headers) and SSH (from and to)
 
Last edited:
undertone2230 said:
I have the same exact issue (like the replies in this post)
I actually had a single node working perfectly for months and suddenly this happened

My root is at 75%, still 11GB available

I'm also getting issues with the network, I can ping even external sources and DNS but cannot access the GUI, apt update (gets stuck in waiting for headers) and SSH (from and to)
Click to expand...
Please provide the output of the following commands:
Code: 
pveversion -v
df -h
The complete error message and the journal since the last boot:
journalctl -b | gzip > journal.txt.gz
 
mira said:
Please provide the output of the following commands:
Code: 
pveversion -v
df -h
The complete error message and the journal since the last boot:
journalctl -b | gzip > journal.txt.gz
Click to expand...

I finally did a fresh install and migrated most everything manually. I sent too many hours on this. Furthermore, I just learned that I must research about doing migrations/changes to host and network resources before messing everything up.
 
You must log in or register to reply here.
Top Bottom