Beginning with LifeKeeper 8.0, logging is done through the standard syslog facility. LifeKeeper supports two syslog implementations: rsyslog, and syslog-ng. During package installation, syslog will be configured to use the "local6" facility for all LifeKeeper log messages (If "local6" has already been in use, please use other local). The syslog configuration file (for example, /etc/rsyslog.conf or /etc/syslog-ng/syslog-ng.conf) will be modified to include LifeKeeper-specific routing sending all LifeKeeper log messages to /var/log/lifekeeper.log. (The original configuration file will be backed up with the same name ending in "~".)
|
|
Important: DO NOT edit LifeKeeper unique setups manually, or, upgrading or uninstalling may not function correctly. |
The facility can be changed after installation by using the lklogconfig tool located in /opt/LifeKeeper/bin.
For example, changing the facility to local5, run the following command instead.
lkstop -f
lklogconfig --action=update --facility=local5
lkstart
See the lklogconfig(8) manpage on a system with LifeKeeper installed for more details on this tool.
If a generic resource script puts a message into /opt/LifeKeeper/out/log directly, LifeKeeper will send a log message with the error severity level as the default into /var/log/lifekeeper.log. The severity level can be changed to information level by adding the following parameter into /etc/default/LifeKeeper, LOGMGR_LOGLEVEL=LK_INFO.
Note: When LifeKeeper is removed from a server, the LifeKeeper-specific syslog configuration will be removed.
© 2018 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.