Appliance 3.0.4.0
1. Open an SSH session to the primary and login as emcsrv
login as: emcsrv
-bash-3.00$ sudo su - rsaadmin
Password: ********
2. Change to the (RSAHome)/server directory:
bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/server
and then Stop all RSA Services
./rsaam stop all (notice it starts with dot-slash)
Reboot the appliance:
/sbin/shutdown -r now
3. Wait for all RSA Services to come back online, and make sure you can log onto both the Security Console and Operations Console.
4. Repeat steps 1-3 with each Replica, one-at-a-time.
5. Access the primary machine to pause the replication:
Open an SSH session to the primary and login as emcsrv
login as: emcsrv
-bash-3.00$ sudo su - rsaadmin
Password: ********
Note: you will be prompted for the master password when running these commands.
bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
6. Copy the file scheduler_check.sql to the /tmp directory using an SFTP client using the emcsrv credentials. A link to this file is at the bottom of this solution.
8. Move the new file from the tmp directory:
Note that linux is case sensitive. The file may be named differently in the tmp directory. In addition, note the space then period at the end of the command - this must be included.
bash-3.00$ cp /tmp/scheduler_check.sql .
9. Issue the following commands (notice the requirement to confirm that you wish to execute SQL during the run of the command):
bash-3.00$ cd ..
bash-3.00$ ./rsautil manage-data -U rep -a exec-sql -f /diagnostics/scheduler_check.sql
10. Repeat steps 6 through 9 on each replica, one-at-a time
11. Issue the following command on the primary:
bash-3.00$ ./rsautil manage-replication -a resume
To ensure all resources are returned and there are no hung processes it is recommended that the instance be rebooted following this procedure.
This should only be done if the device is at SP4. DO NOT do this on any previous versions!
For a similar solution under Windows, See How to remove an unnecessary scheduler (in SP4 only)
Note: the fix is expected to be included in SP P5, but if you are having the symptoms, you should still do steps 1-4 before applying P5 (or later) . AM-22074 AM-22102
Download the file IMS_UTILS_PKG.pck here: https://sftp.rsa.com/human.aspx?Username=support&password=Password1&arg01=713010015&arg12=downloaddirect&transaction=signon&quiet=true
Related Articles
Unable to see orgs after in place upgrade from 5.7.3 to 6.0.2.1 SP2 13Number of Views Obtain the Identity Router Image 78Number of Views Authentication Manager Log Messages (16291-16355) 152Number of Views Requesting access to RSA Authentication Manager Google Compute Engine (GCE) image file for Google Cloud Platform (GCP) env… 94Number of Views Users from an external identity source are listed as disabled in the RSA Authentication Manager 8.x Security Console 229Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide