VMs names (and other things) disappeared from GUI

[m3a2r1]

I've restarted pvedaemon after changing names of nfs resources and I've got only vm ids on GUI. All vms are running.
Anybody can help me how to fix that without restart node?

 

[oguz]

hi,

can you post pveversion -v and maybe a screenshot of the issue?

what was the exact change you made to the nfs resources?

 

[m3a2r1]

pveversion -v output:
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-8
pve-kernel-5.3: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve8
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.1-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-14
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

Screenshot:



About nfs resources: I've readdressed devices in network and changed nfs server ip to dns name. Servers are the same.

 

[oguz]

are your disks being stored on the nfs?

I've readdressed devices in network and changed nfs server ip to dns name.

maybe it's not resolving correctly?

could you post /etc/pve/storage.cfg

 

[m3a2r1]

The first NFS named NAS is on the same node - it's VM 102, most of vms have disk stored on this nfs and they are still working so it resolving correctly. It looks like only gui can't show properly.

my /etc/pve/storage.cfg

dir: local
        path /var/lib/vz
        content backup,iso,vztmpl

lvmthin: local-lvm
        thinpool data
        vgname pve
        content images,rootdir

dir: VMs
        path /mnt/pve/VMs
        content images,backup,rootdir,snippets,vztmpl,iso
        is_mountpoint 1
        nodes proxmox

lvm: raid
        vgname pve
        content images,rootdir
        shared 0

lvm: NAS
        vgname freenas
        content rootdir,images
        shared 0

nfs: freenas
        export /mnt/NAS/NFS
        path /mnt/pve/freenas
        server wb-storage.wodbud.local
        content images,backup,rootdir,snippets,vztmpl,iso
        maxfiles 1
        options vers=3

nfs: STOR2
        export /mnt/NAS/NFS
        path /mnt/pve/STOR2
        server wb-storage2.wodbud.local
        content rootdir,backup,snippets,iso,images
        maxfiles 5

 

[oguz]

STOR2 is using the same export as freenas. are these on the same node?

have you tried specifying the IP to see if it works without the name?

 

[m3a2r1]

Nope, they're on another nodes but they're both freenas and it's the same path to nfs share. I think it's not the issue, it worked earlier.

 

[m3a2r1]

Any ideas?

 

[m3a2r1]

I've found that:

root@proxmox:/etc# mount | grep nfs
freenas.wodbud.local:/mnt/NAS/NFS on /mnt/pve/freenas type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.1.88,mountvers=3,mountport=789,mountproto=udp,local_lock=none,addr=172.16.1.88)
172.16.1.115:/mnt/NAS/NFS on /mnt/pve/STOR2 type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.1.115,mountvers=3,mountport=757,mountproto=udp,local_lock=none,addr=172.16.1.115)
root@proxmox:/etc#

It's the old ip of second storage. Fortunately second because vms disks are on first

 

[m3a2r1]

And now it's the best. After restoring STOR2 to old IP, everything started to show correctly. So now I've got the question, why ip changing of nfs share which is only for backup and not storing any vm's disks, crashing interface of proxmox?