ViPR SRM: Unable to access the frontend console

When using Internet Explorer browser to log in, the ViPR SRM frontend console fails to load with the error:

This page can't be displayed

When using Google Chrome browser to log in, users got the error:

This site can't be reached

Tomcat's Catalina log had these errors:

SEVERE: Attempt to login to tomcat realm as 'ws-user' has failed from 'xx.xx.xx.xx'.
Jan 31, 2019 7:44:08 AM com.sun.xml.ws.server.sei.EndpointMethodHandler invoke
SEVERE: can't get valid user
java.lang.SecurityException: can't get valid user
     at com.watch4net.apg.v2.remote.security.ApplicationUserMapperProvider.getUser(ApplicationUserMapperProvider.java:61)
 com.watch4net.apg.v2.remote.security.ApplicationUserMapperProvider.getUser(ApplicationUserMapperProvider.java:59)
     ... 53 more
Caused by: com.watch4net.apg.gui.master.accessor.MasterDataAccessException: Unable to load user `ws-user` from master database!
     at com.watch4net.apg.gui.master.accessor.jdbc.JdbcMasterUserAccessor.load(JdbcMasterUserAccessor.java:396)

Tomcat could not load or access ws-user from the active database.

In one incident where this happened, restarting all ViPR SRM services on the frontend resolved the issue.

Instructions:

1. Putty into the frontend
2. Go to /opt/APG/bin
3. Run the following.

   ./manage-modules.sh service stop all

4. Run the following

   ./manage-modules.sh service start all

5. Confirm that the user can connect to the ViPR SRM console successfully.

In a similar scenario where the ViPR SRM frontend console fails to load, the Catalina log may contain slightly different errors:

SEVERE: Error authentication user ws-user
com.watch4net.apg.gui.master.accessor.MasterDataAccessException: Unable to access users from master database!
    at com.watch4net.apg.gui.master.accessor.jdbc.JdbcMasterUserAccessor.containsAlternate(JdbcMasterUserAccessor.java:305)....


Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
    at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)