lockd: cannot monitor 192.168.0.31

Hi Everyone,

I keep seeing this error ever 5 mintues on the console of one of my
NFS clients..

Sep 20 13:40:00 mailclone1 kernel: lockd: cannot monitor 192.168.0.3
Sep 20 13:45:00 mailclone1 kernel: lockd: cannot monitor 192.168.0.3
Sep 20 13:50:01 mailclone1 kernel: lockd: cannot monitor 192.168.0.3

I'm running RedHat 7.3 with kernel 2.4.18-10 on both the client and
server. I'm using nfs-utils-0.3.3-5.

I've done some digging and have found quite a few references about
this same problem. However, all of the suggested solutions don't seem to apply to me.

One suggestion was to make sure statd/lockd are running on the
client. They are, and they are also running on the server.

Another was to check permissions of /var/lib/nfs/statd. The
directory is mode 0700 owned by rpcuser.rpcuser, which is the user that rpc.statd is running as.

As far as I can tell everything is working fine with regards to the
NFS mounts. The clients mount them no problem, and have no trouble reading or writing to them. I'm just trying to figure out the cause of these error's before I move these boxes into production. I don't want to leave any loose ends untied.

Any help is greatly appreciated.

Thanks,

John

John Doshier
Unix Systems Administrator
Inter7 Internet Technologies, INC.
(p) 847.492.0470 (f) 847.492.0632
http://www.inter7.com/main.html




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs