OSI Troubleshooting Guide, May 1997

Chapter 2 55
Problem Solving
Interpreting Errors
Interpreting Errors
This section describes where you should look to find more information
about an error you encountered. Table 2-1 gives the places where you
may encounter errors and how to interpret them.
Table 2-1 Interpreting Errors
Where Action
osidiag You will find a description of how to interpret errors at the end of
each section in Chapter 1, “Interoperability Testing,” on page 11.
nettl log files Many errors contain detailed text describing the problem. Some
common logged errors are described at the end of this chapter.
User applications Errors received in applications you write are passed back through
return codes. You may want to use the API tracing facility for the
interface. The nettl log file many also contain information. You
could also increase the logging level and reproduce the problem. See
“Tracing and Logging through /opt/ots/bin/osidiag” on page
62.
FTAM
Interactive
Commands
These errors are described in the HP FTAM/9000 User’s Guide and
the HP FTAM/9000 Reference Manual.
X.400 Commands Refer to the Managing X.400—Administrator’s Guide.
OSI/OTS
Administrative
Commands
These errors are produced from commands like otsstart and
osiconfchk. Descriptions of these errors can be found online. Also
look in the log files in /var/opt/ots.
System Panics Panics occur when an irrecoverable error is detected by the HP-UX
operating system. At reboot after a panic, a copy of the state of the
system will be saved by savecore. See
/etc/rc.config.d/savecore. You may need to create a special
directory for savecore to actually save the image to disk.
Interpreting panics is done by your HP support representative or the
factory.