Bug 766904

Summary:	[RFE] Create a command line tool to change the debug levels on the fly
Product:	Red Hat Enterprise Linux 6	Reporter:	Jenny Severance <jgalipea>
Component:	sssd	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED ERRATA	QA Contact:	IDM QE LIST <seceng-idm-qe-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2	CC:	apeetham, dpal, grajaiya, jgalipea, prc, sgallagh
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sssd-1.8.0-2.el6.beta2	Doc Type:	Enhancement
Doc Text:	Cause: SSSD would only read its configuration at startup time. This means that the verbosity of the debug logs could only be set at startup time. Consequence: When trying to track down an intermittent error, users would have to leave noisy debug logs enabled for extended periods. A reboot to change the debug level might obscure the problem again for some time until it reoccurred. Change: SSSD added a new command-line tool to change the debug level of live SSSD processes. Result: Users can now change the debug verbosity of the SSSD processes without restarting SSSD.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 11:49:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	799039

Description Jenny Severance 2011-12-12 19:16:16 UTC

Description of problem:

This idea was mentioned by Stephen on our ML:

https://fedorahosted.org/pipermail/sssd-devel/2011-May/006142.html

We support changing debug levels on the fly when the admin changes the debug_level variable with low level ldb tools. However, this is not user-friendly.

We should create a new command line tool that would change the debug_level value and send SIGHUP to sssd to instrument it to change its debug level. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Upstream ticket :: https://fedorahosted.org/sssd/ticket/950

Comment 1 Jenny Severance 2011-12-12 19:24:55 UTC

related upstream ticket :: https://fedorahosted.org/sssd/ticket/789

Comment 2 Jenny Severance 2012-01-30 20:42:43 UTC

*** Bug 785882 has been marked as a duplicate of this bug. ***

Comment 3 Stephen Gallagher 2012-01-30 21:02:20 UTC

Upstream ticket:
https://fedorahosted.org/sssd/ticket/950

Comment 6 Amith 2012-05-10 07:39:43 UTC

Verified on sssd-1.8.0-22.el6.x86_64.
Most of the test cases passed during verification. However few issues were found and following bugs are logged:

https://bugzilla.redhat.com/show_bug.cgi?id=820362
https://bugzilla.redhat.com/show_bug.cgi?id=820490

Comment 7 Stephen Gallagher 2012-06-12 13:23:23 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: SSSD would only read its configuration at startup time. This means that the verbosity of the debug logs could only be set at startup time.

Consequence: When trying to track down an intermittent error, users would have to leave noisy debug logs enabled for extended periods. A reboot to change the debug level might obscure the problem again for some time until it reoccurred.

Change: SSSD added a new command-line tool to change the debug level of live SSSD processes.

Result: Users can now change the debug verbosity of the SSSD processes without restarting SSSD.

Comment 9 errata-xmlrpc 2012-06-20 11:49:32 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.

http://rhn.redhat.com/errata/RHBA-2012-0747.html