HP Smart Update Manager (User Guide) - Manual (Page 63)

Troubleshooting 63
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
Smart Update Manager 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.
Debug Trace Files Function
Opman.trace Provides operations manager trace data of the overall installation process, details of
repository/ components added/removed and general errors if any.
InventoryResults.xml Provides details of the component inventory from the repositories.
Settings.xml Provides general settings information of HP SUM such as Force downgrade or
upgrade.
SourceClient.trace Provides trace data of repository manager and general errors if any.
Hpsumiserver\Hpsumis
erver.log
This log contains trace data for HP SUM SOAP server sessions.
Hpsumiserver\Hpsumse
rverW32.log
Hpsumiserver\localhps
umsoapserver.log Contains information of the HP SUM SOAP server.
Sesssion.log This log contains the data and time for each session has started. This file is saved in
separate directory named with the date.
RepositoryManager This directory provides the repository and component information This directory can be
excluded in the trace data when collecting the trace files.
\Discoveryma
nager.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.
\Installmanage
r.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.
\
name>_log.txt
Provides the trace data from operations manager for specific target.
\Settings.xml Provides general settings information of HP SUM such as Force downgrade or upgrade
for specific target.
Log Files Function
\hpsum_log.txt
Note: is the
name of the target in the
source selections
This log contains information of HP SUM discovery, installation status and errors if any.