NFS Performance Tuning for HP-UX 11.0 and 11i Systems

nfs performance tuning for hp-ux 11.0 and 11i systems page 75

Notes:

Page 75July 22, 2002

Troubleshooting Automount & AutoFS

• Collect a debug Automount or AutoFS logfile

• Verify that hostname resolution servers (i.e. DNS,

NIS, etc.) are responding and return accurate data

• Collect a network trace to verify that mount requests

are traversing the network

• TOC the client and analyze the dump with Q4

automount

autofs

Among the best sources of information for troubleshooting automount and AutoFS

problems is a debug logfiles collected while reproducing the problem. Debug

logging can be toggled on and off by sending the SIGUSR2 signal to the running

“automount” (legacy automounter) or “automountd” (AutoFS) process (i.e. kill –17

<pid>). By default, the debug information is logged to the

/var/adm/automount.log file.

In some cases, a network trace is also needed to fully understand the root cause of

an automount problem. The trace can be used to determine whether the mount

requests and replies are traversing the network successfully.

Since AutoFS is a multi-threaded process and spends much of its time in the kernel,

in some cases a TOC dump must be collected and analyzed with Q4 in order to

determine why AutoFS is misbehaving.