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 140
• What was the resolution? Even if cmclconfd & cmcld daemon
recalculates and sets new file descriptors limit, the original value
will be restored for child processes so that they will have the original
system limit.
JAGae98584 local lan failover problems when a single network
switch fails
• What was the problem? Because of a logic error and a time-sensitive
issue, only stationary IP address(es) were switched to the second
standby interface while the relocatable IP address(es) remained in
the primary interface after the shared network switch was powered
down.
• What was the resolution? The logic error has been fixed so that
Serviceguard will allow all IP address(es) to switch to the second
standby properly.
JAGae94575 AUTO_START_TIMEOUT ignored by cmcluster RC
script
• What was the problem? AUTO_START_TIMEOUT ignored by
cmcluster RC script. The /sbin/init.d/cmcluster script has a
hard-coded timeout of 600 seconds.
• What was the resolution? The script was modified to get timeout
value from CDB via cmviewconf. The AUTO_START_TIMEOUT will
be honored even when a node is powered down.
JAGae94512: SG 11.15 reduces the RLIMIT_NOFILE causing
applications to fail to start
• 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 JAGaf01415: SG 11.15 cmclconfd reduces RLIMIT_NOFILE
preventing application startup)
• What was the resolution? Even if cmclconfd & cmcld daemon
recalculates and sets new file descriptors limit, the original value
will be restored for child processes so that they will have the original
system limit.