HP Serviceguard Version A.11.18 Release Notes, September 2008

QXCR1000739586: Serviceguard does not log .cm_start_time message correctly in
syslog after abort
• Problem: If cmcld aborted and you restarted the cluster without first rebooting the
node on which the abort occurred, the following message appeared in syslog.log:
It appears that package applications or resources may be active on this node.
Re-starting the cluster could cause data corruption. To recover from this situation
reboot this system: After ensuring that no package applications or resources are
active, you can override this data. For CFS customers, it is highly recommended
that this node be rebooted.
This message is missing important information. It should say:
It appears that package applications or resources may be active on this node.Re-starting the
cluster could cause data corruption. To recover from this situation reboot this system:
shutdown -r (stops package components)
After ensuring that no package applications or resources are active, you can
override this data integrity protection by issuing the following commands (which
allow the daemon to start without rebooting):
rm /var/adm/cmcluster/.cm_start_time
touch /var/adm/cmcluster/.cm_start_time
For CFS customers, it is highly recommended that you reboot the node instead of
using the data override mechanism
• Resolution: The error message now includes the complete version of the directions
provided above.
QXCR1000740150: cmcld abort when deleting node online
• Problem: When you ran cmapplyconf to delete a node from the cluster
configuration while the cluster was running, cmcld aborted if the name of the
node cmapplyconf was run from was a subset of the name of the node being
deleted.
For example, if you ran cmapplyconf from node1 to delete node10, cmcld
aborted with the following message in syslog.log:
cmcld: Aborting! Deleting local node that is online
(file: rcomm/comm_config.c, line: 583)
The cluster daemon aborted our connection (231).
cmapplyconf: Unable to apply the configuration
• Resolution: The code has been modified to prevent this problem.
QXCR1000740395: Should display warnings about subnets only for related packages
• Problem: cmapplyconf and cmdeleteconf issue a warning if a monitored_subnet
configured for a package is not available on all nodes in a cluster. (The configuration
may be correct if this is a cross-subnet configuration; see “About Cross-Subnet
Configurations” (page 40).) The problem was that this warning was given for all
82 Serviceguard Version A.11.18 Release Notes