NFS statd
Hi to all,
I have a very strange problem. My NFS server is FC3, my NFS client is RH9. On the client i get the log message:
kernel: lockd: cannot monitor <IP of the server>
kernel: lockd: failed to monitor <IP of the server>
after somne googling, I found that the problem was in rpc.statd that should be activated by nfslock startup script. nfslock is enabled (chkconfig shows it "on") and calls "rcp.statd". When I execute rcp.statd, it dies right away: it does not appear in ps.
I work on a cluster on which all the nodes have / mounted on NFS on onather server and they have write permissions only to /tmp /var and /etc but this should not be the problem since I do not get any permission denied error when I execute rpc.statd, even strace rpc.statd does not show any problems of permission.
On the server I get another message that may have something to do with the aforementionned issue:
Received erroneous SM_UNMON request from <name of the NFS server> for <name of the client>
the funny part is that the specific client that appears is this log message is a normal RH9 (/ is not mounted on NFS) and on this client rpc.statd runs...
do you have some ideas ?
thanks a lot !
|