Giant /var/log/pki-ca/debug

[pki-bot]

This issue was migrated from Pagure Issue #898. Originally filed by mharmsen (@mharmsen) on 2014-03-10 23:59:16:

• Closed as Fixed
• Assigned to mharmsen (@mharmsen)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1055080

---

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1055080

I just received a warning that my /var/log filesystem was almost full.  It
turns out that /var/log/pki-ca/debug had grown to 190MB.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2014-06-05 00:04:07

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2014-06-25 02:54:44

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2014-06-25 02:58:21

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)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2014-06-26 03:30:42

Checked into master:

• 532137e

[pki-bot]

Comment from rpattath (@rpattath) at 2014-07-25 21:44:20

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.

[pki-bot]

Comment from rpattath (@rpattath) at 2014-07-25 23:10:59

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.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-02-27 14:07:48

Metadata Update from @mharmsen:

• Issue assigned to mharmsen
• Issue set to the milestone: 10.2 - 06/14 (June)