Stopping LifeKeeper

If you need to stop LifeKeeper, type the appropriate command as root to stop it:

Using systemctl Command

• systemctl set-environment LKSTOP_MODE=stop-nofailover; systemctl stop lifekeeper; systemctl unset-environment LKSTOP_MODE
  This command will shut down LifeKeeper on the local system if it is currently running. It will first remove all protected resources from service on the local system then shut down the LifeKeeper daemons. Protected resources will not fail over to another system in the cluster.

• systemctl set-environment LKSTOP_MODE=stop-daemons; systemctl stop lifekeeper; systemctl unset-environment LKSTOP_MODE
  This command will skip the section that removes the resources from service. The resources will remain running on the local system but will no longer be protected by LifeKeeper. This command should be used with caution because if resources are not gracefully shut down, then items such as SCSI locks will not be removed. If the system on which this command is executed subsequently fails or is shut down, the system(s) will NOT initiate failover of the appropriate resources.

• systemctl stop lifekeeper
  This command will remove the resources from service but does not set the !nofailover! flag (see LifeKeeper flag) on any of the systems that it can communicate with. This means that failover will occur if the shutdown_switchover flag is set. If shutdown_switchover is not set, this command behaves the same as when stop-nofailover is specified in LKSTOP_MODE.

• systemctl set-environment LKSTOP_MODE=stop-failover; systemctl stop lifekeeper; systemctl unset-environment LKSTOP_MODE
  This command will remove resources from service and initiate failover. It will behave the same as systemctl stop lifekeeper when the shutdown_switchover flag is set.

*Note: The above command does not change the auto-start setting of lifekeeper.service. Therefore, whether or not LifeKeeper is automatically started when the system is rebooted depends on the auto-start setting of lifekeeper.service at system shutdown.

Using lkstop Command

*Note: The lkstop process will continue even when a resource remove fails and will not result in a failed lkstop.

• /opt/LifeKeeper/bin/lkstop
  This command will shut down LifeKeeper on the local system if it is currently running. It will first remove all protected resources from service on the local system then shut down the LifeKeeper daemons.

• /opt/LifeKeeper/bin/lkstop -f
  This command will skip the section that removes resources from service. The resources will remain running on the local system but will no longer be protected by LifeKeeper.

*See Commands for additional options and best practices.

*Note: The above command disables the autostart setting of lifekeeper.service (except when the -r option is specified). Therefore, unless you enable the autostart setting of lifekeeper.service when executing the command, LifeKeeper will not autostart after rebooting the system.

!When ‘lkstop -f’ is used to stop LifeKeeper, in-service resources are left configured and running, including data replication resources. It is important that the hierarchy/resources are allowed to be brought back in-service on the correct server after an ‘lkstop -f’. LifeKeeper will automatically bring all resources in-service once communication is established with all servers. Data replication resources may temporarily be marked OSF while LifeKeeper is waiting for all servers to restart and rejoin the cluster. (Please refer to the system’s log files for additional information pertaining to that node.)

Stop Command Behavior Differences

Disabling Automatic LifeKeeper Restart

If you do not want LifeKeeper to automatically restart when the system is restarted, type the following command:

chkconfig lifekeeper off

or

systemctl disable lifekeeper

See the chkconfig (or systemctl) man page for further information.