Configuring Tps Logs - Red Hat CERTIFICATE SYSTEM 7.2 - ADMINISTRATION Administration Manual

• fileName . Specify the full path, including the filename, to the file to write messages. The
server should have read/write permission to the file.
• flushInterval . Specify the interval, in seconds, to flush the buffer to the file. The default
interval is 5 seconds. The flushInterval is the amount of time before the contents of the
buffer are flushed out and added to the log file.
• level . Specify a log level. The choices are 0 for debug, 1 for information, 2 for warning, 3 for
failure, 4 for misconfiguration, 5 for catastrophe, and 6 for security. The default selection is 1.
For more information, see
• maxFileSize . Specify the file size in kilobytes (KB) for the error log. The default size is 100
KB. The maxFileSize determines how large a log file can become before it is rotated. Once
it reaches this size, the file is copied to a rotated file, and the log file is started anew. For more
information, see
• register . If this variable is set to false (the default value), the self-test messages are
only logged to the log file specified by selftests.container.logger.fileName. If this
variable is set to true, then the self-test messages are written to both the log file specified
by selftests.container.logger.fileName as well as to the log file specified by
log.instance.Transactions.fileName.
• rolloverInterval . Specify the frequency at which the server rotates the active error log
file. The available choices are hourly, daily, weekly, monthly, and yearly. The default selection is
monthly. For more information, see
• type . Set to transaction or system.
5. Save the file.
6. Start the subsystem instance.

3.9.8. Configuring TPS Logs

Logging TPS instance activities is handled differently than in the other subsystems. There are three
TPS instance logs:
• tps-debug.log
• tps-error.log
• tps-audit.log
These logs are stored in the /var/log/instance_ID directory. Other types of logs, such as
transaction logs and system logs, are not generated by the TPS instance.
Additionally, certain log features that are available to the other subsystems' logs do not apply to TPS
logging:
• Log rotation
• Log signing
• Registering and deleting log modules
Section 3.9.3, "Log Levels (Message
Section 3.9.5, "Log File
Section 3.9.5, "Log File
Rotation".
Rotation".
Configuring TPS Logs
Categories)".
83