Groupings and Basic Descriptions of LifeKeeper bin Commands

The commands will be in: /opt/LifeKeeper/bin

To place this in your path, execute: ‘. /etc/default/LifeKeeper’

Starting and Stopping LifeKeeper, the GUI, etc.

lkstart – Start LifeKeeper core



lkstop – Stop LifeKeeper core. The behavior differs depending on the command line options.


None – Stop LifeKeeper core and the protected services. The protected service is switched over to the standby system (see Stopping LifeKeeper).

-r – Leave auto-start on system startup enabled.

-n – Stop LifeKeeper core and the protected service. No switchover to the standby system is performed.

-f – Stop LifeKeeper core but do not stop the protected resources.

-i – Stop LifeKeeper core but do not stop the protected resources. The user is prompted to confirm (yes/no) that they want to continue.

lkGUIserver – Start and stop the LifeKeeper GUI daemon processes





lkGUIapp – Starts the LifeKeeper Java application



Monitoring LK and Other Misc. LifeKeeper Commands

lcdstatus – Display status of LifeKeeper resources, comm paths, etc.


-d – <node to run command on>

-q – short reports

lcdsync – Writes LifeKeeper configuration information from memory to disk


-d – <other node to run it on>

lcdrcp – Transfer files from one LifeKeeper node to another via the comm. path


lcdrcp <file names> {dest:ofile | dest:odir}

lcdremexec – Execute the given command on the given LifeKeeper node


-d <node to run command on> <command>

lcdrecover – Checks and sets resource hierarchy instance settings


See the documentation.

Bringing a Hierarchy into and out of Service

perform_action – Performs a given action on a given resource and can be used to switch a given hierarchy to another node.


-a <action name>

-t <tag name>


perform_action -a restore -t $LKTag – bring tier into service

perform_action -a remove -t $LKTag – take tier out of service

Checking the LifeKeeper Configuration

lkchkconf : Performs the following checks to verify /etc/default/LifeKeeper settings.

  • Checks that the running system is actually using the current settings found in /etc/default/LifeKeeper.
    If the current setting of LifeKeeper is different from the /etc/default/LifeKeeper setting, an error message is output to inform the user.
  • Checks for any inconsistencies between the resource health check time interval(LKCHECKINTERVAL) and the timeout value of each ARK.
    An error message will be logged if the timeout value of each ARK is longer than the resource health check time interval (LKCHECKINTERVAL).

Options: – None


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment