Can't reach PVE GUI after upgrade to pve6.41

[Flare]

Hi,there
I have some problems after upgraded to pve6 from pve5.
Here is what the journalctl -xe post:

root@Shuo:~# journalctl -xe
Mar 25 00:40:29 Shuo pveproxy[4862]: Compilation failed in require at /usr/bin/pveproxy line 11.
Mar 25 00:40:29 Shuo pveproxy[4862]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Mar 25 00:40:30 Shuo systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
-- 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 2.
Mar 25 00:40:30 Shuo 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'.
Mar 25 00:40:30 Shuo 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 120856 and the job result is failed.
Mar 25 00:40:30 Shuo systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Mar 25 00:40:30 Shuo systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 201.
-- 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.
Mar 25 00:40:30 Shuo systemd[1]: rrdcached.service: Start request repeated too quickly.
Mar 25 00:40:30 Shuo systemd[1]: rrdcached.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit rrdcached.service has entered the 'failed' state with result 'exit-code'.
Mar 25 00:40:30 Shuo systemd[1]: Failed to start LSB: start or stop rrdcached.
-- Subject: A start job for unit rrdcached.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit rrdcached.service has finished with a failure.
--
-- The job identifier is 121201 and the job result is failed.
Mar 25 00:40:30 Shuo 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 121119 and the job result is done.
Mar 25 00:40:30 Shuo systemd[1]: pve-cluster.service: Start request repeated too quickly.
Mar 25 00:40:30 Shuo systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-cluster.service has entered the 'failed' state with result 'exit-code'.
Mar 25 00:40:30 Shuo systemd[1]: Failed to start The Proxmox VE cluster filesystem.
-- Subject: A start job for unit pve-cluster.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-cluster.service has finished with a failure.
--
-- The job identifier is 121200 and the job result is failed.
Mar 25 00:40:30 Shuo systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
-- Subject: A start job for unit corosync.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit corosync.service has finished successfully.
--
-- The job identifier is 121202.


I checked the /etc/host, it seems everything looks okay. And I can conect via SSH, but I cannot open the GUI page. Someone can help me?