NFS Problem

[Brian Lee]

I have NFS problem.
when I type dmesg on my server.
It comes up like followings:

NFS lookup failed for server slauxpd: RPC: Timed out
NFS create failed for server slauxpd: RPC: Timed out

Please help me.

[Thayanidhi]

Please elabrate the problem. dmesg from NFS client or server? Are you able to ping or telnet NFS server? Can you check whether NFS processes are running in the server and NFS client enabled.. etc?

Are you able use any rlogin/rwho/ruptime ...etc(this is to check RPC)

[Jeff Schussele]

Hi Changwoo,

The server, slauxpd, Is NOT in DNS. Verify that with

nslookup slauxpd

If that's the case you need to get thde DNS adnins to get it into the DNS DB...or correct the NFS import to the proper server name...if it's a typo.
Sounds like NFS is trying to mount something from that server.

Rgds,
Jeff

[sven verhaegen]

Hi

These are informative error messages from NFS , they should not be taken lightly but could also only be information , it all depend on the fact of you having real issues with the NFS mountpoints or only seeing the error from time to time in the logs :

the exact meaning is that the client tried to reach the server with the name "slauxpd" , it requested first a lookup of the properties of some files or directories and it also tried to create a file on the filesystem

the RPC deamon on the server didn't reply for that specific request , several reasons can be the cause of this , a DNS issue could be but is not necessary the cause ... "lookup" doesn't relate to nslookup it relates to the lookup for the file or directory properties on the nfs mountpoint itself (NFS needs it to see the user rights and the file access parameters)

some action-points :

first look if the server hostname indeed has an IP attached to it with nslookup on the client , on the server check if it can find the client IP

if so ping the ip of the server from the cleint and the ip of the cleint from the server

if that works , look if NFSD is still active on the server or and if RPC still is functioning (use rpcinfo)

look on the server syslog for possible error messages ...

the error can result from a high load of the server because not enough nfsd are present , you could set that higher by setting the NUM_NFSD parameter in /etc/rc.config.d/nfsconf file to 16 or 32

also a network issue (network latency or packet loss) can cause the request to timeout and fail generating this error , a retry of the NFS should solve that , do you see any problems with the mount e.g. is it slow or not responding at all (hang) , the messages could just arrive because the server was busy or the network loaded but NFS managed to solve it by resending the request