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, that can be useful in determining HP SUM failures.

The debug trace files are located under %temp%\hp_sum for Windows. The log files are located under C:\cpqsystem\hp\log. These files provide the following information and are appended in each HP SUM session.

HP SUM 5.0.0 and later includes a utility named GatherLogs.exe (Windows) or gatherlogs.sh (Linux) to create a compressed .zip (Windows) or tar.Z (Linux) file 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]

NOTE: Exit HP SUM before running the GatherLogs utility.

Debug Trace Files

Function

Opman.trace

Contains operations manager trace data of the overall installation process, details of repository/components added/removed and general errors if any.

InventoryResults.xml

Contains details of the component inventory from the repositories.

Settings.xml

Includes general settings information of HP SUM such as Force downgrade or upgrade.

SourceClient.trace

Includes trace data of repository manager and general errors if any.

Hpsumiserver\Hpsumiserver.log

Contains trace data for HP SUM SOAP server sessions.

Hpsumiserver\HpsumserverW32.log

Contains remote trace data for HP SUM SOAP server sessions.

Hpsumiserver\localhpsumsoapserver.log

Contains information of the HP SUM SOAP server.

Sesssion.log

Contains the data and time for each session has started. This file is saved in separate directory named with the date.

RepositoryManager

Provides the repository and component information This directory can be excluded in the trace data when collecting the trace files.

<target>\Discoverymanager.log

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.

<target>\Installmanager.log

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.

<target>\<target name>_log.txt

Provides the trace data from operations manager for specific target.

<target> is the name of the target in the source selections screen.

<target>\Settings.xml

Provides general settings information of HP SUM such as Force downgrade or upgrade for specific target.

It is possible to look in the OpMan.trace file and see which components were winnowed from the installation set and which ones were added.