Installation – Known Issues / Restrictions

SAP Recovery Kit is Automatically Installed During Upgrade if SAP DB Recovery Kit has been Previously Installed

If the SAP DB/SAP MaxDB Recovery Kit is installed, the SAP Recovery Kit will automatically be selected for installation when upgrading LifeKeeper even if it was not previously installed. This will be fixed in a future version of LifeKeeper.

Workaround: When upgrading a system with the SAP DB/SAP MaxDB Recovery Kit installed where the user does not intend to install the SAP Recovery Kit, manually deselect the SAP Recovery Kit (under Application Suite → SAP Recovery Kit) for installation.

A functional yum or zypper configuration is required for the successful installation of LfieKeeper.

A misconfigured or non-functional yum or zipper configuration can result in the failure of the LifeKeeper installation script. Output such as the following may be seen:

Install LifeKeeper and dependent packages done.
Setup high availability data replication features.. done.
Setup NFS high availability features…
Configure LifeKeeper management group

Setup failed.
Fix the problem and try again.
sed: can’t read /etc/default/LifeKeeper: No such file or directory
/tmp/mnt/setuplibs/install.sh: line 118: /config/system_information: No such file or directory
/tmp/mnt/setuplibs/install.sh: line 122: /config/system_information: No such file or directory
/tmp/mnt/setuplibs/install.sh: line 122: /config/system_information: No such file or directory
/tmp/mnt/setuplibs/install.sh: line 122: /config/system_information: No such file or directory

Additionally, the following may be seen in the /var/log/LK_install.log file:

Abort, retry, ignore? [a/r/i/? shows all options] (a): a
done.

Linux Dependencies

Installing SIOS Protection Suite for Linux including the optional Recovery Kits requires several packages which have dependencies. If the package manager is properly configured, the required package is automatically installed by the package manager.

If the installation can not be done automatically, the setup script will be interrupted. After manually installing dependent packages (see Linux dependencies for details), re-execute the setup script.

Note: If the installation of these dependent packages is not completed successfully, it could affect the ability to start SIOS Protection Suite for Linux as well as the loading of the SIOS Protection Suite for Linux GUI.

The multipathd daemon will log errors in the error log when the nbd driver is loaded as it tries to scan the new devices

Solution: To avoid these errors in the log, add devnode “^nbd” to the blacklist in /etc/multipath.conf.

mksh conflicts with SIOS Protection Suite for Linux setup needing ksh

If the mksh package is installed, the SIOS Protection Suite for Linux setup will fail indicating a package conflict. The SIOS Protection Suite for Linux requires the ksh package.

Workaround: On RHEL, CentOS or Oracle Linux, remove the mksh package and install the ksh package. After installing the ksh package, re-run the SIOS Protection Suite for Linux setup.

Example:

1. Remove the mksh package
   yum remove mksh
   
   
2. Install the ksh package
   yum install ksh
   
   
3. Re-run setup

Unexpected termination of daemons

Daemons using IPC terminate unexpectedly after update to Red Hat Enterprise Linux 7.2 and Red Hat 7.2 derivative systems. A new systemd feature was introduced in Red Hat Enterprise Linux 7.2 related to the cleanup of all allocated inter-process communication (IPC) resources when the last user session finishes. A session can be an administrative cron job or an interactive session. This behavior can cause daemons running under the same user, and using the same resources, to terminate unexpectedly.

To work around this problem, edit the file /etc/systemd/logind.conf and add the following line:
RemoveIPC=no

Then, execute the following command, so that the change is put into effect:
systemctl restart systemd-logind.service

After performing these steps, daemons no longer crash in the described situation. Applications (such as MQ, Oracle, SAP, etc) using shared memory and semaphores may be affected by this issue and therefore require this change.

Re-execution of LifeKeeper’s “setup” script may be required after updating the kernel

In Red Hat Enterprise Linux 7.x/CentOS 7.x/Oracle Linux 7.x environment, DataKeeper may not function properly when updating the kernel to 7.3 or later.

Workaround:
The problem will be solved by re-running the “setup” script that was executed when installing LifeKeeper on the updated system.

Description:
A loaded kernel module cannot be used after updating the kernel to 7.3 or later due to the compatibility of OS kernel modules.
DataKeeper uses a kernel module called nbd.ko, which accesses disks through the network. A correct nbd.ko module is installed when executing setup script for LifeKeeper installation.
nbd.ko for the new kernel will be installed by executing setup script again after updating the kernel.

Unnecessary warning, displayed from the setup script

Depending on the installation status of the LifeKeeper packages, the following warning is displayed when the setup script is executed.

missing /opt/LifeKeeper/lkadm/subsys/scsi/DEVNAME
missing /opt/LifeKeeper/lkadm/subsys/scsi/DEVNAME/bin
missing /opt/LifeKeeper/subsys/scsi/resources/DEVNAME