000012038 - AM 8.1 Scheduled backups fail  Backup Now fails with 'A replication or backup task is in progress'

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

Article Content

Article Number000012038
Applies ToAM 8.1.0 scheduled backup to Windows Shared Folder
RSA Authentication Manager (AM) 8.1.0
IssueThere was a problem processing your request. 
A replication or backup task is in progress.  Please wait for the current task to finish.

Backup Progress Monitor: Loading the tasks ...           Never finishes
======AdminServer/server.log=========
<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
========ops-console.log=========
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]

ps -ef shows hundreds of [ps] <defunct> as well as at least one [radius] <defunct> - also fixed in P2.
?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".?
CauseIt appears that a network problem broke the connection to the Windows File Share during a write operation of the scheduled backup.  CS reproduced this symptom at AM 8.1.2 by disabling the Windows Server Network adapter during the write operation.  However with AM 8.1 patch 2, this problem self-healed when the Windows File Share problem was fixed (enabled NIC), while customer reported at AM 8.1 no patches it never self-healed. 
Fix in AM 8.1 P2 is not documented because customer reported problem after release of P2 while running AM 8.1 base, then reported problem no longer occurred after P2 applied
 
ResolutionPatch 2 for Authentication Manager 8.1.0
 
Legacy Article IDa67320

Attachments

    Outcomes