HP Smart Update Manager - Manual (Page 99)

6 Troubleshooting
Collecting trace directories
If you need to contact HP for support with an issue, run the GatherLogs utility. GatherLogs is
in the same directory as HP SUM.
In HP SUM 5.x, HP SUM generates a set of debug trace logs located in the %TEMP%\HPSUM
directory on Windows systems. These files contain internal process and debug information which
can be useful in determining HP SUM failures. In HP SUM 6.x, the files are stored in the %temp%\HP
SUM for 6.x
directory.
In HP SUM 5.x, 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.bat (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: Exit HP SUM before running the GatherLogs utility.
The following are the debug files for HP SUM 5.x.
Function Debug Trace Files
Contains details of the component inventory from the
repositories. InventoryResults.xml
Includes general settings information of HP SUM such as
Force downgrade or upgrade. Settings.xml
Includes trace data of repository manager and general
errors if any. SourceClient.trace
Contains trace data for HP SUM SOAP server sessions. Hpsumiserver\Hpsumiserver.log
Contains remote trace data for HP SUM SOAP server
sessions. Hpsumiserver\HpsumserverW32.log
Contains information of the HP SUM SOAP server. Hpsumiserver\localhpsumsoapserver.log
Contains the data and time each session started. This file
is saved in a separate directory named with the date. Sesssion.log
Provides the repository and component information. This
directory can be excluded in the trace data when collecting
the trace files. RepositoryManager
Provides the details of interaction between the Operations
Manager and the remote discovery client. If a discovery <target>\Discoverymanager.log
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 <target>\Installmanager.log
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 a
specific target. <target>\<target name>_log.txt
Collecting trace directories 99