Stopping LifeKeeper

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

*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 in usage.

!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.)

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.