[Contents] [Prev] [Next] [Index] [Report an Error]

## Rotation of Log Files

On C Series Controllers, log files that contain entries are rotated daily when other daily system tasks run on the system. The system retails 5 log files for a component before overwriting the oldest file.

When a new log file is opened to replace a file from the previous day that contains content, a number (1–4) is appended to the name of the older file. For example, sae_debug.log.4 would be the oldest file in the rotation, sae_debug.log.1 would be the newest file in the rotation; sae_debug.log would be the active log file for SAE.

On C Series Controllers, the software compresses log files and appends the .gz suffix; for example, sae_debug.log.4.gz. Log files are stored in the /opt/UMC/component-name/var/log directory; for example, /opt/UMC/sae/var/log.

| Note: On a C Series Controller, log files are automatically rotated on a daily basis. Typically, you do not specify a maximum file size when log files are rotated. Consider whether specifying a rollover filename is needed for SRC software running on a C Series Controller. If you do configure a rollover file when files are rotated, the software creates five compressed versions of partial log files, and one uncompressed log file.

You can configure components to send log messages to the system log server (also called a syslog server) on the platform on which the SRC software is running.

If you plan to filter log messages, you should be familiar with severity levels and filters for logging before you configure system logging for a component.

#### Related Topics

- Overview of Logging for SRC Components
- Configuring a Component to Store Log Messages in a File (SRC CLI)
- Configuring ACP to Store Log Messages in a File (C-Web Interface)
- Configuring the SAE to Store Log Messages in a File (C-Web Interface)
- Configuring NIC to Store Log Messages in a File (C-Web Interface)

[Contents] [Prev] [Next] [Index] [Report an Error]