Troubleshooting; Recovering From An Installation Failure; Collecting Trace Directories - HP Integrity Superdome 2 16-socket User Manual

5 Troubleshooting

Recovering from an installation failure

Collecting trace directories

HP SUM generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows
systems. These files contain internal process and debug information, which can be useful in
determining HP SUM failures.
The debug trace files can be located under %temp%\hp_sum for windows. The log files can be
located under C:\cpqsystem\hp\log. These files provide the following information and are
appended in each HP SUM session.
HP SUM has a utility named GatherLogs.exe (Windows) or GatherLogs.sh (Linux) to create a
compressed file (Windows: .zip; Linux: tar.Z) with all the logs. If you need to review the log files,
you can run this utility to gather all the logs in one file.
NOTE: Exit HP SUM before running the GatherLogs utility.
Debug Trace Files
Opman.trace
InventoryResults.xml
Settings.xml
SourceClient.trace
Hpsumiserver\Hpsumiserver.log
Hpsumiserver\HpsumserverW32.log
Hpsumiserver\localhpsumsoapserver.log
Sesssion.log
RepositoryManager
<target>\Discoverymanager.log
<target>\Installmanager.log
<target>\<target name>_log.txt
<target>\Settings.xml
Function
Contains operations manager trace data of the overall
installation process, details of repository/ components
added/removed and general errors if any.
Contains details of the component inventory from the
repositories.
Includes general settings information of HP SUM such as
Force downgrade or upgrade.
Includes trace data of repository manager and general
errors if any.
Contains trace data for HP SUM SOAP server sessions.
Contains information of the HP SUM SOAP server.
Contains the data and time for each session has started.
This file is saved in separate directory named with the date.
Provides the repository and component information This
directory can be excluded in the trace data when collecting
the trace files.
Provides the details of interaction between the Operations
Manager and the remote discovery client. If a discovery
tool fails, it is reported to this trace file and surfaced as a
Discovery Failed message. This log is target specific.
Provides the interaction between the Operations Manager
and the remote discovery client. If a discovery tool fails, it
is reported to this trace file and surfaced as a Discovery
Failed message. This log is target specific.
Provides the trace data from operations manager for
specific target.
Provides general settings information of HP SUM such as
Force downgrade or upgrade for specific target.
Recovering from an installation failure 59