[06/04/2014] - As this ticket is associated with a RHEL 6 bug, moving back to 10.2 (June).

Patch to switch numeric debug log levels OBNOXIOUS and INFO
20140624-Swap-numeric-values-of-OBNOXIOUS-and-INFO-debug-log.patch

The attached patch is basically a copy of the patch that was applied to Bugzilla Bug #1055080 - Giant /var/log/pki-ca/debug except it does not reset the CS.cfg 'debug.level=0' (log everything) to 'debug.level=10' (log information only) since the Fedora platform's primary usage is for development, and thus debug logs are used far more prevalently.

To test this patch:

• Build a default CA using the patched source
• Install the default CA using 'pkispawn'
• Examine the '/var/log/pki/pki-tomcat/ca/debug' file to reveal that it contains much content (debug.level=0)
• Shutdown the CA
• Edit '/etc/pki/pki-tomcat/ca/CS.cfg' and change 'debug.level=0' (log everything) to 'debug.level=10' (log information only)
• Empty the CA 'debug' log by typing 'cat /dev/null > /var/log/pki/pki-tomcat/ca/debug'
• Restart the CA
• Examine the '/var/log/pki/pki-tomcat/ca/debug' file to reveal that it contains minimal content (debug.level=10)

Checked into master:

• 532137ef51d0a4b422b6b9c73f9449e0f9dce6ee

Using the latest dogtag10 devel repo on F20, debug.level=0 in ca instance's CS.cfg but the debug log is very heavy. Verified the bug on RHEL 6.6, does not get the same debug log messages on F20.

On RHEL 6.6 the default value of debug.level=10 so was expecting the same on dogtag 10, missed step 5 in comment 8. Sorry for the mistake and reopening the ticket.

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1465

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.