Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254
Same problem here. However, mine is on the client side.
On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1.
When I mount my NFS server 192.168.120.254, it works. However, if I want
to use some tool which need to lock file to save the file on the NFS
server, e.g.
vgcfgbackup -f $NFS_MNT_POINT/vg.cfg
I get the message "lockd: cannot monitor 192.168.120.254", and the
message shown on the /var/log/daemon.log:
May 21 08:52:44 debian rpc.statd[1298]: STAT_FAIL to debian for SM_MON
of 192.168.120.254
May 21 08:52:44 debian rpc.statd[1298]: No canonical hostname found for
192.168.120.254
I have to put a lookup setting in /etc/hosts, something like
192.168.120.254 nfs-server
then the command vgcfgbackup can successfully save the file on the NFS dir.
This bug is really annoying especially in the private IP addresses
environment. It's really a pain to put all the possible machines on the
/etc/hosts.
Please consider this as a serious issue, because it will cause a lot of
NFS-based computing clusters fail.
My 2 cents.
Steven.
--
Steven Shiau<steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A
Reply to: