You are here: Administration > Man Pages > lk_confirmso(1M)



lk_confirmso(1M) — instructs LifeKeeper to either proceed or not proceed with the failover of a server for which the confirmso!uname flag was set


LKROOT/bin/lk_confirmso { -y | -n } -s system_name


This command is used by the system administrator to instruct LifeKeeper to either proceed or not proceed with the failover of a server for which the confirmso!uname flag was set. If this flag is set when LifeKeeper detects the failure of the server indicated by the uname portion of the flag, LifeKeeper will issue the confirmso event via the LifeKeeper sendevent mechanism. By default, this event will cause a message to be printed on the system console with instructions for confirming or denying the pending failover (using this command with the appropriate options).

The -y option instructs LifeKeeper to proceed with the failover, while the -n option is used to tell LifeKeeper to abandon the failover. The system_name argument to the -s option indicates the failed system to which the instruction applies.

Because LifeKeeper uses the sendevent mechanism to issue the notification to the system console that a failover is pending which requires manual confirmation, it is possible to customize the event to send the notification elsewhere e.g., server management consoles, beepers, etc. This can be done by adding additional scripts to the confirmso event type directory.

LifeKeeper will timeout and perform the default action if no instruction is received within the timeout window. The default timeout value is 600 seconds or 10 minutes, and the default action is to allow the failover to proceed. These defaults can be modified by editing the CONFIRMSOTO and CONFIRMSODEF tunable values in the file /etc/default/LifeKeeper.


In a LifeKeeper configuration of 2 servers, SystemA and SystemB, the confirmso!SystemA flag is set on SystemB, indicating that any failovers from SystemA to SystemB require manual confirmation. SystemA fails, and SystemB detects the failure. The presence of the confirmso!SystemA flag on SystemB causes a confirmso event to be issued. The following message appears on the SystemB console:

LifeKeeper: FAILOVER RECOVERY OF MACHINE SystemA requires manual confirmation! Execute '/opt/LifeKeeper/bin/lk_confirmso -y -s SystemA' to allow this failover,  or execute '/opt/LifeKeeper/bin/lk_confirmso -n -s SystemA' to prevent it.  If no instruction is provided, LifeKeeper will timeout in 600 seconds and the failover will be allowed to proceed. 

After checking the status of SystemA, the administrator determines that SystemA is still alive, but has experienced a simple network failure which caused LifeKeeper on SystemB to lose all communication to SystemA. Since no failover is actually required, the administrator then issues the following command on SystemB to prevent the failover:

/opt/LifeKeeper/bin/lk_confirmso -n -s SystemA 


The following exit codes could be returned by these commands:


Execution of command completed successfully.


Failed to open the temporary file used to interface with the LifeKeeper Core, most likely because the specified server name was incorrect.


The location of this utility, LKROOT, is defined in the default file /etc/default/LifeKeeper.



© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.