Project

General

Profile

Bug #57049

cluster logging does not adhere to mon_cluster_log_file_level

Added by Prashant D over 1 year ago. Updated over 1 year ago.

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

0%

Source:
Tags:
Backport:
Regression:
Yes
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Even after setting mon_cluster_log_file_level to info or less verbose level, we are still seeing debug logs are getting logged to the cluster log file.

$ ceph config set mon mon_cluster_log_file_level warn

cluster log file :

2022-08-05T11:28:00.097804-0400 osd.2 (osd.2) 13 : cluster [DBG] 2.8 scrub ok
2022-08-05T11:28:00.258964-0400 mon.a (mon.0) 182 : audit [INF] from='mgr.4110 10.74.128.231:0/467438' entity='mgr.x' cmd='[{"prefix": "osd pool set", "pool": "cephfs.a.meta", "var": "pgp_num_actual", "val": "8"}]': finished
2022-08-05T11:28:00.259025-0400 mon.a (mon.0) 183 : cluster [DBG] osdmap e37: 3 total, 3 up, 3 in
2022-08-05T11:28:01.266884-0400 mon.a (mon.0) 184 : cluster [DBG] osdmap e38: 3 total, 3 up, 3 in
2022-08-05T11:28:01.556299-0400 mgr.x (mgr.4110) 37 : cluster [DBG] pgmap v71: 49 pgs: 2 peering, 47 active+clean; 578 KiB data, 3.0 GiB used, 300 GiB / 303 GiB avail
2022-08-05T11:28:01.863949-0400 osd.0 (osd.0) 9 : cluster [DBG] 3.9 scrub starts
2022-08-05T11:28:01.870440-0400 osd.0 (osd.0) 10 : cluster [DBG] 3.9 scrub ok
2022-08-05T11:28:01.940313-0400 osd.1 (osd.1) 14 : cluster [DBG] 3.4 scrub starts
2022-08-05T11:28:01.946881-0400 osd.1 (osd.1) 15 : cluster [DBG] 3.4 scrub ok
2022-08-05T11:28:02.821282-0400 osd.0 (osd.0) 11 : cluster [DBG] 3.1 scrub starts
2022-08-05T11:28:02.827805-0400 osd.0 (osd.0) 12 : cluster [DBG] 3.1 scrub ok
2022-08-05T11:28:03.557303-0400 mgr.x (mgr.4110) 38 : cluster [DBG] pgmap v72: 49 pgs: 2 peering, 47 active+clean; 578 KiB data, 3.0 GiB used, 300 GiB / 303 GiB avail


Related issues

Duplicated by RADOS - Bug #57727: mon_cluster_log_file_level option doesn't take effect Duplicate

History

#1 Updated by Prashant D over 1 year ago

  • Pull request ID set to 47480

#2 Updated by Prashant D over 1 year ago

  • Status changed from New to Fix Under Review

#3 Updated by Prashant D over 1 year ago

  • Pull request ID changed from 47480 to 47502

#4 Updated by Prashant D over 1 year ago

I had a PR#47480 opened for this issue but closed it in favor of PR#47502. The PR#47502 addresses this issue along with handling of the cluster logging to external entities according to cluster log level set.

#5 Updated by Ilya Dryomov over 1 year ago

  • Duplicated by Bug #57727: mon_cluster_log_file_level option doesn't take effect added

#6 Updated by Ilya Dryomov over 1 year ago

  • Regression changed from No to Yes

#7 Updated by Radoslaw Zarzynski over 1 year ago

  • Status changed from Fix Under Review to Duplicate

Also available in: Atom PDF