Cannot log in via webgui after upgrade(pveproxy service down)

tianmo

New Member
Apr 27, 2018
16
0
1
43
Today I upgraded my pve5.4 to 6.0. I have a 2-node cluster. One of the upgrades is normal. After another upgrade, I can't access webgui. I report connection refused 595. I log in from the normal one and see One is a green hook, and the other is a gray question mark. However, this node that cannot log in with webgui can still log in through ssh normally. Then I learned about the pveproxy service after searching in the forum. The following is my pveproxy service information. How to solve this? Thank you!!

Code:
root@pve:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-07-18 16:22:44 CST; 2min 41s ago
  Process: 1695 ExecStart=/usr/bin/pveproxy start (code=exited, status=2)

Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Jul 18 16:22:44 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:22:44 pve systemd[1]: Failed to start PVE API Proxy Server.
Code:
root@pve:~# journalctl -xe
-- 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 2395 and the job result is failed.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:41:18 pve 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.
Jul 18 16:41:18 pve systemd[1]: Stopped 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 2482 and the job result is done.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 18 16:41:18 pve 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'.
Jul 18 16:41:18 pve systemd[1]: Failed to start 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 2482 and the job result is failed.
 

Stefan_R

Proxmox Staff Member
Staff member
Jun 4, 2019
309
48
28
Vienna
The logs you posted seem incomplete, e.g. the error you showed is from the service restarting after already having failed.

Try "journalctl -u pveproxy" to get more complete logs (or even "journalctl -u 'pve*' -e").
 

tianmo

New Member
Apr 27, 2018
16
0
1
43
The logs you posted seem incomplete, e.g. the error you showed is from the service restarting after already having failed.

Try "journalctl -u pveproxy" to get more complete logs (or even "journalctl -u 'pve*' -e").
thank you very much!
Code:
root@pve:~# journalctl -u pveproxy
-- Logs begin at Thu 2019-07-18 16:17:30 CST, end at Thu 2019-07-18 16:56:45 CST. --
Jul 18 16:17:35 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:17:35 pve pveproxy[1133]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:17:35 pve pveproxy[1133]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:17:35 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:17:35 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:17:35 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:17:35 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:17:35 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 1.
Jul 18 16:17:35 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:17:35 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:17:35 pve pveproxy[1151]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:17:35 pve pveproxy[1151]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:17:35 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:17:35 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:17:35 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
Jul 18 16:17:36 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:17:36 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:17:36 pve pveproxy[1153]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:17:36 pve pveproxy[1153]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:17:36 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
Jul 18 16:17:36 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:17:36 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:17:36 pve pveproxy[1154]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:17:36 pve pveproxy[1154]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:17:36 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:17:36 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
Jul 18 16:17:37 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:17:37 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:17:37 pve pveproxy[1173]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:17:37 pve pveproxy[1173]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:17:37 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Jul 18 16:17:37 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 18 16:17:37 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:17:37 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:20:57 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:20:57 pve pveproxy[1517]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:20:57 pve pveproxy[1517]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:20:57 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 1.
Jul 18 16:20:57 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:20:57 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:20:57 pve pveproxy[1525]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:20:57 pve pveproxy[1525]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:20:57 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
Jul 18 16:20:57 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:20:57 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:20:57 pve pveproxy[1527]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:20:57 pve pveproxy[1527]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:20:57 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:20:57 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
Jul 18 16:20:57 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:20:57 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:20:58 pve pveproxy[1530]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:20:58 pve pveproxy[1530]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:20:58 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
Jul 18 16:20:58 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:20:58 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:20:58 pve pveproxy[1531]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:20:58 pve pveproxy[1531]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:20:58 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Jul 18 16:20:58 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 18 16:20:58 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:20:58 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:22:43 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:22:43 pve pveproxy[1681]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:22:43 pve pveproxy[1681]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:22:43 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 1.
Jul 18 16:22:43 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:22:43 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:22:43 pve pveproxy[1689]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:22:43 pve pveproxy[1689]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:22:43 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
Jul 18 16:22:43 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:22:43 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:22:43 pve pveproxy[1692]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:22:43 pve pveproxy[1692]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:22:43 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:22:43 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
Jul 18 16:22:43 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:22:43 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:22:44 pve pveproxy[1693]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:22:44 pve pveproxy[1693]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:22:44 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
Jul 18 16:22:44 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:22:44 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:22:44 pve pveproxy[1695]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:22:44 pve pveproxy[1695]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:22:44 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Jul 18 16:22:44 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 18 16:22:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:22:44 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:41:17 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:41:17 pve pveproxy[3321]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:41:17 pve pveproxy[3321]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:41:17 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 1.
Jul 18 16:41:17 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:41:17 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:41:17 pve pveproxy[3330]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:41:17 pve pveproxy[3330]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:41:17 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:41:17 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
Jul 18 16:41:17 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:41:17 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:41:18 pve pveproxy[3333]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:41:18 pve pveproxy[3333]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:41:18 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
Jul 18 16:41:18 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:41:18 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:41:18 pve pveproxy[3336]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:41:18 pve pveproxy[3336]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:41:18 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
Jul 18 16:41:18 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:41:18 pve systemd[1]: Starting PVE API Proxy Server...
Jul 18 16:41:18 pve pveproxy[3337]: Can't locate PVE/Service/pveproxy.pm in @INC (you may need to install the PVE::Service::pveproxy module) (@INC contains: /et
Jul 18 16:41:18 pve pveproxy[3337]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:41:18 pve systemd[1]: Failed to start PVE API Proxy Server.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Jul 18 16:41:18 pve systemd[1]: Stopped PVE API Proxy Server.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 18 16:41:18 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 18 16:41:18 pve systemd[1]: Failed to start PVE API Proxy Server.
 

