RHBA-2004:491 - Bug Fix Advisory
Updated clumanager and redhat-config-cluster packages
Bug Fix Advisory
Updated Red Hat Cluster Manager (clumanager, redhat-config-cluster)
packages that fix various bugs and provide a few enhancements are now
available for Red Hat Cluster Suite on Red Hat Enterprise Linux 3.
Red Hat Cluster Manager provides high availability of critical server
applications in the event of planned or unplanned system downtime.
Various bugs in Red Hat Cluster Manager have been discovered and addressed
since the release of Red Hat Enterprise Linux 3, including:
- Stale NFS file handles on service restart or relocate in certain
- Localization fixes in redhat-config-cluster
- Clumembd/cluquorumd hangs if a timeout is encountered
- Heartbeat sends from the wrong IP address if an alias is configured on a
bonded ethernet device
- Formation of quorum not occurring after network connectivity is restored
to a member which started with none, and an IP tiebreaker was in use with
soft quorum enabled
- During force unmount, clumanager was using both lsof and fuser
- Sparse ID tags in /etc/cluster.xml break services
In addition, the following features have been implemented:
- Support for the APC MasterSwitch 7900 power switch
- Option to restrict use of NICs for broadcast heartbeats
- Maximum false starts or restarts prior to failover is implemented as a
- Store /etc/cluster.xml when "shutil -i" is run
- Ability to change the cluster's syslog facility using cludb
Users of Red Hat Cluster Manager are advised to upgrade to these updated
packages, which resolve these issues.
Performing a Cluster Upgrade
This erratum can be upgraded in a "rolling" fashion. That is, it is
possible to upgrade the cluster software without taking the entire cluster
offline at once. Due to a bugfix between 1.2.3 and 1.2.9, however, it is
necessary to upgrade the lowest-ordered member last. (If you are upgrading
from 1.2.9, you may upgrade the members in any order; the instructions
below assume you are running clumanager version 1.2.3.)
Notes (Before you begin):
- All cluster members must be running and participating in the cluster
quorum, or no members should be running at all.
- Is a good idea to perform this upgrade during scheduled maintenance
and/or when it will impact the fewest number of users.
Steps (with all cluster members running):
(1) Run the following:
# cludb -g members%member0%name
The host displayed is the lowest-ordered cluster member. This member must
be upgraded *last*.
If this member is "not found", look at /etc/cluster.xml. Look for the
"member" tag with the lowest "id" property; this is the lowest-ordered member.
Make a note of this member; this member must be upgraded last.
(2) Run 'rpm -Fvh [filenames]' (as noted above) on all cluster members
except the member noted in step (1), one at a time. Do not execute this
command on multiple members simultaneously, as the upgrade process disables
a member temporarily (removing it from the cluster quorum). If too many
members are disabled simultaneously, the cluster quorum will no longer
exist, forcing services managed by the cluster software to become
Services located on a member that is being upgraded will migrate to other
cluster members whenever possible.
(3) Run 'rpm -Uvh [filenames]' on the member noted in step (1).
(4) If desired, balance cluster services across available members using
redhat-config-cluster or clusvcadm.
(5) Run 'chkconfig --add clumanager' on all members.
Steps (No cluster members running the cluster software):
(1) Run 'service clumanager stop' on all members.
(2) Run 'rpm -Uvh [filenames]' on all members.
(3) Run 'chkconfig --add clumanager' on all members.
(4) Restart the cluster software on all members if desired.
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains
the desired RPMs.
Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
If up2date fails to connect to Red Hat Network due to SSL
Certificate Errors, you need to install a version of the
up2date client with an updated certificate. The latest version of
up2date is available from the Red Hat FTP site and may also be
downloaded directly from the RHN website:
- Red Hat Enterprise Linux High Availability (for RHEL Server) 3 x86_64
- Red Hat Enterprise Linux High Availability (for RHEL Server) 3 ia64
- Red Hat Enterprise Linux High Availability (for RHEL Server) 3 i386
- BZ - 114388 - Stale file handles under failover conditions
- BZ - 125741 - clumembd hanging when stopping clumanager
- BZ - 129710 - Heatbeat fails with multiple IP addresses on Ethernet device
- BZ - 129997 - wrong localization domain
- BZ - 130426 - clumanager doesn't recover from network disconnect /reconnect
- BZ - 131006 - RFE: Make a clumembd option to restrict cluster broadcast heartbeating to private NICs/loopback
- BZ - 131225 - can you change the cluster daemons\' logging facility?
- BZ - 131235 - clusvcadm -d <svcname> hangs forever when lsof for NFS filesystem hangs
- BZ - 131574 - Unclean shutdown can leave resources allocated
- BZ - 132591 - RFE: shutil -i stores /etc/cluster.xml automagically
- BZ - 133080 - Sparse ID tags in cluster.xml do not work
- BZ - 133285 - RFE: Support APC MasterSwitch 7900