NFS Services Administrator's Guide (B.11.31.03) August 2008
– status
– nlockmgr
On the NFS server, check if the following processes are running:
– nfsd
– rpc.mountd
– rpc.statd
– rpc.lockd
If any of these processes is not running, follow these steps:
1. Make sure the /etc/rc.config.d/nfsconf file on the NFS server contains
the following lines:
NFS_SERVER=1
START_MOUNTD=1
2. Enter the following command on the NFS server to start all the necessary NFS
processes:
/sbin/init.d/nfs.server start
□ Enter the following command on the NFS client to make sure the rpc.mountd
process on the NFS server is available and responding to RPC requests:
/usr/bin/rpcinfo -u servername mountd
If the rpcinfo command returns RPC_TIMED_OUT, the rpc.mountd process
may be hung. Enter the following commands on the NFS server to restart
rpc.mountd (PID is the process ID returned by the ps command) :
/usr/bin/ps -ef | /usr/bin/grep mountd
/usr/bin/kill PID/usr/sbin/rpc.mountd
□ You can receive “server not responding” messages when the server or
network is heavily loaded and the RPC requests are timing out.
NOTE: For TCP, the default timeout is 600 while for UDP, the default timeout
is 11.
Try doubling the timeo mount option for the directory, as in the following example
from the /etc/fstab file, which changes the timeo value from 600 (the default)
to 1200. (The timeo option is in tenths of a second.)
cabbage:/usr /usr nfs nosuid,timeo=1200 0 0
□ Enter the following command on the NFS client to check that your hosts database
returns the correct address for the NFS server:
/usr/bin/nslookup server_name
Enter the same nslookup command on the NFS server, and compare the address
with the one returned by the nslookup command on the NFS client. If they are
different, correct your NIS, BIND, or /etc/hosts configuration. For information
130 Troubleshooting NFS Services