Baseline troubleshooting, Hp sum 6.0.0 and later trace directories – HP Smart Update Manager User Manual

Page 100

Advertising
background image

Function

Debug Trace Files

<target>

is the name of the target in the source selections

screen.

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

<target>\Settings.xml

Function

Log Files

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

<target>\hpsum_log.txt

<target>

is the name of the target in the source selections

screen.

Contains the log data of the components.

Hpsum_detail_log.txt

Stores persistent data on the user's system.

hpsum.ini

HP SUM 6.0.0 and later 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:

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.

Baseline troubleshooting

HP SUM lists SUSE Enterprise Linux dependencies for Red Hat Enterprise Linux systems

Solution: No action to take. HP SUM incorrectly lists the SUSE components. HP SUM will install
the Red Hat components.

HP SUM displays two versions of the same component when creating a custom
baseline

Solution: Multiple instances of the same component can be seen when creating a custom baseline
because the same component exists in the multiple baselines that were selected to be included in
the custom baseline. When you create a custom baseline, make sure you only select one version
of a component if it is included in multiple source baselines.

100 Troubleshooting

Advertising