Unable to place RSA Authentication Manager 8.x troubleshooting logs larger than 2GB on SFTP for troubleshooting
Originally Published: 2018-10-29
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.2.1, 8.2, 8.3
Issue
Cause
Resolution
Workaround
Notes
- audit_runtime refers to authentication activities
- audit_admin refers to administrative activites by Super Admin and Help Desk administrators
- system_ refers to system messages and errors
For example, the three archive log file types for 29 June 2018 and their digital signature files;
/opt/rsa/am/server/audit_admin_2018-06-29_0.log /opt/rsa/am/server/audit_admin_2018-06-29_0.log.sig /opt/rsa/am/server/audit_runtime_2018-06-29_0.log /opt/rsa/am/server/audit_runtime_2018-06-29_0.log.sig /opt/rsa/am/server/system_2018-06-29_0.log /opt/rsa/am/server/system_2018-06-29_0.log.sig
While these files may be important for historic and legal reasons, they would not be helpful in troubleshooting a recent problem and should not be included in Troubleshooting logs. Remove them from the .zip file to save space,
Related Articles
Error: 'media.sig - failed: no digest for this file in media signature file' 9Number of Views How to capture a web browser console log for troubleshooting purposes 33Number of Views Unable to view any encrypted documents 1Number of Views RSA MFA Agent 9.0 for PAM - Installation and Configuration Guide for Oracle and RHEL (German) 14Number of Views Distribute Software Tokens Using File-Based Provisioning 79Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?