pveproxy not starting

[mattps]

Hi forum,

I recently updated both of my PVE hosts to 8.4.13. This cleared out the temp mods I have in the gui so I used the following (as I have always done previously):

apt-get install lm-sensors
wget  https://raw.githubusercontent.com/Meliox/PVE-mods/main/pve-mod-gui-sensors.sh
bash pve-mod-gui-sensors.sh install

But this time the gui failed to restart. I can get to the server using ssh from my other pve host and using the suggested commands systemctl status pveproxy.service and systemctl status pveproxy.service I see this:

× pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2025-09-16 19:27:31 BST; 11s ago
Process: 2814 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 2818 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEPTION)
CPU: 1.065s

Sep 16 19:27:31 pve2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Sep 16 19:27:31 pve2 systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Sep 16 19:27:31 pve2 systemd[1]: pveproxy.service: Consumed 1.065s CPU time.
Sep 16 19:27:31 pve2 systemd[1]: pveproxy.service: Start request repeated too quickly.
Sep 16 19:27:31 pve2 systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Sep 16 19:27:31 pve2 systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.

and

░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
Sep 16 19:27:31 pve2 systemd[1]: pveproxy.service: Consumed 1.065s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service completed and consumed the indicated resources.
Sep 16 19:27:31 pve2 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.
Sep 16 19:27:31 pve2 systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
░░ Subject: A stop job for unit pveproxy.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pveproxy.service has finished.
░░
░░ The job identifier is 4392 and the job result is done.
Sep 16 19:27:31 pve2 systemd[1]: pveproxy.service: Consumed 1.065s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service completed and consumed the indicated resources.
Sep 16 19:27:31 pve2 systemd[1]: pveproxy.service: Start request repeated too quickly.
Sep 16 19:27:31 pve2 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'.
Sep 16 19:27:31 pve2 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 4392 and the job result is failed.

Anything I can do to get this back?

Thank you.

 

[t.lamprecht]

The actual error is not visible, can you please share the full journal output of the service, e.g. for getting all ouput of the current boot you could use:

journalctl -b -u pveproxy.service

 

[BobhWasatch]

You installed a script that modifies the PVE code. It apparently needs an update for PVE9. Maybe you could do "apt install --reinstall pveproxy" and don't install your patches to get back to a working system.

 

[mattps]

Thanks both. I managed to reverse the state by uninstalling the mod and the removing

$res->{thermalstate} = `sensors -j`;

from:

/usr/share/oerl5/PVE/API2/Nodes.pm

Then I restarted the pveproxy service and it came back - lessoned learned!