Log File Locations - Netscape MANAGEMENT SYSTEM 4.5 Installation And Setup Manual

Table 23-3 Classification of log entries or messages (Continued)
Log level Message category
3 Failure
(default selection for
system and error logs)
4 Misconfiguration
5 Catastrophic failure
6 Security-related events
You can use log levels to filter log entries based on the severity of an event. By
default, a level 3 (Failure) is set for all services.
NOTE

Log File Locations

For quick access, all the log files—system, error, and audit—are maintained in your
local file system. Make sure that your storage capacity is sufficient for all your log
files. A log file has the following default location:
<server_root>/cert-<instance_id>/logs
You can change the default location for logs by modifying it in the configuration.
Description
These messages indicate errors and failures that prevent the server
from operating normally.
Examples of messages that fall into this category include failures to
perform a certificate service operation ("User authentication failed" or
"Certificate revoked") and unexpected situations that can cause
irrevocable errors ("The server cannot send back the request it
processed for a client through the same channel the request came from
the client").
These messages indicate that a misconfiguration in the server is
causing an error.
These messages indicate that because of an error, the service cannot
continue running.
These messages identify occurrences that affect the security of the
server (for example, "Privileged access attempted by user with
revoked or unlisted certificate").
The log level is additive—that is, specifying a value of 3 causes
levels 4, 5, and 6 to be logged. Log data can be voluminous,
especially at lower (more verbose) logging levels. Make sure that
the host machine has sufficient disk space for all the log files. It is
also important to define your logging level, log rotation, log
expiration, and server-backup policies appropriately so that all the
log files are backed up and the host system doesn't get overloaded;
otherwise, you may lose information.
Introduction to Logs
Chapter 23 Managing CMS Logs 769