Bug #15808
closedAssign LOG_INFO priority to syslog calls
0%
Description
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.
Updated by Brad Hubbard almost 8 years ago
- Related to Bug #13993: Use of syslog results in all log messages at priority "emerg" added
Updated by Brad Hubbard almost 8 years ago
- Status changed from New to In Progress
Updated by Brad Hubbard almost 8 years ago
- Status changed from In Progress to Resolved
Updated by Samuel Just over 7 years ago
- Status changed from Resolved to Pending Backport
Updated by Nathan Cutler over 7 years ago
- Copied to Backport #17376: jewel: Assign LOG_INFO priority to syslog calls added
Updated by Loïc Dachary over 7 years ago
- Status changed from Pending Backport to Resolved