After update NFS storage stopped working

G

gkovacs

Renowned Member
Dec 22, 2008
516
51
93
Budapest, Hungary
We have been doing our daily vzdump backups to a shared NFS folder. Since updating to the new PVE packages yesterday, our Proxmox servers can't reach the NFS share.

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.

[6673]ERR: 24: Error in Perl code: command '/bin/mount -t nfs 10.10.10.20:/z/backup/nfs/daily /mnt/pve/backup-daily' failed with exit code 32

Apache Embperl 2.2.0 [Fri Jan 27 14:29:51 2012]
Click to expand...

I am also unable to create a new storage (Add NFS share), scanning the IP gives the following error:

Error: command '/sbin/showmount --no-headers --exports 10.10.10.20' failed with exit code 1
Click to expand...

Server version as follows:

Code: 
proxmox:~# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
 
Well, deleting and recreating the cluster and all defined storages and backups helped.
Looks like these configuration files can get messed up if the cluster gets updated.

Case closed.
 
I don't know what I'm talking about, I was simply guessing.

We still have a third Proxmox server that is unable to connect to or browse NFS shares, since it's installation (it's under Hyper-V).
Any idea how to check why it's not working with NFS?
 
You must log in or register to reply here.
Top Bottom