A Troubleshooting

For information regarding system recovery troubleshooting, see “System recovery questions and answers” (page 221).

Also, see the Ignite-UX Frequently Asked Questions manual, available at http://www.hp.com/go/ ignite-ux-docs.

Errors and warnings

During an HP-UX installation, messages indicating the status of tasks are written to the client log file and either the log viewer (Ignite-UX server GUI-based installation) or the console (client UI-based installation). Some of these messages may be ERROR or WARNING messages, which have the following significance:

ERROR This indicates a serious problem, usually requiring action from you in order to proceed with an installation.

WARNING This indicates something out of the ordinary, but not fatal. The warning may require action.

If you encounter a message or experience unusual behavior, you can use the following sections as prioritized lists of likely problems and their solutions.

Ignite-UX server problems

Mixed Versions of Ignite-UX

Cannot find /d_cfg_mnt_sb61/monitor_bpr after updating the server.

This is caused by having a mix of Ignite-UX fileset versions on your server. In most cases it happens when you update only one release bundle even though you install other releases from that server.

An easy way to check for this case is to look at the output from the command:

swlist Ignite-UX

All the filesets must have the same version; if not, then you need to install all consistent versions. If you have boot helper systems (see “Ignite-UXbootp boot helper” (page 56)), they also need to have the Ignite-UX product updated to match the same version as the server that they reference. For information about the supported versions, see Ignite-UX Supported Versions for HP-UX 11i:

http://www.hp.com/go/ignite-ux-docs

Installing systems with Ignite-UX

Numerous samreg errors

Installing from an image returns numerous samreg errors.

The problem is that the SAM filesets have not been configured when certain products are trying to register themselves with SAM.

The work-around is to place the following configuration clause in /var/opt/ignite/ config.local or in the configuration file that contains the sw_source clause of the core operating system.

sw_source "core"

{

post_load_cmd += "swconfig -xautoselect_dependencies=false

-xenforce_dependencies=false SystemAdmin.SAM -xreconfigure=true"

}

NOTE: Due to formatting limitations, unintended line wraps exist in the previous example; the post_load_cmd line must not wrap in your configuration file. You verify the syntax with the instl_adm -Tcommand.

228 Troubleshooting