Scheduled backups fail and Backup Now fails with 'A replication or backup task is in progress' in RSA Authentication Manager 8.1
Originally Published: 2014-08-11
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1
Issue
- The following message displays when attempting a scheduled backup of clicking Backup Now:
There was a problem processing your request.
A replication or backup task is in progress. Please wait for the current task to finish.
A replication or backup task is in progress. Please wait for the current task to finish.
- The Backup Progress Monitor loading the tasks but never finishes.
- The /opt/rsa/am/AdminServer/server.log has the following error:
<Jul 20, <BEA-090166> <Failed to load identity keystore
<BEA-101083> <Connection failure. java.io.IOException: A complete message could not be read on socket: 'weblogic.socket.JSSEFilterImpl@1cc41d54 with delegate: weblogic.servlet.internal.MuxableSocketHTTP@1ccf04f6:Socket[addr=/172.21.155.70,port=42737,localport=7002] - idle timeout: '60000' ms, socket timeout: '25000' ms', in the configured timeout period of '60' secs
<BEA-101019> <[ServletContext@451376777[app:am-app module:/remoting path:null spec-version:3.0]] Servlet failed with an IOException java.net.SocketTimeoutException: Read timed out
<BEA-101083> <Connection failure. java.io.IOException: A complete message could not be read on socket: 'weblogic.socket.JSSEFilterImpl@1cc41d54 with delegate: weblogic.servlet.internal.MuxableSocketHTTP@1ccf04f6:Socket[addr=/172.21.155.70,port=42737,localport=7002] - idle timeout: '60000' ms, socket timeout: '25000' ms', in the configured timeout period of '60' secs
<BEA-101019> <[ServletContext@451376777[app:am-app module:/remoting path:null spec-version:3.0]] Servlet failed with an IOException java.net.SocketTimeoutException: Read timed out
- The opt/rsa/am/logs/ops-console.log shows:
2014-03-11: Unable to get configuration data for scope 0000-Global-0000 and section auth_manager.backup.scheduler.job%
Caused by: org.springframework.dao.DataAccessResourceFailure Exception: PreparedStatementCallback; SQL [SELECT NAME, VALUE FROM IMS_CONFIG_VALUE WHERE INSTANCE_ID=? AND NAME LIKE ?]; Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.; nested exception is org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
2014-05-16 [[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] GUILog.traceException(587) | exception: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://<Server>.<subdomain>.local:7082: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out; No available router to destination]
Caused by: org.springframework.dao.DataAccessResourceFailure Exception: PreparedStatementCallback; SQL [SELECT NAME, VALUE FROM IMS_CONFIG_VALUE WHERE INSTANCE_ID=? AND NAME LIKE ?]; Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.; nested exception is org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
2014-05-16 [[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] GUILog.traceException(587) | exception: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://<Server>.<subdomain>.local:7082: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out; No available router to destination]
- Running ps -ef shows hundreds of [ps] <defunct> processes, as well as at least one [radius] <defunct> - also fixed in P2.
- The following message is seen in the Operations Console UI:
Attention! The following critical system event occurred: Your deployment is at risk. A backup has not been created successfully in the last 7 days. Log on to the Operations Console, and select "Backup and Restore > Back Up Now" or "Backup and Restore > Schedule Backups".
Cause
RSA Customer Support reproduced this symptom with RSA Authentication Manager 8.1 patch 2 (8.1.0.2.0) by disabling the Windows Server Network adapter during the write operation.
However with Authentication Manager 8.1.2.0.0, this problem self-healed when the Windows File Share problem was fixed (enabled NIC), while customer reported at Authentication Manager 8.1.0.0.0 with no patches that it never self-healed.
The fix in Authentication Manager 8.1 patch 2 is not documented because the customer reported the problem after the release of patch 2 while running Authentication Manager 8.1 base, then reported problem no longer occurred after patch 2 was applied
Resolution
Related Articles
Backing Up User Profiles for HTTP Federation Applications 104Number of Views Create a Backup Using Schedule Backups 113Number of Views Failed to create a backup on Windows shared folder for RSA Authentication Manager 8.1 289Number of Views Create a Backup Using Back Up Now 137Number of Views Replacing the Console Certificate 244Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA MFA Agent 2.4.3 for Microsoft Windows Group Policy Object Template Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.4.3 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?