Issue after upgrade to 7.2.3

Kage

Active Member
Mar 29, 2016
40
5
28
32
Hello,

There is strange issue after upgrading to 7.2-3 ,

all nodes appears as unknown...

quorum looks works

pvecm status
Cluster information
-------------------
Name: proxceph
Config Version: 3
Transport: knet
Secure auth: on

Quorum information
------------------
Date: Wed May 4 20:02:32 2022
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 0x00000003
Ring ID: 1.22a1
Quorate: Yes

Votequorum information
----------------------
Expected votes: 3
Highest expected: 3
Total votes: 3
Quorum: 2
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.13.178
0x00000002 1 192.168.13.180
0x00000003 1 192.168.13.179 (local)


Can you advice how we can troubleshoot this ?

Best regards,
 

Attachments

  • proxmox-7.2.3.png
    proxmox-7.2.3.png
    113.4 KB · Views: 67

hvillemoes

New Member
Dec 13, 2020
12
1
3
71
Cure found: systemctl restart pvestatd

Storage icons, however, still has '?' status.



root@flamme:~# systemctl status pvestatd
â pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-05-04 16:18:32 CEST; 3h 50min ago
Process: 1052 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
Main PID: 1068 (pvestatd)
Tasks: 3 (limit: 38351)
Memory: 103.9M
CPU: 998ms
CGroup: /system.slice/pvestatd.service
ââ1068 pvestatd
ââ1342 /bin/mount -t nfs hedeqnap.l.vrc.dk:/pbs /mnt/pve/hedeqnap-nas
ââ1343 /sbin/mount.nfs hedeqnap.l.vrc.dk:/pbs /mnt/pve/hedeqnap-nas -o rw

May 04 16:18:32 flamme systemd[1]: Starting PVE Status Daemon...
May 04 16:18:32 flamme pvestatd[1068]: starting server
May 04 16:18:32 flamme systemd[1]: Started PVE Status Daemon.
May 04 16:18:44 flamme pvestatd[1068]: proxmox-backup-client failed: Error: unable to open chunk store 'pbs-qnap-ds' at "/mnt/pve/hedeqnap-nas/.chunks" - No such file or directory (os error 2)
root@flamme:~# systemctl restart pvestatd
root@flamme:~# systemctl status pvestatd
â pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-05-04 20:10:34 CEST; 2s ago
Process: 56657 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
Main PID: 56658 (pvestatd)
Tasks: 1 (limit: 38351)
Memory: 79.1M
CPU: 357ms
CGroup: /system.slice/pvestatd.service
ââ56658 pvestatd

May 04 20:10:34 flamme systemd[1]: Starting PVE Status Daemon...
May 04 20:10:34 flamme pvestatd[56658]: starting server
May 04 20:10:34 flamme systemd[1]: Started PVE Status Daemon.
root@flamme:~#


Best regards / hvilllemoes
 
Last edited:

Kage

Active Member
Mar 29, 2016
40
5
28
32
root@prox1:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-helper: 7.2-2
pve-kernel-5.15: 7.2-1
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-4
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-2-pve: 5.11.22-4
pve-kernel-5.11.21-1-pve: 5.11.21-1
pve-kernel-5.11.17-1-pve: 5.11.17-1
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-1
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1


root@prox1:~# systemctl status pvestatd
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-05-04 17:47:45 CEST; 2h 25min ago
Process: 1803 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
Main PID: 1960 (pvestatd)
Tasks: 3 (limit: 37927)
Memory: 98.2M
CPU: 2.555s
CGroup: /system.slice/pvestatd.service
├─1960 pvestatd
├─2286 /bin/mount -t nfs 10.199.119.1:/qnap-proxmox-vms /mnt/pve/qnap-proxmox-vms
└─2292 /sbin/mount.nfs 10.199.119.1:/qnap-proxmox-vms /mnt/pve/qnap-proxmox-vms -o rw

May 04 17:47:43 prox1 systemd[1]: Starting PVE Status Daemon...
May 04 17:47:45 prox1 pvestatd[1960]: starting server
May 04 17:47:45 prox1 systemd[1]: Started PVE Status Daemon.
root@prox1:~#



Upgrade was done using apt upgrade -y



Upgrade was done using apt upgrade -y
 

Kage

Active Member
Mar 29, 2016
40
5
28
32
nice, I did many upgrade from version 5.x to 7.x using only apt upgrade for minor versions, this never was issue.

Is any known way to fix it now ? apt full-upgrade do not points any packages now to update
 

M3ntalBadg3r

Member
Sep 6, 2019
2
0
6
41
I’m also seeing the same issue, I can see that both kage and hvilllemoes have NFS shares on a QNAP NAS, the same as me.

For reference I upgraded via the GUI
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,348
1,649
164
South Tyrol/Italy
shop.proxmox.com
Some report in the German forum mentions that they could resolve the issue with the QNAP NFS mount under 5.15 by explicitly using NFS version 4 to mount it (can be configured in the Storage options if you mount it via PVE, needs a manual unmount or reboot to re-mount with changed options)
 
Last edited:

Kage

Active Member
Mar 29, 2016
40
5
28
32
to be more sure, this issue appear in update not in way I did update ?

after set manually nfs to 4 in storage options proxmox start to work , but by default from QNAP nfs was mounted in version 4
 

Kage

Active Member
Mar 29, 2016
40
5
28
32
anyway thanks for tips, proxmox start to respond now
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,348
1,649
164
South Tyrol/Italy
shop.proxmox.com
to be more sure, this issue appear in update not in way I did update ?
IIRC, there was no new dependency removal that happened on this upgrade if comming from 7.1 (but depends on what version your system upgraded from), so you may have been lucky, anyhow I'd strongly recommend against just blindly passing the -y flag to any apt command and using full-upgrade (or dist-upgrade, which is just an alias for backward compat) in the future.

Your pveversion -v output seems also alright, so that backs the fact that your package state is alright.

If you're indeed using a QNAP NFS mount like the others reporting similar issues I'd think it's safe to say that the issue stems from that, not the upgrade procedure.
 

hvillemoes

New Member
Dec 13, 2020
12
1
3
71
Setting NFS version to 4 and rebooting did the trick for me.

Only rebooting did not help.

Thank you all.

/ Harald
 

M3ntalBadg3r

Member
Sep 6, 2019
2
0
6
41
I can confirm setting the QNAP NFS mounts to version 4.0 worked, previously they were set to 4.1

Thanks all
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,348
1,649
164
South Tyrol/Italy
shop.proxmox.com
Thanks for all your feedback here, I added this info to the known issues list of the Proxmox VE 7.2 release log
https://pve.proxmox.com/wiki/Roadmap#7.2-known-issues

We'll look into this on the kernel client side, but not having a QNAP test system may make that a bit harder to do.
 
  • Like
Reactions: Neobin and Kage

turkertalayman

New Member
Oct 25, 2021
1
0
1
48
Hi all,

I also confirm setting the QNAP NFS mounts to version 4.0 worked, previously they were set to 4.1 or Default.

Datacenter\Storage\{NFS mount}\Advanced\NFS Version set to 4

Thank you all. Good luck.
 

Attachments

  • Capture-proxmox 7.2.-3.JPG
    Capture-proxmox 7.2.-3.JPG
    28.9 KB · Views: 18

BeWu

New Member
May 26, 2021
8
2
3
41
Hello! Just wanted to confirm that observed the same issue with my QNAP, and setting NFS to version 4 solved the problem!

All the best everyone!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!