HP-UX Containers (SRP) A.03.01 Administrator's Guide

• If neither global_srp nor local_srp_list options are specified, then the install,

remove, or configure will occur on the system and all system containers.

• If the global_srp=true and local_srp_list options are not specified, then the install,

remove, or configure will occur only on the system.

• If the global_srp=true and local_srp_list options are set, then the install, remove,

configure will occur on the system and the listed system containers.

• If the local_srp_list option is set and the global_srp option is not specified, then the

install, remove, configure will occur only in the listed system containers.

You can use these new options to recover a container after software installation failure (see 15.5.5

Recovering unsynchronized containers) or when installing/removing a product from the global view

that is not part of the system containers.

For example, when removing a product from the global view that is not in the HP-UX Containers

allowed product list (therefore, it is not installed in system containers), it would be quicker to target

just the global, as follows:

# swremove -x global_srp=true PRODUCT

When installing a product that is not in the HP-UX Containers allowed product list (and that does not

require a reboot), you can avoid having to stop the shared subtype containers by targeting just the

global, as follows:

# swinstall -x global_srp=true -s /tmp/product.depot PRODUCT

15.5.5 Recovering unsynchronized containers

If a software maintenance operation fails in the global view, check the swagent log file

/var/adm/sw/swagent.log to identify the problem, take corrective action and repeat the

operation.

If a software maintenance operation succeeds in the global view but fails in one or more containers

then the SD operation will display errors indicating the containers that are out of sync with the global

view.

For example, if the installation of the product MY_PRODUCT succeeds in global view but fails in

container_A, then swinstall will display the following error:

# swinstall -s /tmp/myproduct_version_2.depot MY_PRODUCT

Scanning the products in "container_A" please be patient....

The SRP product 'MY_PRODUCT' does not match global's version

SRP has version 'A.01.00' Global has version 'A.02.00'

As the message indicates, the system container still has version 1 of the product, but the global view

now has version 2 installed.

If the container file system subtype is shared, then the container cannot be started until the software in

the container matches the software in the global view. If the file system subtype is private then the

container can be started but depending on the type of the update (see 15.5.6 Advanced installation:

varying software versions) the container software must be kept in sync with the global view.

To take corrective actions:

1. Check the /var/adm/sw/swagent.log file in the container to identify the problem. Either

follow the ROOTPATH of the container, or enter the container by changing its state to