Authentication Manager 8.x

When choosing to download troubleshooting logs for a support issue, the internal script gathers everything in /opt/rsa/am/server/logs. This can include many unnecessary files that are part of the normal use of Authentication Manager. You will see these rotated logs in the directory with extensions like .log00001, log00002, etc.  See the article on removing extraneous files from /opt/rsa/am/server/logs that can be slowing performance in Authentication Manager 8.x for more information. All of these extra files increase the size of the troubleshooting log bundle, making it harder to save locally and then upload to RSA Support.

The script attached to this article allows you to gather just the active logs when opening a support call. It harvests all current active logs from /opt/rsa/am/server/logs, prompts for a password to encrypt the file then creates an output a file in /tmp called am_logs_tarball_yyyymmdd.zip that can be uploaded to a support case.

To run the script and create the .zip, follow the steps below:

1. Copy the attached gather_am_current_log.sh to any directory on the Authentication Manager server from where you were asked to gather logs. Depending on this issue reported, this may be done on the primary and also on any replica(s) having an issue.
2. Run chmod 755 gather_am_current_log.sh to ensure that it is executable.
3. Run ./gather_am_current_log.sh.
4. Navigate to /tmp and look for the am_logs_tarball_yyyymmdd.zip.
5. Use a file transfer program to copy the .zip from the server.
6. Attach it to an open support case via the RSA Community.