Project

General

Profile

Bug #15808

Assign LOG_INFO priority to syslog calls

Added by Brad Hubbard over 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
05/10/2016
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
upgrade/dumpling
Release:
Needs Doc:

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.

  1. logger -p user.info "This should go to syslog"
  2. logger -p user.debug "This should not go to syslog"
  3. 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.


Related issues

Related to Ceph - Bug #13993: Use of syslog results in all log messages at priority "emerg" Resolved 12/07/2015
Copied to Ceph - Backport #17376: jewel: Assign LOG_INFO priority to syslog calls Resolved

Associated revisions

Revision 3ab5a660 (diff)
Added by Brad Hubbard over 1 year ago

log: Log.cc: Assign LOG_INFO priority to syslog calls

LOG_DEBUG prio messages are not logged by a default syslog
configuration so log at LOG_INFO instead.

Fixes: #15808
Signed-off-by: Brad Hubbard <>

History

#1 Updated by Brad Hubbard over 1 year ago

  • Related to Bug #13993: Use of syslog results in all log messages at priority "emerg" added

#2 Updated by Brad Hubbard over 1 year ago

  • Status changed from New to In Progress

#3 Updated by Nathan Cutler over 1 year ago

  • Backport set to jewel

#4 Updated by Brad Hubbard about 1 year ago

  • Status changed from In Progress to Resolved

#5 Updated by Samuel Just about 1 year ago

  • Status changed from Resolved to Pending Backport

#6 Updated by Nathan Cutler about 1 year ago

  • Copied to Backport #17376: jewel: Assign LOG_INFO priority to syslog calls added

#7 Updated by Loic Dachary 11 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF