RAAS Log Rotation Issue Due to Incorrect Configuration

Products

• VMware Aria Suite

Issue/Introduction

The RAAS log file (raas.log) was not rotating, even after reaching 61 GB in size. As a result, the log files became inaccessible, which hindered further review and troubleshooting.

Environment

Aria Config 8.X

Cause

Upon investigation, it was found that the log rotation configuration was referencing the wrong log file. The configuration in /etc/logrotate.d/raas.logrotate was pointing to "raas" instead of the actual "raas.log" file as configured in the RAAS configuration file (/etc/raas/raas). This misconfiguration prevented the log file from being properly rotated, allowing it to grow excessively.

Resolution

1. Review the log rotation configuration file located at /etc/logrotate.d/raas.logrotate.
2. Correct the file reference in the configuration from "raas" to "raas.log" (the actual log file name).
3. Restart the RAAS services to apply the updated log rotation settings.
4. Verify that the log rotation is now functioning correctly by checking the log file size and rotation behavior.

After the changes were made and the RAAS services restarted, the log rotation issue was resolved, and logs began rotating as expected, preventing further excessive log growth.