RSA Authentication Manager 8.x: Large Disk Space Used by Logs
Originally Published: 2018-02-14
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
Cause
This is due to migration from 7.1, the database has the location for the archive log incorrectly set as /opt/am/server/server.
Resolution
Unless the Archive now or schedule archive page is modified with different parameters and saved, the database value doesn't get updated for the log location.
Workaround
Notes
Once the archive job runs successfully, check the location /opt/rsa/am/Log_archive location for the new files.
After this, the automated jobs should purge the data periodically as expected.
Related Articles
Running out of disk space on KCA system 25Number of Views Examining the Disk Space Usage on Authentication Manager 8.x 743Number of Views How to enable Verbose logging without consuming your Disk Space on RSA Authentication Manager 8.x 219Number of Views RSA Authentication Manager 8.x requires more disk space 1.81KNumber of Views Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle 198Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?