[SOLVED] GUI problem after update to Proxmox VE 7.2

R

Rojer

New Member
Aug 30, 2021
7
0
1
39
Hi!
I have cluster from 4 nodes proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve).
05.05.2022 I launched an update on one node from GUI.
After reboot node I can't login it GUI directly (Login failed).
From another (not updated node) i see it as "Status: unknown". VMs and containers are works.
I tried to update another node. And got the same result.

Can anyone help with advice?
 

Attachments

  • prox_72.JPG
    prox_72.JPG
    64.4 KB · Views: 23
Below is the output of pveversion -v on updated and not updated nodes.

proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.2-2pve-kernel-helper: 7.1-6
pve-kernel-5.15: 7.2-1pve-kernel-5.13: 7.1-5
pve-kernel-5.13: 7.1-9pve-kernel-5.11: 7.0-10
pve-kernel-5.11: 7.0-10pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.15.30-2-pve: 5.15.30-3pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.13.19-6-pve: 5.13.19-15pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.13.19-3-pve: 5.13.19-7pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.13.19-2-pve: 5.13.19-4pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.13.19-1-pve: 5.13.19-3pve-kernel-5.11.22-1-pve: 5.11.22-2
pve-kernel-5.11.22-7-pve: 5.11.22-12ceph-fuse: 15.2.13-pve1
pve-kernel-5.11.22-5-pve: 5.11.22-10corosync: 3.1.5-pve2
pve-kernel-5.11.22-4-pve: 5.11.22-9criu: 3.15-1+pve-1
pve-kernel-5.11.22-3-pve: 5.11.22-7glusterfs-client: 9.2-1
pve-kernel-5.11.22-1-pve: 5.11.22-2ifupdown2: 3.1.0-1+pmx3
ceph-fuse: 15.2.13-pve1ksm-control-daemon: 1.4-1
corosync: 3.1.5-pve2libjs-extjs: 7.0.0-1
criu: 3.15-1+pve-1libknet1: 1.22-pve2
glusterfs-client: 9.2-1libproxmox-acme-perl: 1.4.0
ifupdown2: 3.1.0-1+pmx3libproxmox-backup-qemu0: 1.2.0-1
ksm-control-daemon: 1.4-1libpve-access-control: 7.1-5
libjs-extjs: 7.0.0-1libpve-apiclient-perl: 3.2-1
libknet1: 1.22-pve2libpve-common-perl: 7.0-14
libproxmox-acme-perl: 1.4.2libpve-guest-common-perl: 4.0-3
libproxmox-backup-qemu0: 1.2.0-1libpve-http-server-perl: 4.0-4
libpve-access-control: 7.1-8libpve-storage-perl: 7.0-15
libpve-apiclient-perl: 3.2-1libspice-server1: 0.14.3-2.1
libpve-common-perl: 7.1-6lvm2: 2.03.11-2.1
libpve-guest-common-perl: 4.1-2lxc-pve: 4.0.11-1
libpve-http-server-perl: 4.1-1lxcfs: 4.0.11-pve1
libpve-storage-perl: 7.2-2novnc-pve: 1.3.0-1
libspice-server1: 0.14.3-2.1proxmox-backup-client: 2.1.2-1
lvm2: 2.03.11-2.1proxmox-backup-file-restore: 2.1.2-1
lxc-pve: 4.0.12-1proxmox-mini-journalreader: 1.3-1
lxcfs: 4.0.12-pve1proxmox-widget-toolkit: 3.4-4
novnc-pve: 1.3.0-3pve-cluster: 7.1-3
proxmox-backup-client: 2.1.8-1pve-container: 4.1-3
proxmox-backup-file-restore: 2.1.8-1pve-docs: 7.1-2
proxmox-mini-journalreader: 1.3-1pve-edk2-firmware: 3.20210831-2
proxmox-widget-toolkit: 3.4-10pve-firewall: 4.2-5
pve-cluster: 7.2-1pve-firmware: 3.3-4
pve-container: 4.2-1pve-ha-manager: 3.3-1
pve-docs: 7.2-2pve-i18n: 2.6-2
pve-edk2-firmware: 3.20210831-2pve-qemu-kvm: 6.1.0-3
pve-firewall: 4.2-5pve-xtermjs: 4.12.0-1
pve-firmware: 3.4-1qemu-server: 7.1-4
pve-ha-manager: 3.3-4smartmontools: 7.2-1
pve-i18n: 2.7-1spiceterm: 3.2-2
pve-qemu-kvm: 6.2.0-5swtpm: 0.7.0~rc1+2
pve-xtermjs: 4.16.0-1vncterm: 1.7-1
qemu-server: 7.2-2zfsutils-linux: 2.1.1-pve3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
 
On my QNAP D2, I just unchecked "Enable NFS v4 Service", and everything worked.
I will test the new kernel later.
 

Attachments

  • qnap_d2.JPG
    qnap_d2.JPG
    50 KB · Views: 16
Please mark the thread as solved (click edit, there's a dropdown at the left side of the title) if your problem is fixed :)
 
  • Like
Reactions: Rojer
You must log in or register to reply here.
Top Bottom