Upgraded from 5.4 to 7.4 - cannot connect to web GUI

[wsurfa]

As per title, upgraded following the guide from 5 to 7. I cannot now connect to the web GUI.

I can ping using SSH to external and internal addresses and can ping the proxmox @ 192.168.1.190.

https://192.168.1.190:8006/ gives 'this site cant be reached'

I had minimal knowledge when I set this up a few years ago, and what knowledge I had, has evaporated since.

I was only using to run plex on OMV and that's all I need to get back in reality

thanks for any help

 

[Lukas Wagner]

Hello,
please provide the output of the following commands:

• pveversion -v
• systemctl status pveproxy.service
• systemctl status pvedaemon.service

You can also try restarting the two services (in case you have not tried a full reboot yet), simply replace 'status' with 'reload-or-restart'.

 

[Lukas Wagner]

Also, how exactly did you perform the upgrade?

Usually the process is upgrading 5 -> 6 -> 7 using the guides below:

https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

 

[wsurfa]

Yep followed that process

 

[wsurfa]

root@pve:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-5.15: 7.4-3
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-4.15: 5.4-16
pve-kernel-4.15.18-27-pve: 4.15.18-55
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 3.0.4-pve1~bpo9
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libpve-access-control: 5.1-12
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.5-1~bpo9+2
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 5.0-38
pve-container: 2.0-41
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 3.0-22
pve-firmware: 3.6-5
pve-ha-manager: 2.0-9
pve-i18n: 2.12-1
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 4.7.0-3
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: not correctly installed

 

[wsurfa]

root@pve:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-05-15 19:54:32 BST; 22h ago
Process: 1103 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
CPU: 374ms

May 15 19:54:32 pve pveproxy[1103]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
May 15 19:54:32 pve pveproxy[1103]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
May 15 19:54:32 pve pveproxy[1103]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
May 15 19:54:32 pve pveproxy[1103]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
May 15 19:54:32 pve pveproxy[1103]: Compilation failed in require at /usr/bin/pveproxy line 11.
May 15 19:54:32 pve pveproxy[1103]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
May 15 19:54:32 pve systemd[1]: pveproxy.service: Control process exited, code=exited status=255
May 15 19:54:32 pve systemd[1]: Failed to start PVE API Proxy Server.
May 15 19:54:32 pve systemd[1]: pveproxy.service: Unit entered failed state.
May 15 19:54:32 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.

 

[wsurfa]

root@pve:~# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-05-15 19:54:32 BST; 22h ago
Process: 1086 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)
CPU: 379ms

May 15 19:54:32 pve pvedaemon[1086]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
May 15 19:54:32 pve pvedaemon[1086]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
May 15 19:54:32 pve pvedaemon[1086]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
May 15 19:54:32 pve pvedaemon[1086]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
May 15 19:54:32 pve pvedaemon[1086]: Compilation failed in require at /usr/bin/pvedaemon line 11.
May 15 19:54:32 pve pvedaemon[1086]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
May 15 19:54:32 pve systemd[1]: pvedaemon.service: Control process exited, code=exited status=255
May 15 19:54:32 pve systemd[1]: Failed to start PVE API Daemon.
May 15 19:54:32 pve systemd[1]: pvedaemon.service: Unit entered failed state.
May 15 19:54:32 pve systemd[1]: pvedaemon.service: Failed with result 'exit-code'.

 

[wsurfa]

The regular appearance of 'failed' is I guess not a good sign

 

[wsurfa]

thanks for the help

 

[wsurfa]

no need for any help, I've managed to kill the system entirely.....doh!

 

[Neobin]

root@pve:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-5.15: 7.4-3
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-4.15: 5.4-16
pve-kernel-4.15.18-27-pve: 4.15.18-55
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 3.0.4-pve1~bpo9
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libpve-access-control: 5.1-12
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.5-1~bpo9+2
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 5.0-38
pve-container: 2.0-41
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 3.0-22
pve-firmware: 3.6-5
pve-ha-manager: 2.0-9
pve-i18n: 2.12-1
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 4.7.0-3
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: not correctly installed

Your (attempt to) upgrade has gone severely wrong, since most of the packages are still on the/a (really) old version.

no need for any help, I've managed to kill the system entirely.....doh!

Unfortunate to read this, but in this case, it might probably be cleaner, easier and quicker to reinstall and restore from backups anyway.