SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
New Contributor
New Contributor

Can the time taken to 'restart' the RSA Authentication Manager be reduced?

With the goal of trying to reduce the length of time the RSA Primary is 'offline', I have used different settings for my VMWare RSA VA.

The time taken with 2 CPU and 8GB of Memory was the same as 4 CPU and 8GB of Memroy.

The time taken with 4 CPU and 16GB of Memory was the same as the group above.

It was/is, always just over 10mins.

There is also a pause of 1min 30sec during every restart, where it says on the console "a start job is running for swap.device".

So my question is 3 fold.

1) Is it possible to reduce the restart time of the VA, and if so how?

2) Is it possible to remove or reduce the swap.device stage of the restart?

3) Is there anywhere in the RSA web consoles that shows the Memory given to the VA (like a sysinfo)?


Labels (1)
1 Reply
Moderator Moderator


For the Authentication Manager services to take about ten minutes to start sounds pretty accurate. Consider it the perfect amount of time to make a fresh cup of coffee or just get out of your office chair to stretch! 😊

Some items for you to check that might be helpful:

  • How big is your database? How many users are in your internal and external identity sources? A larger database may impact the start of Authentication Manager services.
  • How much do you log? Is verbose logging enabled? If so, please turn off verbose logging.
  • Speaking of logging, do you archive your logs? Archiving your logs to offline and taking them off the server will also help with the restart of services. Take a look at this article on understanding and managing log archival maintenance for Authentication Manager 8.x.
  • We do not have an option in the Authentication Manager GUIs to show memory information. 
  • What is the output from running vmstat to check your virtual memory?
  • You can also try running vacuumdb, a utility for cleaning a PostgreSQL database. It will also generate internal statistics used by the PostgreSQL query optimizer. To run the utility, you will need to connect to the database using pgSQL. Be sure to back up your database before running this command. A snapshot of your virtual machine is nice, but also take a backup from the Operations Console (Maintenance > Backup and Restore > Backup Now).
  • Finally, take a look at the Authentication Manager 8.7 Performance and Scalability Guide. Chapter 2 goes over performance factors for Authentication Manager 8.7.


Best regards,