How to manage logs in DCImanager 6

Description

By default, logs are stored and rotated using the journald. For more details, refer to the article Platform log files.

Over time, the volume of logs increases, which can lead to full disk space consumption. To prevent this and ensure the availability of logs for required periods, it is necessary to configure their rotation and retention policy in journald.

Proper logging configuration allows you to:

• optimize disk space usage;
• control the retention period of log files.

Diagnostics

To assess free space before changing settings, evaluate the current log volume by running:

journalctl --disk-usage

Solution

To configure log rotation:

1. Connect to the server with the platform via SSH. For more information about connecting via SSH, see Workstation setup.
2. Open the file /usr/lib/systemd/journald.conf.d/dci.conf for editing:
   Default file contents

   [Journal]
   Storage=persistent
   Compress=yes
   SystemMaxFileSize=500M
   SystemMaxUse=20G

   Comments

   Configuration parameters set by the platform:

   • Storage=persistent — store files on disk;
   • Compress=yes — compress data in logs;
   • SystemMaxFileSize=500M — the maximum size of the log file is 500 Mb. When this value is reached, logs are rotated;
   • SystemMaxUse=20G — the maximum disk size for storing logs is 20 GB. When this value is reached, older files will be deleted.
3. Edit the file:
   
   • to increase the log retention period, increase the value of the SystemMaxUse parameter;
   • to reduce the space occupied by logs, decrease the values of the SystemMaxUse and SystemMaxFileSize parameters.
     
4. Restart the systemd-journald service to apply the changes:
   

   systemctl restart systemd-journald

To immediately free up space, you can manually clean up logs older than a specified time. For example, to delete all logs created more than 12 hours ago, run the command:

journalctl --vacuum-time=12h