Stefan_R

Proxmox Staff Member
Staff member
Jun 4, 2019
309
48
28
Vienna
This seems like some files are missing from your installation. Are you sure the upgrade worked without errors? Do other PVE commands work? (e.g. pvecm status, pveversion, pct list, qm list, ...)

Maybe try running 'apt dist-upgrade' again.

(BTW: Your logs are still cut off on the side, it seems you copied the output from your pager. If you run journalctl with --no-pager or pipe its output into a file you get plain text including all information.)
 

tianmo

New Member
Apr 27, 2018
16
0
1
43
This seems like some files are missing from your installation. Are you sure the upgrade worked without errors? Do other PVE commands work? (e.g. pvecm status, pveversion, pct list, qm list, ...)

Maybe try running 'apt dist-upgrade' again.

(BTW: Your logs are still cut off on the side, it seems you copied the output from your pager. If you run journalctl with --no-pager or pipe its output into a file you get plain text including all information.)
Oh, indeed, when I upgraded, the root partition space is not enough, and the upgrade is interrupted. I re-expanded the root partition and re-upgraded and reported an error. I have been tossing for a long time before the upgrade is successful. Then I found that webgui could not log in. I rerun apt dist-upgrade and the feedback says 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
"pvecm status" is working fine, "pveversion" reports the following error
Code:
root@pve:~# pveversion
Can't locate PVE/API2/APT.pm in @INC (you may need to install the PVE::API2::APT module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/bin/pveversion line 7.
BEGIN failed--compilation aborted at /usr/bin/pveversion line 7.
 

Stefan_R

Proxmox Staff Member
Staff member
Jun 4, 2019
309
48
28
Vienna
You can reinstall all pve packages, which should fix any missing files:
Code:
apt install --reinstall $(apt list --installed | grep pve | sed 's/\/.*$//g')
 

tianmo

New Member
Apr 27, 2018
16
0
1
43
You can reinstall all pve packages, which should fix any missing files:
Code:
apt install --reinstall $(apt list --installed | grep pve | sed 's/\/.*$//g')
thank you very much. I tried your code. But it seems to be useless, pveproxy still can't run, journalctl -xe gets the same error message as before
 

Stefan_R

Proxmox Staff Member
Staff member
Jun 4, 2019
309
48
28
Vienna
I tried your code. But it seems to be useless
But did it install packages? Or did it not work in general?

Try 'apt list --installed | grep pve' on its own. That command is showing 66 packages in my testing, if your count is significantly lower, maybe try 'apt install proxmox-ve' to install missing packages?

As a last resort you could try to reinstall the node entirely. Filling up a disk mid-upgrade can lead to some very weird behaviour, it could very well be that your installation is broken beyond repair.
 

tianmo

New Member
Apr 27, 2018
16
0
1
43
But did it install packages? Or did it not work in general?

Try 'apt list --installed | grep pve' on its own. That command is showing 66 packages in my testing, if your count is significantly lower, maybe try 'apt install proxmox-ve' to install missing packages?

As a last resort you could try to reinstall the node entirely. Filling up a disk mid-upgrade can lead to some very weird behaviour, it could very well be that your installation is broken beyond repair.
Thank you again.I'll try
 

tianmo

New Member
Apr 27, 2018
16
0
1
43
But did it install packages? Or did it not work in general?

Try 'apt list --installed | grep pve' on its own. That command is showing 66 packages in my testing, if your count is significantly lower, maybe try 'apt install proxmox-ve' to install missing packages?

As a last resort you could try to reinstall the node entirely. Filling up a disk mid-upgrade can lead to some very weird behaviour, it could very well be that your installation is broken beyond repair.
Yeah!!!!!!! IT DOSE WORK!problem resolved!!Thank you very much!!!!!!
 

About

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

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 your own in 60 seconds.

Buy now!