我不会说太多英语，抱歉，这是通过翻译软件说的英语
I can't access the 8006 webpage at the moment but the vps on it is still operational, I don't want to affect the vps, how can I get back to managing from the webpage to pve
May 27 16:18:24 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:19:54 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:19:54 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:21:24 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:21:24 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
May 27 16:22:54 pve2 systemd[1]: pveproxy.service: Processes still around after final SIGKILL. Entering failed mode.
May 27 16:22:54 pve2 systemd[1]: pveproxy.service: Failed with result 'timeout'.
May 27 16:22:54 pve2 systemd[1]: Failed to start PVE API Proxy Server.
May 27 16:22:55 pve2 systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
May 27 16:22:55 pve2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
May 27 16:22:55 pve2 systemd[1]: Stopped PVE API Proxy Server.
May 27 16:22:55 pve2 systemd[1]: pveproxy.service: Found left-over process 30542 (pveproxy) in control group while starting unit. Ignoring.
May 27 16:22:55 pve2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 27 16:22:55 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:24:25 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:24:25 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:25:55 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:25:55 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
May 27 16:27:25 pve2 systemd[1]: pveproxy.service: Processes still around after final SIGKILL. Entering failed mode.
May 27 16:27:25 pve2 systemd[1]: pveproxy.service: Failed with result 'timeout'.
May 27 16:27:25 pve2 systemd[1]: Failed to start PVE API Proxy Server.
May 27 16:27:26 pve2 systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
May 27 16:27:26 pve2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
May 27 16:27:26 pve2 systemd[1]: Stopped PVE API Proxy Server.
May 27 16:27:26 pve2 systemd[1]: pveproxy.service: Found left-over process 30542 (pveproxy) in control group while starting unit. Ignoring.
May 27 16:27:26 pve2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 27 16:27:26 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:28:56 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:28:56 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:30:26 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:30:26 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
May 27 16:31:56 pve2 systemd[1]: pveproxy.service: Processes still around after final SIGKILL. Entering failed mode.
May 27 16:31:56 pve2 systemd[1]: pveproxy.service: Failed with result 'timeout'.
May 27 16:31:56 pve2 systemd[1]: Failed to start PVE API Proxy Server.
May 27 16:31:57 pve2 systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
May 27 16:31:57 pve2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
May 27 16:31:57 pve2 systemd[1]: Stopped PVE API Proxy Server.
May 27 16:31:57 pve2 systemd[1]: pveproxy.service: Found left-over process 30542 (pveproxy) in control group while starting unit. Ignoring.
May 27 16:31:57 pve2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 27 16:31:57 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
root@pve2:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: deactivating (final-sigkill) (Result: timeout) since Tue 2025-05-27 16:06:21 CST; 28min ago
Process: 31830 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=killed, signal=TERM)
Tasks: 1 (limit: 14745)
Memory: 164.1M
CGroup: /system.slice/pveproxy.service
└─30542 /usr/bin/perl -T /usr/bin/pveproxy stop
May 27 16:31:57 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
root@pve2:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 1.2.5-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
openvswitch-switch: 2.10.7+ds1-0+deb10u5
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
top - 16:41:31 up 239 days, 15:28, 7 users, load average: 105.09, 95.63, 93.50
Tasks: 1436 total, 5 running, 1431 sleeping, 0 stopped, 0 zombie
%Cpu(s): 75.1 us, 4.3 sy, 0.0 ni, 20.2 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
MiB Mem : 515938.6 total, 2955.7 free, 472671.4 used, 40311.5 buff/cache
MiB Swap: 8192.0 total, 28.7 free, 8163.3 used. 35919.1 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
12091 root 20 0 12.4g 14544 7888 S 4786 0.0 263577,23 pved
30119 root 20 0 17.0g 8.2g 8324 S 449.7 1.6 193317:56 kvm
16327 root 20 0 9108504 4.4g 4836 S 220.8 0.9 820204:18 kvm
11289 root 20 0 96.9g 93.4g 5112 S 210.4 18.5 429035:24 kvm
I can't access the 8006 webpage at the moment but the vps on it is still operational, I don't want to affect the vps, how can I get back to managing from the webpage to pve
May 27 16:18:24 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:19:54 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:19:54 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:21:24 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:21:24 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
May 27 16:22:54 pve2 systemd[1]: pveproxy.service: Processes still around after final SIGKILL. Entering failed mode.
May 27 16:22:54 pve2 systemd[1]: pveproxy.service: Failed with result 'timeout'.
May 27 16:22:54 pve2 systemd[1]: Failed to start PVE API Proxy Server.
May 27 16:22:55 pve2 systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
May 27 16:22:55 pve2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
May 27 16:22:55 pve2 systemd[1]: Stopped PVE API Proxy Server.
May 27 16:22:55 pve2 systemd[1]: pveproxy.service: Found left-over process 30542 (pveproxy) in control group while starting unit. Ignoring.
May 27 16:22:55 pve2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 27 16:22:55 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:24:25 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:24:25 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:25:55 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:25:55 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
May 27 16:27:25 pve2 systemd[1]: pveproxy.service: Processes still around after final SIGKILL. Entering failed mode.
May 27 16:27:25 pve2 systemd[1]: pveproxy.service: Failed with result 'timeout'.
May 27 16:27:25 pve2 systemd[1]: Failed to start PVE API Proxy Server.
May 27 16:27:26 pve2 systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
May 27 16:27:26 pve2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
May 27 16:27:26 pve2 systemd[1]: Stopped PVE API Proxy Server.
May 27 16:27:26 pve2 systemd[1]: pveproxy.service: Found left-over process 30542 (pveproxy) in control group while starting unit. Ignoring.
May 27 16:27:26 pve2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 27 16:27:26 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:28:56 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:28:56 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:30:26 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:30:26 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
May 27 16:31:56 pve2 systemd[1]: pveproxy.service: Processes still around after final SIGKILL. Entering failed mode.
May 27 16:31:56 pve2 systemd[1]: pveproxy.service: Failed with result 'timeout'.
May 27 16:31:56 pve2 systemd[1]: Failed to start PVE API Proxy Server.
May 27 16:31:57 pve2 systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
May 27 16:31:57 pve2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
May 27 16:31:57 pve2 systemd[1]: Stopped PVE API Proxy Server.
May 27 16:31:57 pve2 systemd[1]: pveproxy.service: Found left-over process 30542 (pveproxy) in control group while starting unit. Ignoring.
May 27 16:31:57 pve2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 27 16:31:57 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
root@pve2:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: deactivating (final-sigkill) (Result: timeout) since Tue 2025-05-27 16:06:21 CST; 28min ago
Process: 31830 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=killed, signal=TERM)
Tasks: 1 (limit: 14745)
Memory: 164.1M
CGroup: /system.slice/pveproxy.service
└─30542 /usr/bin/perl -T /usr/bin/pveproxy stop
May 27 16:31:57 pve2 systemd[1]: Starting PVE API Proxy Server...
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Start-pre operation timed out. Terminating.
May 27 16:33:27 pve2 systemd[1]: pveproxy.service: Control process exited, code=killed, status=15/TERM
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: State 'stop-final-sigterm' timed out. Killing.
May 27 16:34:57 pve2 systemd[1]: pveproxy.service: Killing process 30542 (pveproxy) with signal SIGKILL.
root@pve2:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 1.2.5-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
openvswitch-switch: 2.10.7+ds1-0+deb10u5
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
top - 16:41:31 up 239 days, 15:28, 7 users, load average: 105.09, 95.63, 93.50
Tasks: 1436 total, 5 running, 1431 sleeping, 0 stopped, 0 zombie
%Cpu(s): 75.1 us, 4.3 sy, 0.0 ni, 20.2 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
MiB Mem : 515938.6 total, 2955.7 free, 472671.4 used, 40311.5 buff/cache
MiB Swap: 8192.0 total, 28.7 free, 8163.3 used. 35919.1 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
12091 root 20 0 12.4g 14544 7888 S 4786 0.0 263577,23 pved
30119 root 20 0 17.0g 8.2g 8324 S 449.7 1.6 193317:56 kvm
16327 root 20 0 9108504 4.4g 4836 S 220.8 0.9 820204:18 kvm
11289 root 20 0 96.9g 93.4g 5112 S 210.4 18.5 429035:24 kvm
