Cluster logging_daemon settings from /etc/cluster/cluster.conf are not being applied in RHEL 6
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
- One or more
<logging_daemon>entries in/etc/cluster/cluster.conf cmanreleases prior to3.0.12.1-59.el6_5.1in RHEL 6 Update 5, or prior to3.0.12.1-68.el6in other releases.
Issue
- When I configure settings in a
<logging_daemon>entry in/etc/cluster/cluster.conf, the settings don't get applied - I tried to change the
syslog_priorityorlogfile_priorityforrgmanagervia alogging_daemon, but it still logged at the old priority.
<logging>
<logging_daemon name="rgmanager" syslog_priority="notice" logfile_priority="notice"/>
</logging>
- Why are things logged into
/var/log/clusterwhile in the/etc/cluster/cluster.conflogging_daemonentry I have a different directory?
<logging logfile_priority="debug" syslog_facility="daemon" syslog_priority="info" to_logfile="yes" to_syslog="yes">
<logging_daemon logfile="/var/log/mysql/qdiskd.log" name="qdiskd"/>
<logging_daemon logfile="/var/log/mysql/fenced.log" name="fenced"/>
<logging_daemon logfile="/var/log/mysql/rgmanager.log" name="rgmanager"/>
<logging_daemon logfile="/var/log/mysql/corosync.log" name="corosync"/>
</logging>
Resolution
- RHEL 6 Update 5: Update to
cman-3.0.12.1-59.el6_5.1or later. - Other RHEL 6 Updates: Update to
cman-3.0.12.1-68.el5or later. - Workaround for all releases: Configure the desired settings in the global
<logging>tag:
<logging syslog_priority="notice" logfile_priority="notice"/>
Note: This will change the relevant attributes for all logging daemons. There is currently no way to make changes to the individual daemons independently.
Root Cause
This issue is being tracked by Red Hat Engineering via Bugzilla #980575.
An issue exists in the cluster package that causes it to query the configuration system for an invalid attribute when searching for the logging_daemon settings. The individual daemons call this function to determine what settings they should use for logging, and the bug causes the configured values to be ignored.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.