HP CIFS Client A.02.02.03 Administrator's Guide

6 Troubleshooting and Error Messages
This chapter includes information about problems that you may encounter when using the HP CIFS
client and explanations of error messages that might occur with HP CIFS commands.
“Troubleshooting FAQs” (page 44).
“Troubleshooting Kerberos in the HP CIFS Client” (page 44).
“Troubleshooting cifsmount or mount in the HP CIFS Client” (page 45).
“CIFS Client Log File and Log Levels” (page 46).
Troubleshooting FAQs
This section includes commonly asked questions about HP CIFS.
How to Shutdown the Daemon with cifsclient stop
You should never kill the daemon process directly. Although HP CIFS tries to unmount all mounted
shares, it may not be successful and the stale mounts will become unusable and cause problems.
The correct way to do it is with cifsclient stop.
Refer to "Step 4, Starting and Stopping the Client" in chapter 2 in this manual for more detailed
information about cifsclient stop.
What to Do if the Daemon Terminates
If the daemon terminates, all shares served by HP CIFS will immediately become unusable. Every
access will hang until the NFS timeout (configured in the configuration file) elapses. You can
probably get away without rebooting if you immediately terminate all processes using the mounts,
change all current directories from within the mounts and then use the cifsclient force_umount
<mountpoint> command to unmount the stale mounts. Report the event to HP Technical Support
and describe how the problem can be reproduced.
Troubleshooting Kerberos in the HP CIFS Client
cifsTrace, authentication log levels
Informative log messages will be produced by Kerberos processing in the HP CIFS Client log
file if the cifsTrace and authentication log levels are enabled.
Temporary credentials files
When Kerberos authentication is used, the HP CIFS Client utilizes a temporary file to store
users' credentials during login processing. There is one temporary credentials file per user
per server. Kerberos tickets are not reused by the HP CIFS Client. Hence, when the user's login
processing is completed, the temporary file is removed.
For troubleshooting, the temporary credential files can be preserved by setting the configuration
variable rmTempKerbCredFiles to no. You can then examine and remove the files with
the standard Kerberos Client utilities, klist(1) and kdestroy(1). Use the -c cache_filename option
with these commands, specifying filenames in the followng form:
/var/opt/cifsclient/krb5_tmp/krb5cc_servername_uid
where servername is the CIFS server and uid is the user's Unix uid on the local HP-UX host on
which the CIFS Client is running.
As a convenience, the cifsclient control script can also be used to operate on these
credentials files without referring to file or path names. Enter cifsclient -h for a syntax
summary.
44 Troubleshooting and Error Messages