I'm currently running a Proxmox v9.1 server which I had installed from scratch and which has been running without any problems for a little over a month.
Earlier this morning I tried to install iperf3 onto the PVE host, but the installation failed:
I wondered what the problem was but went on to do something else. A few hours later, I tried to access the Proxmox web GUI and discovered it wasn't responding. All of the LXC containers were still running, however, and I could ssh into the server. After doing some research into the problem, I learned that pveproxy most likely had stopped running. I checked the status of pveproxy and got the following:
Similar error to what I experienced when I tried to install iperf3. I decided just to restart pveproxy:
Running journalctl -xeu pveproxy.service shows the following:
As I was getting ready to post this, I ran pveversion and also got the same error:
It seems that the Perl installation on my Proxmox server somehow got corrupted and this is causing Proxmox to fail. Is there some way I can reinstall Perl to fix this problem?
Earlier this morning I tried to install iperf3 onto the PVE host, but the installation failed:
Bash:
root@asta:~# apt install iperf3
Installing:
iperf3
Installing dependencies:
libiperf0 libsctp1
Suggested packages:
lksctp-tools
Summary:
Upgrading: 0, Installing: 3, Removing: 0, Not Upgrading: 79
Download size: 163 kB
Space needed: 425 kB / 118 GB available
Continue? [Y/n]
Get:1 http://deb.debian.org/debian trixie/main amd64 libsctp1 amd64 1.0.21+dfsg-1 [25.8 kB]
Get:2 http://deb.debian.org/debian trixie/main amd64 libiperf0 amd64 3.18-2+deb13u1 [100 kB]
Get:3 http://deb.debian.org/debian trixie/main amd64 iperf3 amd64 3.18-2+deb13u1 [37.3 kB]
Fetched 163 kB in 0s (801 kB/s)
Recursive inheritance detected in package 'IO::File'.
Error: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (25)
Error: Failure running script /usr/share/proxmox-ve/pve-apt-hookI wondered what the problem was but went on to do something else. A few hours later, I tried to access the Proxmox web GUI and discovered it wasn't responding. All of the LXC containers were still running, however, and I could ssh into the server. After doing some research into the problem, I learned that pveproxy most likely had stopped running. I checked the status of pveproxy and got the following:
Bash:
root@asta:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/usr/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-12-09 13:17:55 EST; 2 days ago
Invocation: c53939a94212410ca25108aa9e86fac0
Process: 2584 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 2608 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Process: 2619 ExecStartPost=sh -c [ ! -e /var/log/pveam.log ] && /usr/bin/pveupdate (code=exite>
Process: 1904216 ExecReload=/usr/bin/pveproxy restart (code=exited, status=25)
Main PID: 2613 (pveproxy)
Tasks: 2 (limit: 37983)
Memory: 224.2M (peak: 397.3M)
CPU: 1d 9h 46min 22.309s
CGroup: /system.slice/pveproxy.service
├─ 2613 pveproxy
└─3389772 "pveproxy worker"
Dec 12 02:32:17 asta pveproxy[2613]: worker 3389772 started
Dec 12 02:32:17 asta pveproxy[3389772]: ERROR: Recursive inheritance detected in package 'PVE::Serv>
Dec 12 02:32:17 asta pveproxy[3389772]: Recursive inheritance detected in package 'PVE::Service::pv>
Dec 12 02:32:17 asta pveproxy[3389772]: start failed - Recursive inheritance detected in package 'P>
Dec 12 02:32:17 asta pveproxy[2613]: worker 3389771 finished
Dec 12 02:32:17 asta pveproxy[2613]: starting 2 worker(s)
Dec 12 02:32:17 asta pveproxy[2613]: worker 3389773 started
Dec 12 02:32:17 asta pveproxy[3389773]: ERROR: Recursive inheritance detected in package 'PVE::Serv>
Dec 12 02:32:17 asta pveproxy[3389773]: Recursive inheritance detected in package 'PVE::Service::pv>
Dec 12 02:32:17 asta pveproxy[3389773]: start failed - Recursive inheritance detected in package 'P>
Dec 12 02:32:17 asta pveproxy[2613]: worker 3389772 finished
Dec 12 02:32:17 asta pveproxy[2613]: worker 3389774 started
Dec 12 02:32:17 asta pveproxy[3389774]: ERROR: Recursive inheritance detected in package 'PVE::Serv>
Dec 12 02:32:17 asta pveproxy[3389774]: Recursive inheritance detected in package 'PVE::Service::pv>
Dec 12 02:32:17 asta pveproxy[3389774]: start failed - Recursive inheritance detected in package 'P>Similar error to what I experienced when I tried to install iperf3. I decided just to restart pveproxy:
Bash:
root@asta:~# systemctl restart pveproxy
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
root@asta:/var/log/apt# systemctl status pveproxy
× pveproxy.service - PVE API Proxy Server
Loaded: loaded (/usr/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2025-12-12 02:32:42 EST; 7min ago
Duration: 2d 13h 14min 45.810s
Invocation: a11f4decfdf74a0893edcf270e10904e
Process: 3395075 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=25)
Process: 3395077 ExecStart=/usr/bin/pveproxy start (code=exited, status=25)
Dec 12 02:32:42 asta systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Dec 12 02:32:42 asta systemd[1]: pveproxy.service: Start request repeated too quickly.
Dec 12 02:32:42 asta systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Dec 12 02:32:42 asta systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.Running journalctl -xeu pveproxy.service shows the following:
Code:
Dec 12 14:36:20 asta systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 41142.
Dec 12 14:36:20 asta pvecm[3958964]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:20 asta pveproxy[3958966]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:20 asta systemd[1]: pveproxy.service: Control process exited, code=exited, status=25/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 25.
Dec 12 14:36:20 asta systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Dec 12 14:36:20 asta systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 41142 and the job result is failed.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 12 14:36:21 asta systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 41242.
Dec 12 14:36:21 asta pvecm[3958969]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta pveproxy[3958971]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Control process exited, code=exited, status=25/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 25.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Dec 12 14:36:21 asta systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 41242 and the job result is failed.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 12 14:36:21 asta systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 41342.
Dec 12 14:36:21 asta pvecm[3958973]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta pveproxy[3958975]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Control process exited, code=exited, status=25/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 25.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Dec 12 14:36:21 asta systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 41342 and the job result is failed.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 12 14:36:21 asta systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 41442.
Dec 12 14:36:21 asta pvecm[3958980]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta pveproxy[3958982]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Control process exited, code=exited, status=25/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 25.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Dec 12 14:36:21 asta systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 41442 and the job result is failed.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 12 14:36:21 asta systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 41542.
Dec 12 14:36:21 asta pvecm[3959006]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta pveproxy[3959008]: Recursive inheritance detected in package 'IO::File'.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Control process exited, code=exited, status=25/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 25.
Dec 12 14:36:21 asta systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Dec 12 14:36:21 asta systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 41542 and the job result is failed.
Dec 12 14:36:22 asta systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 12 14:36:22 asta systemd[1]: pveproxy.service: Start request repeated too quickly.
Dec 12 14:36:22 asta systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Dec 12 14:36:22 asta systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 41642 and the job result is failed.As I was getting ready to post this, I ran pveversion and also got the same error:
Bash:
root@asta:/var/log# pveversion
Recursive inheritance detected in package 'IO::File'.It seems that the Perl installation on my Proxmox server somehow got corrupted and this is causing Proxmox to fail. Is there some way I can reinstall Perl to fix this problem?