Project

General

Profile

Actions

Bug #15808

closed

Assign LOG_INFO priority to syslog calls

Added by Brad Hubbard almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
upgrade/dumpling
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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 2 (0 open2 closed)

Related to Ceph - Bug #13993: Use of syslog results in all log messages at priority "emerg"ResolvedBrad Hubbard12/07/2015

Actions
Copied to Ceph - Backport #17376: jewel: Assign LOG_INFO priority to syslog callsResolvedBrad HubbardActions
Actions #1

Updated by Brad Hubbard almost 8 years ago

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

Updated by Brad Hubbard almost 8 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Nathan Cutler almost 8 years ago

  • Backport set to jewel
Actions #4

Updated by Brad Hubbard almost 8 years ago

  • Status changed from In Progress to Resolved
Actions #5

Updated by Samuel Just over 7 years ago

  • Status changed from Resolved to Pending Backport
Actions #6

Updated by Nathan Cutler over 7 years ago

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

Updated by Loïc Dachary over 7 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF