Collecting trace directories

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: ]

NOTE: Exit HP SUM before running the GatherLogs utility.


The following are the debug files for HP SUM 5.x.

Debug Trace Files

Function

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 each session started. This file is saved in a 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 a 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 a specific target.

Log Files

Function

<target>\hpsum_log.txt

Contains information of HP SUM discovery, installation status and errors if any.

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

Hpsum_detail_log.txt

Contains the log data of the components.

hpsum.ini

Stores persistent data on the user's system.

HP SUM 6.0.0 trace directories

In HP SUM 6.x, trace directories are stored in the /tmp/HPSUM (Linux) and %temp%\HPSUM (Windows) directories. HP SUM creates trace directories for each function and node that HP SUM updates.

If you are running HP SUM in offline mode, use the following instructions to collect trace directories and logs.

  1. Launch HP SUM in offline mode.

  2. Launch the command prompt from the HP SUM GUI by pressing CTRL+ALT+D+B+X.


    [NOTE: ]

    NOTE: After approximately 30 seconds, the command prompt appears over the HP SUM GUI window.


  3. Change the directory to the one running HP SUM. For example, cd /mnt/bootdevice/SPP2012060B/hp/swpackages.

  4. Type ./gatherlogs.sh to collect the HP SUM logs. All logs are collected in a .tar.gz file in the directory where you placed HP SUM or in a temp directory if the HP SUM directory is read-only. The log file is named HPSUM_Logs_$(datetime).tar.

  5. Place the logs on a removable media if you want to view them on another computer.