HP Serveur lame HP ProLiant BL465c Gen8 - Manual (Page 520)

Investigating standard output logs
When execution of a Application Agent results in some problem, investigate the information in the
standard output logs. If a problem occurs, the time when the problem occurred and the messages that
were displayed in the standard output are recorded in the standard output logs.
Refer to the contents of the standard output log, and check what messages were output when the
problem occurred. For details on how to respond to each message, contact your HP support
representative for assistance.
Investigating the trace logs for Application Agent-cooperative software
When the cause of a problem cannot be solved even if you have investigated the messages in the
standard output log, or when a problem is not eliminated even if you have carried out the recommended
action, then investigate the information in the trace log of the software that cooperates with Application
Agent (referred to as Application Agent-cooperative software).
Application Agent functions by cooperating with various products: such as a logic volume manager,
a backup manager product, and RAID Manager. The execution results of such Application
Agent-cooperative software are recorded in trace logs. The trace log files that record the execution
results of Application Agent-cooperative software are as follows:
• Trace logs related to disk operations
The execution results when controlling RAID Manager and a logic volume manager are output to
trace logs related to disk operations. When you investigate trace logs related to disk operations
and a problem with the RAID Manager is found, examine the detailed trace log provided by the
RAID Manager and handle the problem according to the contents of the log.
• Trace logs of NetBackup
The execution results when controlling NetBackup are output to a NetBackup trace log. When
you investigate a NetBackup trace log and a problem with NetBackup is found, handle the
problem by using the NetBackup GUI or by referring to the detailed trace log provided by Net-
Backup.
Investigating the detailed trace log
When a problem is not solved, even after you have investigated the standard output log and the trace
log files of the software linking with Application Agent, investigate the Application Agent detailed
trace log.
The following information is output to the detailed trace log:
• Internal functions that were used from the execution of a command to the end, as shown in the
internal processing sequence information
• The time and the command execution process ID for the processing that was performed at the
system call level
• Keywords showing normal and abnormal processing
• Messages showing error causes
The keyword ER showing an abnormality is output to the log record that the problem generated. In
the case of OS system-call abnormalities, the system also outputs the returned value in addition to the
keyword. The error causes are output in a message.
Troubleshooting 520