Upgrade PVE 7 to 8 GUI services do not start automatically

[Ramartins]

Hello everyone

I have the following problem: I updated the PVE version from 7 to 8. So far, everything is fine. However, when I restarted the server, the WEB GUI services did not start automatically. I had to start them all manually by accessing the server via SSH. I used the command below and then I was able to access the GUI

systemctl start pve-cluster pveproxy pvedaemon pvestatd pvescheduler pve-firewall

With the command systemctl --failed, I received the following information

UNIT LOAD ACTIVE SUB DESCRIPTION
● ceph-mgr@pve.service loaded failed failed Ceph cluster manager daemon
● pve-guests.service loaded failed failed PVE guests

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
2 loaded units listed.

Command systemctl status pve-guests.service I receive the following information

× pve-guests.service - PVE guests Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2024-11-07 17:47:02 -03; 16h Aug Main PID: 1487 (code=exited, status=111) CPU: 1.183s Nov 07 17:47:01 pve systemd[1]: Starting pve-guests.service - PVE guests... Nov 07 17:47:02 pve pvesh[1487]: ipcc_send_rec[1] failed: Connection refused Nov 07 17:47: 02 pve pvesh[1487]: ipcc_send_rec[2] failed: Connection refused Nov 07 17:47:02 pve pvesh[1487]: ipcc_send_rec[3] failed: Connection refused Nov 07 17:47:02 pve pvesh[1487]: Unable to load access control list: Connection refused
Nov 07 17:47:02 pve systemd[1]: pve-guests.service: Main process exited, code=exited, status=111/n/a
Nov 07 17:47:02 pve systemd[1]: pve-guests.service: Failed with result 'exit-code'.
Nov 07 17:47:02 pve systemd[1]: Failed to start pve-guests.service - PVE guests.
Nov 07 17:47:02 pve systemd[1]: pve-guests.service: Consumed 1.183s CPU time.

I didn't understand exactly where the error is, I searched the forum and didn't find anything related to this.

If anyone can help me I would be very grateful

 

[Hannes Laimer]

Hey,

did any errors pop up during the upgrade? Could you try

apt update
apt dist-upgrade
apt reinstall pve-manager

Also check journalctl -b, it'll give you the logs since the last boot, look for any errors, especially for the services you mentioned. Do you have a cluster? If, do other nodes have a same problem after the upgrade?

 

[Ramartins]

During the upgrade, no errors occurred. I strictly followed the instructions in the manual https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 to complete the upgrade. I also tried running the apt command to reinstall pve-manager, but without success.

As for the cluster, it is still not working, we are performing upgrades to connect it to another equally updated server.

did any errors pop up during the upgrade? Could you try

apt update
apt dist-upgrade
apt reinstall pve-manager

Also check journalctl -b, it'll give you the logs since the last boot, look for any errors, especially for the services you mentioned. Do you have a cluster? If, do other nodes have a same problem after the upgrade?

Attached is the journalctl -b log

 

[Ramartins]

Does anyone have any suggestions ???

 

[Daniel_Dog]

To be honest my recommendation (and what i always advice and do in general every major version) is just backup your data from the server.
Then just do a clean install of the new major version with the ISO file.

Updating between major versions has the risk to break things. (Even though it is officially supported to do so.)
And in my experience it is just easier and quicker to do a clean install every major version. (x.2 is major and 8.x is minor)