000011622 - How to remove an unnecessary scheduler from RSA Authentication Manager 7.1 SP4 on Unix or RSA SecurID Appliance 3.0 SP4

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 5Show Document
  • View in full screen mode

Article Content

Article Number000011622
Applies ToRSA Product Set:  SecurID
RSA Product/Service Type:  Authentication Manager
RSA Version/Condition:  7.1 SP4, 3.0.4.0
Platform:  RSA SecurID Appliance or Unix
IssueThis article provides information on how to remove the scheduler from RSA Authentication Manager 7.1 SP4 on Unix or RSA SecurID Appliance 3.0 SP4.
This is required if the following error is seen:

Long running txn detected

CauseA scheduler present in Authentication Manager is no longer needed once the server is patched to SP4. This scheduler has been found to cause resource issues and replication failures and needs to be removed. An upcoming hot fix will address this, but this can also be accomplished immediately by following the steps below.
Resolution
  1. Open an SSH session to the primary.  If this is an RSA SecurID Appliance, login as emcsrv.
  2. Sudo to the rsaadmin user.
  3. Navigate to the RSA_HOME/server directory.
  4. Stop all RSA services.
  5. When back at the bash prompt, reboot the server.
login as: emcsrv
emcsrv@cs-appliance3-03.na.rsa.net's password:  <enter operating system password>
Last login: Wed Jan 20 14:15:31 2016
-bash-3.00$ sudo su - rsaadmin
Password:  <enter operating system password>
-bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/server
-bash-3.00$ ./rsaam stop all
RSA Authentication Manager:                                [  OK  ]
RSA Authentication Manager Administration Server:          [  OK  ]
RSA Authentication Manager Node Manager:                   [  OK  ]
RSA Authentication Manager Database Server:                [  OK  ]
RSA Authentication Manager Database Listener:              [  OK  ]
RSA Authentication Manager Operations Console:             [  OK  ]
RSA Authentication Manager Radius:                         [  OK  ]
RSA RADIUS Operations Console:                             [  OK  ]
-bash-3.00$ /sbin/shutdown -r now

  1. Wait for all RSA Services to come back online, and make sure you can log onto both the Security Console and Operations Console.
  2. Repeat steps 1-6 with each replica,  making sure to complete the steps on one replica before moving to the next.
  3. Access the primary machine to pause the replication.  As above, SSH to the server, login then sudo to rsaadmin then navigate to /usr/local/RSASecurity/RSAAuthenticationManager/utils.
  4. Run the command ./rsautil manage-replication -a pause.
-bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
-bash-3.00$ ./rsautil manage-replication -a pause
Enter password: <enter master password>

  1. Download the IMS_UTILS_PKG.pck file from the RSA SFTP site.
  2. Copy the file ims_utils_pkg.pck to the /tmp directory using an SFTP client and the emcsrv user credentials.
  3. Rename the existing file (Note: If the file does not exist, then this is a good indication that you are not yet running SP4, although it is also possible that the older file has been deleted):
bash-3.00$ cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
bash-3.00$ mv IMS_UTILS_PKG.pck IMS_UTILS_PKG.bak

  1. Move the new file from /tmp.  Note that Unix is case sensitive. The file may be named differently in /tmp. In addition, note the space then period at the end of the command.  This must be included.
bash-3.00$ cp /tmp/IMS_UTILS_PKG.pck .

  1. Issue the following command (notice the requirement to confirm that you wish to execute SQL during the run of the command):
bash-3.00$ ./rsautil manage-data -U rep -a exec-sql -f IMS_UTILS_PKG.pck
Enter Master password: <enter master password>
Manage Database ims-2.0.4-build20110222120046
Copyright (C) 2010 RSA Security Inc. All rights reserved.
 %% Running at: myserver.acme.net:[necq3n12] %%
===========================================
 %             Execute SQL                %
 ===========================================
 Are you sure you want to execute the SQL file [c:\temp\IMS_UTILS_PKG.pck] ? (Y/N): y
.SQL*Plus: Release 10.2.0.5.0 - Production on Fri May 27 11:47:01 2011
.Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.
.Connected to:
.Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production
.With the OLAP, Data Mining and Real Application Testing options
.Package created.
.Package body created.
.SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production
.With the OLAP, Data Mining and Real Application Testing options
Done...
bash-3.00$

  1. Repeat steps 8 - 14 with each replica,  making sure to complete the steps on one replica before moving to the next.
  2. From an SSH session on the primary, navigate to /usr/local/RSASecurity/RSAAuthenticationManager/utils and issue the following command:
bash-3.00$ ./rsautil manage-replication -a resume

  1. To ensure all resources are returned and there are no hung processes, it is recommended that the instance be rebooted following this procedure.
Notes
Legacy Article IDa54948

Attachments

    Outcomes