Serviceguard Version A.11.16 Release Notes, 2nd Edition, September 2004

Serviceguard Version A.11.16 Release Notes, Second Edition
Patches and Fixes in this Version
Chapter 1 39
memory, fills in the required information and sends it back to the
command. Later it is supposed to free up the memory that was
created. In this case, freeing of the memory is not done.
• What was the resolution? The fix is to free up the memory, if it was
created successfully.
JAGaf03966 2 node cluster with no QS or quorum server:
• What is the problem? cmapplyconf does not properly check for
adding cluster lock while the cluster is running.
• What is the workaround? Modified the cmapplyconf code to properly
check and not allow addition of a cluster lock while the cluster is
running.
JAGaf03957 Control script executing cmhaltpkg command fails
• What was the problem? In this case the cmhaltpkg command was in
progress while waiting for the package control script to finish. If
reconfiguration happens during that time, the command does not
know if the halt of the control script was successful or not. The retry
to learn the status might have found that the package is not running
even though it might have halted successfully. So the command exits
with an error.
• What was the resolution? As this is a race condition and multiple
things are happening at a particular time, the error cannot be
avoided in all cases. So a clearer message is displayed if this
condition is encountered.
JAGaf01415: SG 11.15 cmclconfd reduces RLIMIT_NOFILE,
preventing application startup
• What was the problem? The cmclconfd and cmcld daemon
recalculates the number of file descriptors for its own environment
and sets its value in the system (currently 1024 set by cmclconfd).
The same value gets passed to cmcld and from cmcld to the
applications starting from Serviceguard, thus creating a problem.
(See JAGae94512: SG 11.15 reduces the RLIMIT_NOFILE causing
applications to fail to start)