PVEProxy Error

P

paradinglunatic

New Member
Jan 6, 2026
4
0
1
After upgrading from 8.x to 9 (currently on 9.1.4), my logs are getting flooded with the same error every 5 seconds, where the PID shown changes based on one of the three PID's pveproxy is running on. I've restarted the service and this is the only error that shows up.

pveproxy[738421]: internal error at /usr/share/perl5/PVE/RESTHandler.pm line 387

I'm not entirely sure what the issue is but looking at that general area of that file it's in the subroutine of "map_path_to_methods".

My setup is pretty simple, single node, installed with two local disks with ZFS in a mirror and two NFS mounts one where my VMs are stored and the other for backups.

Everything appears to be working fine.

The only other issue I have since the upgrade is that when applying updates through the web UI and clicking the upgrade button, it pops up a new window and does everything right but in the tasks it'll show the shell task attempting to run then eventually "failing" when the updates are complete and I exit out of the window. I've tried clearing cookies, trying different browsers. Same issue each time.
 
Yup, that upgrade guide is the one I followed to perform the upgrade. Didn't run into any strange issues during the upgrade either.

Just double checked my repo's and there are no references to bookworm.
 
please run on the host root console:
Code: 
apt update
apt dist-upgrade -y
apt autoremove -y
And show us the results in a seperate CODE-Block.
 
Last edited:
Code: 
root@pve01:~# apt update
Get:1 http://security.debian.org trixie-security InRelease [43.4 kB]
Hit:2 http://ftp.us.debian.org/debian trixie InRelease                                                     
Get:3 http://ftp.us.debian.org/debian trixie-updates InRelease [47.3 kB]
Hit:4 http://download.proxmox.com/debian/ceph-squid trixie InRelease
Hit:5 http://download.proxmox.com/debian/pve trixie InRelease
Fetched 90.7 kB in 0s (642 kB/s)
All packages are up to date.   
root@pve01:~# apt dist-upgrade -y
Summary:                       
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
root@pve01:~# apt autoremove -y
Summary:                       
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
root@pve01:~#
 
Hi,
I'd try to check the installed files using debsums:
Code: 
apt install debsums
debsums -c
which can take a while, and will output package files differing from the expected.

Please share a bigger excerpt from the system logs before and after the error message.
 
fiona said:
Hi,
I'd try to check the installed files using debsums:
Code: 
apt install debsums
debsums -c
which can take a while, and will output package files differing from the expected.

Please share a bigger excerpt from the system logs before and after the error message.
Click to expand...
Installed and ran debsums -c. Nothing was returned.

Here's a bit from the log. Basically I restarted pveproxy and captured the error prior to the restart of pveproxy, the restart of pveproxy, and a few lines after it started producing the error which it just keeps repeating over and over approximately every 5 seconds. There's nothing else to show after that except more of the same error.

Code: 
Jan 14 08:05:43 pve01 pveproxy[247592]: internal error at /usr/share/perl5/PVE/RESTHandler.pm line 387.
Jan 14 08:05:47 pve01 systemd[1]: Stopping pveproxy.service - PVE API Proxy Server...
Jan 14 08:05:48 pve01 pveproxy[247592]: internal error at /usr/share/perl5/PVE/RESTHandler.pm line 387.
Jan 14 08:05:48 pve01 pveproxy[1565]: received signal TERM
Jan 14 08:05:48 pve01 pveproxy[1565]: server closing
Jan 14 08:05:48 pve01 pveproxy[244526]: worker exit
Jan 14 08:05:48 pve01 pveproxy[266959]: worker exit
Jan 14 08:05:48 pve01 pveproxy[1565]: worker 266959 finished
Jan 14 08:05:48 pve01 pveproxy[1565]: worker 244526 finished
Jan 14 08:05:48 pve01 pveproxy[1565]: worker 247592 finished
Jan 14 08:05:48 pve01 pveproxy[1565]: server stopped
Jan 14 08:05:49 pve01 pveproxy[300434]: worker exit
Jan 14 08:05:49 pve01 systemd[1]: pveproxy.service: Deactivated successfully.
Jan 14 08:05:49 pve01 systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Jan 14 08:05:49 pve01 systemd[1]: pveproxy.service: Consumed 59.534s CPU time, 388.1M memory peak.
Jan 14 08:05:49 pve01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Jan 14 08:05:50 pve01 pveproxy[300443]: starting server
Jan 14 08:05:50 pve01 pveproxy[300443]: starting 3 worker(s)
Jan 14 08:05:50 pve01 pveproxy[300443]: worker 300444 started
Jan 14 08:05:50 pve01 pveproxy[300443]: worker 300445 started
Jan 14 08:05:50 pve01 pveproxy[300443]: worker 300446 started
Jan 14 08:05:50 pve01 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Jan 14 08:05:53 pve01 pveproxy[300445]: internal error at /usr/share/perl5/PVE/RESTHandler.pm line 387.
Jan 14 08:05:58 pve01 pveproxy[300445]: internal error at /usr/share/perl5/PVE/RESTHandler.pm line 387.
Jan 14 08:06:03 pve01 pveproxy[300446]: internal error at /usr/share/perl5/PVE/RESTHandler.pm line 387.
 
You must log in or register to reply here.
Top Bottom