Open System Services NFS Management and Operations Guide

8 Troubleshooting
This chapter gives an overview of OSS NFS troubleshooting.
When troubleshooting an OSS NFS problem, note these three main points of failure in network
services:
• The server
• The network itself
• The client
Troubleshooting Quickstart
Table 2 lists procedures to try when troubleshooting the OSS NFS subsystem. The remainder of
the chapter provides an overview of the points where failures can happen, suggests troubleshooting
actions for each point, and indicates the tools available for troubleshooting.
Table 2 Quickstart for Troubleshooting OSS NFS
Recommended ProcedureSymptom
Client cannot mount OSS NFS
fileset because of a permission
error
1. Make sure the PCNFSD process is running if the client is a PC or Apple Macintosh
computer. If PCNFSD is not running, run the NFSSTOP and NFSCOLD files to ensure
that it restarts. Do not purge the user database.
If PCNFSD fails to start, check the port mapper process:
• Run NFSSTOP.
• Ensure that the $ZPM* portmapper process is stopped.
• Run NFSCOLD again.
2. Check the setting of the NULL-ALIAS-OK attribute in the server:
• If that attribute is FALSE, all users need to be defined in the OSS NFS user
database and must have a valid user ID alias to access files in a PASSTHRU
server.
• If that attribute is TRUE and the client is having problems with NFS, check that
the nobody user ID is defined and has a valid user ID alias.
3. Check the setting of the ROOT-USER-OK attribute in the server. If it is FALSE:
• Verify that the client is not logged on as root for OSS NFS.
• Verify that the user ID alias for OSS NFS is not 255,255.
4. Check the READ-ONLY attribute in the server configuration.
• If that attribute is TRUE, make sure the client is not trying to mount a fileset for
read-write access.
• If that attribute is FALSE, check the read-only access flag for the fileset in the
OSS fileset configuration (use the SCF INFO FILESET, DETAIL command).
5. Check the ADDR-CHECK attribute in the LAN interface process. If that attribute is
TRUE:
• Make sure the client machine name and IP address are defined in the host file
or in the Domain Name Server (DNS).
• Verify that the TCPIP-HOST-FILE or TCPIP-RESOLVER-NAME attribute is correctly
configured.
• Check the NonStop TCP/IP search path used in resolving host names.
• Verify that the fileset is exported.
Client can access the OSS NFS
server only as the nobody
public user
1. Verify that the PCNFSD process is running; run rpcinfo from the client.
2. Verify that the user is defined in the OSS NFS user database. If the user is defined,
make sure it has a valid user ID alias.
3. Verify that the password supplied to PCNFSD is correct; log on in TACL using the
user ID alias and the password.
72 Troubleshooting