Specifications
LifeKeeper Core
Description
Language Environment Effects
Some LifeKeeper scripts parse the output of Linux system utilities and rely on certain patterns in
order to extract information. When some of these commands run under non-English locales, the
expected patterns are altered, and LifeKeeper scripts fail to retrieve the needed information.For
this reason, the language environment variable LC_MESSAGES has been set to the POSIX “C”
locale (LC_MESSAGES=C) in/etc/default/LifeKeeper.It is not necessary to install Linux with the
language set to English (any language variant available with your installation media may be
chosen); the setting of LC_MESSAGES in/etc/default/LifeKeeperwill only influence LifeKeeper.
If you change the value of LC_MESSAGES in/etc/default/LifeKeeper, be aware that it may
adversely affect the way LifeKeeper operates. The side effects depend on whether or not message
catalogs are installed for various languages and utilities and if they produce text output that
LifeKeeper does not expect.
File system labels should not be used in large configurations
The use of file system labels can cause performance problems during boot-up with large clusters.
The problems are generally the result of the requirement that to use labels all devices connected to
a system must be scanned. For systems connected to a SAN, especially those with LifeKeeper
where accessing a device is blocked, this scanning can be very slow.
To avoid this performance problem on Red Hat systems, edit /etc/fstab and replace the labels with
the path names.
Cannot break reservation on QLogic driver (qla2xxx) running SUSE SLES 10
Failover does not work on a SUSE SLES 10 system using the QLogic driver (qla2xxxx). On x86
boxes running SLES 10 with the stock QLogic driver, a failover does not work since we cannot
break the reservation. It appears the qla2xxx driver delivered on SLES 10 will only issue a reset if
there is a hung IO. NOTE: The qla2xxx driver delivered on SLES 10 SP1 corrects the problem.
Syntax errors can occur with gen/app resources
When the steeleye-lkGUI package is upgraded without upgrading the core, a syntax error can
occur with gen/app resources. The steeleye-lkGUI package contains updates to the gen/app GUI
components that require the same version or later version of the core.
NOTE: When upgrading LifeKeeper, both the GUI and the core packages should be upgraded to
the latest versions. When the core is upgraded in conjunction with the GUI package, no errors
should occur.
Shutdown hangs on SLES10 systems
When running shutdown on an AMD64 system with SLES10, the system locks up and the
shutdown does not complete. This has been reported to Novell via bug #294787. The lockup
appears to be caused by the SLES10 powersave package.
Workaround:Remove the SLES10 powersave package to enable shutdown to complete
successfully.
224Troubleshooting