TPS Logging Issues

[pki-bot]

This issue was migrated from Pagure Issue #2507. Originally filed by gkapoor (@geetikakay) on 2016-10-06 18:30:05:

• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1382252

---

1. In TPS CS.cfg, Factory setting has below mentioned properties.

logAudit.fileName=/var/lib/pki/topology-02-TPS/logs/tps/access
logError.fileName=/var/lib/pki/topology-02-TPS/logs/tps/error

but i don't see these files getting created.

2. when log.impl.file.class=com.netscape.cms.logging.LogFile
   does expirationTime and maxFileSize should work.Documenttaion doesn't clearly
   says anything about this.

Steps to Reproduce:

1. Set log.impl.file.class=com.netscape.cms.logging.LogFile
2. Set expiration time for self test logs and Audit logs.Below is the CS.cfg.

grep "expirationTime" /etc/pki/topology-02-TPS/tps/CS.cfg
log.instance.SignedAudit.expirationTime=12
log.instance.System.expirationTime=0
log.instance.Transactions.expirationTime=0
selftests.container.logger.expirationTime=10

3. Check that logs should get expired and deleted within mentioned time as
mentioned in https://access.redhat.com/documentation/en-US/Red_Hat_Certificate_
System/8.1/html/Admin_Guide/java-logs.html#Configuring_Logs_in_the_CS.cfg_File
page 497

4. Logs are not getting deleted.

Additional info:

Attaching CS.cfg for reference in associated bug.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-10-11 23:59:55

Per PKI Bug Council of 10/10/2016: 10.4

[pki-bot]

Comment from gkapoor (@geetikakay) at 2017-02-27 14:05:19

Metadata Update from @geetikakay:

• Issue set to the milestone: UNTRIAGED

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-03-03 20:20:24

Metadata Update from @mharmsen:

• Custom field feature adjusted to ''
• Custom field proposedmilestone adjusted to ''
• Custom field proposedpriority adjusted to ''
• Custom field reviewer adjusted to ''
• Custom field version adjusted to ''
• Issue close_status updated to: None
• Issue set to the milestone: 10.4 (was: UNTRIAGED)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 12:42:20

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 12:42:20

Metadata Update from @mharmsen:

• Issue set to the milestone: FUTURE (was: 10.4)