.Ceph log messages are now LOG_INFO priority
Previously, Ceph log messages had the `LOG_DEBUG` priority. However, with the default `syslog` configuration, `LOG_DEBUG` messages do not appear in the logs. With this update, Ceph log messages have `LOG_INFO` priority, ensuring that they appear in the logs.
Description of problem:
When we resolved Bug #13993 to stop everything sent to syslog being sent at LOG_EMERG priority it was decided LOG_DEBUG was the appropriate level. In hindsight I believe this was the wrong decision and that LOG_INFO is a better choice.
With a default syslog configuration syslog messages sent at LOG_DEBUG priority do not make it to the logs, since by default syslog logs everything of info level or higher. So, in order to see syslog messages from Ceph (including logs generated in the event of as crash) currently requires configuring Ceph to log to syslog and also configuring syslog (or rsyslog) to display debug messages.
The problem can be demonstrated on a system with syslog configured using the following.
logger -p user.info "This should go to syslog"
logger -p user.debug "This should not go to syslog"
grep "to syslog" /var/log/messages
May 10 02:22:02 intel-boxen-02 root: This should go to syslog
The move to journalctl will make this less of an issue IMHO but that may take a while to be the default in all environments.
Version-Release number of selected component (if applicable):
10.2.2-41.el7cp.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2815.html
Description of problem: When we resolved Bug #13993 to stop everything sent to syslog being sent at LOG_EMERG priority it was decided LOG_DEBUG was the appropriate level. In hindsight I believe this was the wrong decision and that LOG_INFO is a better choice. With a default syslog configuration syslog messages sent at LOG_DEBUG priority do not make it to the logs, since by default syslog logs everything of info level or higher. So, in order to see syslog messages from Ceph (including logs generated in the event of as crash) currently requires configuring Ceph to log to syslog and also configuring syslog (or rsyslog) to display debug messages. The problem can be demonstrated on a system with syslog configured using the following. logger -p user.info "This should go to syslog" logger -p user.debug "This should not go to syslog" grep "to syslog" /var/log/messages May 10 02:22:02 intel-boxen-02 root: This should go to syslog The move to journalctl will make this less of an issue IMHO but that may take a while to be the default in all environments. Version-Release number of selected component (if applicable): 10.2.2-41.el7cp.x86_64