LifeKeeper Event Email Notification is a mechanism by which one or more users may receive email notices when certain events occur in a LifeKeeper cluster. LifeKeeper has an event notification mechanism for registering applications that wish to be notified of specific events or alarms (see the sendevent(5) man page). LifeKeeper can be easily enabled to send email notification of key LifeKeeper events to a selected set of users wishing to monitor LifeKeeper activity.
By default, LifeKeeper Event Email Notification is disabled. Enabling this feature requires setting the LK_NOTIFY_ALIAS environment variable defined in /etc/default/LifeKeeper. The LK_NOTIFY_ALIAS environment variable can be set to a single email address or alias, or it can contain multiple addresses or aliases separated by commas. To set LK_NOTIFY_ALIAS either run lk_confignotify alias (See the lk_confignotifyalias(1M) man page for an example) from the command line and supply the address or list of addresses that should receive email when an event occurs or edit the defaults file /etc/default/LifeKeeper to add the email address or address list. Search for the entry LK_NOTIFY_ALIAS= and insert the address or address list separated by commas. Repeat this action on all nodes in the cluster that need to send email for the selected LifeKeeper events.
To disable Email Notification, either run lk_confignotifyalias (See the lk_confignotifyalias(1M) man page for an example) with the —disable argument or edit the defaults file /etc/default/LifeKeeper and remove the setting of LK_NOTIFY_ALIAS (change the line to LK_NOTIFY_ALIAS=).
LifeKeeper Events Generating Email
The following LifeKeeper events will generate email notices when LK_NOTIFY_ALIAS is set.
|LifeKeeper Event||Event Description|
|LifeKeeper Startup Complete||Sent from a node when LifeKeeper is started on that node.|
|LifeKeeper Shutdown Initiated||Sent from a node beginning LifeKeeper shutdown.|
|LifeKeeper Shutdown Complete||Sent from a node completing LifeKeeper shutdown.|
|LifeKeeper Manual Switchover Initiated on Server||Sent from the node from which a manual switchover was requested.|
|LifeKeeper Manual Switchover Complete – recovered list||Sent from the node where the manual switchover was completed listing the resource successfully recovered.|
|LifeKeeper Manual Switchover Complete – failed list||Sent from the node where the manual switchover was completed listing the resource that failed to successfully switchover.|
|LifeKeeper Node Failure Detected||Sent from each node within the cluster when a node in that cluster fails.|
|LifeKeeper Node Recovery Complete for Server – recovered list||Sent from each node within the cluster that has recovered resources from the failed node listing the resource successfully recovered.|
|LifeKeeper Node Recovery Complete for Server – failed list||Sent from each node within the cluster that has failed to recover resources from the failed node listing the resource that failed to successfully recover.|
|LifeKeeper Resource Recovery Initiated||Sent from a node recovering a resource; a “Resource Recovery Complete” or “Resource Recovery Failed” message always follows to indicate whether the recovery was completed or failed.|
|LifeKeeper Resource Recovery Complete||Sent from the node that issued a “Resource Recovery Initiated” message when the recovery of the resource is completed listing the resource successfully recovered.|
|LifeKeeper Resource Recovery Failed||Sent from the node that issued a “Resource Recovery Initiated” message if the resource fails to come into service listing the resource that failed to successfully recover.|
|LifeKeeper Communications Path Up||A communications path to a node has become operational.|
|LifeKeeper Communications Path Down||A communications path to a node has gone down.|
|LifeKeeper <Node Monitoring> Failure Detected||Sent from a node where a failure was detected with Node Monitoring of the Standby Node Health Check. Detected failure is described in <Node Monitoring>.|
|LifeKeeper <OSUquickCheck> Failure Detected||Sent from a node where a failure was detected with OSU resource monitoring of the Standby Node Health Check. Tag name of the resource where the failure was detected is described in <OSUquickCheck>.|