on Jun 14, 2016Article Content
| Article Number | 000033158 | ||||||
| Applies To | RSA Product Set : SecurID RSA Product/Service Type : RSA Authentication Manager RSA Version/Condition : AM 8.1 or 8.1 Service Pack 1 or later Platform : SUSE Enterprise Linux | ||||||
| Issue | RSA Authentication Manager server fails to start the RSA Services after a Reboot. RSA Authentication Manager service unavailable on Primary server.  | ||||||
| Cause | A corrupted or a missing rsaserv file in the server directory of RSA Authentication Manager 8.1 due to reasons below
| ||||||
| Resolution | A) For a RSA Authentication Manager 8.1 Deployment with a Primary Server down and a working Replica Server 1. Using Winscp or Filezilla client connect to RSA Authentication Manager 8.1 Replica server 2. Navigate to /opt/rsa/am/server directory 3. Copy the rsaserv file from RSA Authentication Manager 8.1 Replica server to the local system as below  4. Again Using WinSCP or Filezilla client connect to RSA Authentication Manager 8.1 Primary server where RSA Services fail to start 5. Copy the rsaserv file from local system to RSA Authentication Manager 8.1 Primary server as below  6. Login as root on the console of the VM of RSA Authentication Manager 8.1 Primary server 7. Reboot the RSA Authentication Manager 8.1 Primary server 8. Now the RSA Authentication Manager Services will start automatically as below  9. Now both Security Console (SC) and Operations Console (OC) of RSA Authentication Manager 8.1 server are accessible B) For a Standalone RSA Authentication Manager 8.1 Deployment 1. If the RSA Authentication Manager 8.1 Deployment has only a Primary server, contact RSA Support for fresh copies of the rsaserv file 2. Repeat Step 5 to Step 9 as above to resolve the issue | ||||||
| Notes | Contacting RSA Customer Support
|