Article Number | 000030531 |
Applies To | Data Protection Manager Appliance 3.5.x |
Issue | Missing cluster information on the database schema rkm_appliance_user. The appliance console does not show other cluster members in a supported browser: 1. Click on the Clustering tab 2. Select the drop down Manage Cluster category 3. Notice that the node(s) that were joined during initialization do not appear in the details. However, you go to another member of the cluster in the same place and see all the details. |
Cause | The initialization completes successfully during a join and does not catch the error.
ERROR - com.rsa.appliance.sys.service.impl.ReplicationServiceUtil.updateNodeDTOToRemoteNode(ReplicationServiceUtil.java:1182) : Error while setting up replication. com.rsa.appliance.exception.BusinessServiceException at com.rsa.appliance.sys.service.impl.ReplicationServiceUtil.executeRemotePersist(ReplicationServiceUtil.java:1163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.rsa.appliance.sys.communication.MethodDispatchHandler.execute(MethodDispatchHandler.java:89) at com.rsa.appliance.sys.communication.ApplianceReceiverAdapter.handleExecuteCall(ApplianceReceiverAdapter.java:123) at com.rsa.appliance.sys.communication.ApplianceReceiverAdapter.handleSyncCall(ApplianceReceiverAdapter.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:302) at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:326) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:447) at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:354) at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:230) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:556) at org.jgroups.JChannel.up(JChannel.java:716) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1026) at org.jgroups.protocols.pbcast.StreamingStateTransfer.up(StreamingStateTransfer.java:262) at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:881) at org.jgroups.protocols.AUTH.up(AUTH.java:84) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:656) at org.jgroups.protocols.UNICAST.up(UNICAST.java:317) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:597) at org.jgroups.protocols.ENCRYPT.passItUp(ENCRYPT.java:453) at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:579) at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:438) at org.jgroups.protocols.BARRIER.up(BARRIER.java:102) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:140) at org.jgroups.protocols.FD.up(FD.java:273) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:284) at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) at org.jgroups.protocols.Discovery.up(Discovery.java:354) at org.jgroups.protocols.TP.passMessageUp(TP.java:1174) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1709) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1691) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) |
Resolution | If the missing node data can be found on other nodes of the cluster there is a script that can be run on the appliance that can be used to repair the node. Open a support case with RSA support and they will help provide the script. |
Notes | The script is targeted to be included in the DPM 3.5.2.4 release |