Trace logs are generated when ADSS Server is started and are created inside the [ADSS Server Home]/logs directory. Trace logs contain information about all transactions e.g. at what time and from where a request came and when the response was sent. It also stores the steps performed by ADSS Server when generating the response. Errors are also reported inside these logs. Details of the disk spaces requirements are shown below. Note that logs sizes depend upon the amount of ADSS Server usage and whether DEBUG Mode is set to ON or OFF.  Refer to ADSS Server Logging for details of how to modify the log settings mode.

Log Dir

Disk Utilization (DEBUG is ON)

Disk Utilization (DEBUG is OFF)

console

Depends upon console usage. Approx 0.5 MB/day (two people using the console extensively)

Depends upon console usage. Approx 0.1 MB/day (two people using the console extensively)

service/crlmanager

4 KB/ CA for which ADSS Server polls

3 KB/ CA for which ADSS Server polls

service/signing

11 KB/ signing request

5 KB/ signing request

service/verification

16 KB/ request containing 1 signature. Add 9KB for each additional signature

9 KB/ request containing 1 signature. Add 5KB for each additional signature

service/certification

8 KB / certification request

4 KB / certification request

service/ocsp

5 KB/ request containing 1 Certificate ID

1 KB/ request containing 1 Certificate ID

service/tsa

5 KB/ request

4 KB/ request

service/xkms

8 KB/ request containing 1 certificate Add 2 KB for each additional certificate being validated

4 KB/request containing 1 certificate. Add 2KB for each additional certificate

service/ltan

10 KB/ request

5 KB/ request

system

3 KB for every ADSS Server start + 4.5 KB for a system user login + 0.5 KB for any service request received

2.7 KB for every ADSS Server start + 0.5 KB for any service request received

tomcat

Varies based on ADSS usage. If all services are being used then based on the table shown above, the size requirement will vary from 1 KB 100 KB.  These logs are usually generated when tomcat goes in an error state.


See also

Database