Data required for troubleshooting, Os log information, Data – HP Serveur lame HP ProLiant BL465c Gen8 User Manual
Page 512: Required for troubleshooting, Data required for, Troubleshooting
2.
Check the problem in the Application Agent log file.
When an error occurs in a Application Agent command executed within an extended command,
an error message is output to the Application Agent log file
drm_output.log
(or
drm_output.log.old
). See the content of the Application Agent log file regarding the time
when the error message for the extended command was output, and check the message and the
operation status from the time the problem with the Application Agent command occurred.
3.
Check the OS log file.
If no error message was output to
drm_output.log
(or
drm_output.log.old
), see the OS
log file, and then check the operating status that existed at the time when the problem occurred.
Data required for troubleshooting
This section describes the data that needs to be collected to determine the cause of a problem. For
details about how to collect Application Agent maintenance information, see the HP P9000 Replication
Manager Software Configuration Guide.
Data required for troubleshooting
OS log information
Collect the OS log information shown in the following table.
Table 105 OS log information
Default file name
Summary
Information type
--
Windows event log
#1
System log
system-directory
\system32\drivers\etc\hosts
hosts
file
System files
system-directory
\system32\drivers\etc\services
services
file
--
Windows system inform-
ation
--
•
Names of the OS
and installed product
•
Version information
•
Patch information
Information about the
OS and installed
product
--
Environment variable
Environment setting
information
Windows Server 2003
system-drive
\Documents and Settings\
user-name
#3
\
Local Settings\Application Data\Microsoft\
Dr Watson\drwtsn32.log
Dr. Watson
log file
#2
Dump information
Windows Server 2003
system-drive
\Documents and Settings\
user-name
#3
\
Local Settings\Application Data\Microsoft\
Dr Watson\user.dmp
Memory dump
#4
Troubleshooting
512