Syslog priority is broken for Ceph logs

Bug #1482215 reported by Simon Pasquier
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Medium
Radoslaw Zarzynski
7.0.x
Won't Fix
High
MOS Ceph
8.0.x
Won't Fix
Medium
MOS Ceph
Mitaka
Won't Fix
Medium
Radoslaw Zarzynski
Newton
Won't Fix
Medium
Radoslaw Zarzynski

Bug Description

The Ceph processes log messages with a broken priority value:

# tail /var/log/syslog
<8>Aug 6 12:54:15 node-38 ceph-mon: 2015-08-06 12:54:15.099553 7f23b2ac8700 0 mon.node-38@0(leader) e3 handle_command mon_command({"prefix": "df", "format": "json"} v 0) v1
<8>Aug 6 12:54:15 node-38 ceph-mon: 2015-08-06 12:54:15.113244 7f23b2ac8700 0 mon.node-38@0(leader) e3 handle_command mon_command({"prefix": "status", "format": "json"} v 0) v1
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.318317 7f6754fd9700 1 ====== starting new request req=0x7f6768010270 =====
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.319669 7f6754fd9700 1 ====== req done req=0x7f6768010270 http_status=200 ======
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.320780 7f6756fdd700 1 ====== starting new request req=0x7f6768010760 =====
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.321473 7f6755fdb700 1 ====== starting new request req=0x7f676801d5d0 =====
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.322608 7f6756fdd700 1 ====== req done req=0x7f6768010760 http_status=200 ======
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.322853 7f6755fdb700 1 ====== req done req=0x7f676801d5d0 http_status=200 ======
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.327602 7f67577de700 1 ====== starting new request req=0x7f676801ede0 =====
<8>Aug 6 12:54:16 node-38 radosgw: 2015-08-06 12:54:16.328477 7f67577de700 1 ====== req done req=0x7f676801ede0 http_status=200 ======

The priority <8> means facility=8 (user-level messages) and severity level=0 (emergency). So something is wrong here, these log messages are definitely not indicating an emergency situation...

The logging configuration for Ceph:
log_to_syslog_level = info
log_to_syslog = True
log_to_syslog_facility = LOG_LOCAL0

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "525"
  build_id: "2015-06-19_13-02-31"
  nailgun_sha: "dbd54158812033dd8cfd7e60c3f6650f18013a37"
  python-fuelclient_sha: "4fc55db0265bbf39c369df398b9dc7d6469ba13b"
  astute_sha: "1ea8017fe8889413706d543a5b9f557f5414beae"
  fuel-library_sha: "2e7a08ad9792c700ebf08ce87f4867df36aa9fab"
  fuel-ostf_sha: "8fefcf7c4649370f00847cc309c24f0b62de718d"
  fuelmain_sha: "a3998372183468f56019c8ce21aa8bb81fee0c2f"

Changed in fuel:
milestone: none → 7.0
assignee: nobody → Oleksiy Molchanov (omolchanov)
importance: Undecided → Medium
status: New → Confirmed
Changed in fuel:
status: Confirmed → Won't Fix
tags: added: logging
Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/8.0.x
Changed in fuel:
milestone: 7.0 → 8.0
status: Won't Fix → Confirmed
Dmitry Pyzhov (dpyzhov)
tags: added: area-library
Changed in fuel:
assignee: Peter Zhurba (pzhurba) → Fuel Library Team (fuel-library)
Changed in fuel:
status: Confirmed → In Progress
assignee: Fuel Library Team (fuel-library) → Maksim Malchuk (mmalchuk)
Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

changing *_syslog_level and *_syslog_facility in the ceph.conf and restarting services didn't solve the problem

Changed in fuel:
status: In Progress → Confirmed
assignee: Maksim Malchuk (mmalchuk) → MOS Linux (mos-linux)
Changed in fuel:
assignee: MOS Linux (mos-linux) → MOS Ceph (mos-ceph)
Dmitry Pyzhov (dpyzhov)
tags: added: area-mos
removed: area-library
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

We no longer fix Medium bugs in 8.0, closing as Won't Fix

Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Revision history for this message
Radoslaw Zarzynski (rzarzynski) wrote :

We no longer fix Medium bugs in 9.0, closing as Won't Fix.

Roman Vyalov (r0mikiam)
Changed in fuel:
milestone: 9.0 → 9.x-updates
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

We no longer support MOS5.1, MOS6.0, MOS6.1
We deliver only Critical/Security fixes to MOS7.0, MOS8.0.
We deliver only High/Critical/Security fixes to MOS9.2.

Changed in fuel:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.