HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

QXCR1000766057: cmviewcl package state “blocked” is not documented
• What is the problem? cmviewcl shows the per-node state of multi-node packages
as blocked, but the manpage does not explain what “blocked” means.
• What is the workaround? “Blocked” means that the multi-node package has never
run on the node. This may be because a dependency has not been met, or auto_run
is set to no.
Dependencies are configured in the package configuration file; see Chapter 6 of
Managing Serviceguard for Linux for more information.
QXCR1000766101: cmhaltpkg reports that auto_run is disabled for multi-node packages
but it is not
• What is the problem? When you use cmhaltpkg to halt packages, cmhaltpkg
prints the following message:
One or more packages or package instances have been halted.
These packages have AUTO_RUN disabled and no new instance
can start automatically. To allow automatic start, enable
AUTO_RUN via cmmodpkg -e <package_name>
This is true of the failover packages on the command list but not true of the
multi-node packages.
• What is the workaround? No action is required; cmhaltpkg does not disable auto_run
for the multi-node packages, which is the correct behavior.
QXCR1000771266: Cluster Create: ASCII files are not distributed if cluster name contains
$
• What is the problem? If you create a cluster with a name containing the $ sign, the
cluster configuration file will not be distributed to the cluster nodes. The operation
log will indicate that the command that distributes the newly created cluster
configuration file failed to do so. But the cluster will be created properly and will
function normally.
• What is the workaround? Preferably, do not create a cluster name that includes a $
sign. But if you have done so, and cannot easily change it, you can produce a cluster
configuration file using the cmgetconf command, and then copy it manually to
each node.
Known Problems and Workarounds for Serviceguard Manager
This section describes known problems and provides workarounds for Serviceguard
Manager version B.01.01.
Known Problems and Workarounds 85