|Summary:||Pinsetting jobs should be TRACE or FINE, not debug|
|Product:||[Community] Candlepin||Reporter:||Bryan Kearney <bkearney>|
|Component:||candlepin||Assignee:||Jesus M. Rodriguez <jesusr>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||John Sefler <jsefler>|
|Version:||0.5||CC:||jesusr, jmolet, lzap|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-05-30 13:15:39 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Bryan Kearney 2011-08-08 16:18:37 UTC
Hello, just upgraded to latest stable and getting DEBUG org.fedoraproject.candlepin.pinsetter.core.TransactionalPinsetterJob - System message every five seconds. Would it be possible to issue this rather with TRACE or FINEST level than with DEBUG? I expect this version will fill me HDD soon. :-) Thanks!
Comment 1 Jesus M. Rodriguez 2011-08-08 16:55:15 UTC
The CancelJob is the one causing this. It runs every 5 seconds. If it weren't for that no one would've noticed this log statement. I'd be ok with just removing the entire debug statement altogether. If removed, don't forget to remove the logger statement at the top as well.
Comment 2 Jesus M. Rodriguez 2011-08-09 00:52:49 UTC
Removed debug logging altogether, waiting on patch review.
Comment 3 Jesus M. Rodriguez 2011-08-09 20:06:38 UTC
fixed in 554a988972fa9f4e954bbabcb2bd1ceea8d5fab9
Comment 4 Lukas Zapletal 2011-08-10 07:52:43 UTC
Comment 5 Jesus M. Rodriguez 2011-09-14 00:56:03 UTC
Created attachment 523032 [details] offending catalina.out attaching a gziped copy of the offending catalina.out containing the offending lines. A separate file containing ONLY the offending lines will be attached as an example.
Comment 6 Jesus M. Rodriguez 2011-09-14 00:58:06 UTC
Created attachment 523033 [details] sample messages Here are the offending messages extracted from the previously attached log file for Aug 04 2011. It's clear that it happens every 5 seconds and could easily fill up a log file with useless information.
Comment 7 J.C. Molet 2011-09-27 18:14:45 UTC
Looking at the logs now, it seems to be only logged once, when the tomcat service starts. This is an acceptable level of logging for this. Marking VERIFIED. [root@mgmt5 config]# git branch 0.2 0.3 BETA * master ownergate [root@mgmt5 config]# git show-ref | grep master 1243076d76a343d157dc49bb0afb2de19ebfc71f refs/heads/master 1243076d76a343d157dc49bb0afb2de19ebfc71f refs/remotes/origin/master