HP Serviceguard Version A.11.18 Release Notes, September 2008

Resolution: The select()system call is now retried a maximum of ten times when it
fails because of an interrupted system call.
JAGag25508 (SR8606470417): Log file permissions set to 666
Problem: Permissions for log files defined in /etc/cmcluster.conf were set to 666
(allowing anyone to read or write to the file).
Resolution: These permissions are now set to 644, restricting writes to the owner of the
file.
JAGag35297 (SR8606481305): cfsmount failed since the package was already started
by cmcld
• Problem: This affected the CFS mount point package. If the package was already
down on all nodes when you ran the cfsmount command, cfsmount could fail,
complaining the package had already been started.
• Resolution: If cfsmount finds any package whose per-node state is blocked, it
will run cmhaltpkg -n to clear the state to halted, then run cmmodpkg to allow
cmrunpkg to bring up the package.
JAGag41937 (SR8606489376): Hanging node problem causing 2 out of 4 nodes to
die
• Problem: If a node experienced multiple hangs during cluster reformation, this
could cause two nodes to fail: the node experiencing the hang and the node that
was the candidate for cluster coordinator.
• Resolution: The code has been modified so that the cluster coordinator does not
fail.
JAGag48756 (SR8606496838): Serviceguard minimum lan requirements not updated
for VM detection information
• Problem: When a cluster uses virtual machine guests as nodes, the following warning
may appear during the network validation phase of the Serviceguard commands
cmapplyconf, cmcheckconf and cmquerycl:
Minimum network configuration requirements for the cluster have not been met. Minimum network
configuration requirements are:
- 2 or more heartbeat networks OR
- 1 heartbeat network with local switch (HP-UX Only) OR
- 1 heartbeat network using APA with 2 trunk members (HP-UX Only) OR
- 1 heartbeat network using bonding (mode 1) with 2 slaves (Linux Only).
The warning really means that the minimum requirements are not met at the
immediate network level. If you see this warning, you need to make sure that the
minimum requirements are met in your overall network configuration.
• Resolution: You can ignore the warning in a VM configuration if there is one
heartbeat network on the guest, backed by a network on the host using APA with
two trunk members as in the third case listed in the warning text (HPVM), or using
80 Serviceguard Version A.11.18 Release Notes