Bug 924399

Summary: cgrulesengd daemon has different default logging level than the rest of the library
Product: Red Hat Enterprise Linux 6 Reporter: Peter Schiffer <pschiffe>
Component: libcgroupAssignee: Peter Schiffer <pschiffe>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: jsafrane, lnovich, ovasik, varekova
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: cgrulesengd daemon had different default logging level than the rest of the library Consequence: inconsistent log messages Fix: unify logging level of cgrulesengd daemon and library Result: unified log messages
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 22:33:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
libcgroup-0.37-cgrulesengd-logging.patch none

Description Peter Schiffer 2013-03-21 17:18:25 UTC
Description of problem:
cgrulesengd daemon has different logging level settings than the rest of the library which are not in sync

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run cgconfig and cgred service
2. see /var/log/messages
Actual results:
many warning messages in /var/log/messages from cgrulesengd daemon

Expected results:
only errors in /var/log/messages from cgrulesengd daemon

Additional info:
patch posted in upstream:

Comment 6 Peter Schiffer 2013-07-31 15:55:15 UTC
Created attachment 781225 [details]

Comment 9 Mike Gahagan 2013-09-19 19:51:43 UTC
confirmed cgrulesengd from libcgroup-0.40.rc1-3.el6 now has default log level for errors rather than warnings.

Comment 10 errata-xmlrpc 2013-11-21 22:33:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.