Stopping LifeKeeper

Use the following command to stop LifeKeeper. The lkadmin privilege is required to run this command.

*Note: Do not stop LifeKeeper while a resource is starting or stopping. In particular, immediately after starting LifeKeeper, check the lifekeeper.log to ensure that no resources are running.

/opt/LifeKeeper/bin/lkcli stop [-f|-i|-n|-r]

See LifeKeeper Command Line Interface (LKCLI) for details on the command.

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

!When ‘lkcli stop -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 ‘lkcli stop -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.)

Behavior Differences Depending on Options

The behavior with each option is as follows.

The -i option prompts for a “yes/no” confirmation to continue the shutdown process. Otherwise, its behavior is the same as the -f option.