Bug 999730

Summary:	Numad logging crazily verbose
Product:	Red Hat Enterprise Linux 6	Reporter:	Dan Pritts <redhat>
Component:	numad	Assignee:	Bill Gray <bgray>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	jeharris, jsynacek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 12:41:58 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:
Embargoed:

Description Dan Pritts 2013-08-22 00:19:41 UTC

Description of problem:

1) /var/log/numad.log, when set at the default level, is crazily verbose.

Here is a sample of the output from a single run.  It runs every 15 seconds.  

Wed Aug 21 20:09:05 2013: Advising pid 51512 (jsvc) move from nodes (2) to nodes (2)
Wed Aug 21 20:09:05 2013: Including task: 51512
Wed Aug 21 20:09:05 2013: Including task: 51513
[ cut 148 "including task" lines ]
Wed Aug 21 20:09:05 2013: Including task: 60888
Wed Aug 21 20:09:05 2013: Including task: 61018
Wed Aug 21 20:09:05 2013: PID 51512 moved to node(s) 2 in 0.0 seconds


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

numad-0.5-8.20121015git.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1.start numad
2.look at log to try to understand what it's doing
3.feel brain melt out ears

Actual results:

brain melts

Expected results:

learn something useful from logs

Additional info:

Comment 1 Dan Pritts 2013-08-22 00:20:29 UTC

yeah, I know I can just grep out the bad lines, but sheesh.

Comment 3 RHEL Program Management 2013-10-14 02:37:11 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 Jan Kurik 2017-12-06 12:41:58 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/