Thursday, 19 May 2016

Websphere Node agent Synchronization Issue

TroubleShooting: Synchronization problem with Node agent



Issue: Node status shows not synchronized in the  administrative console


Error message:
[18/05/16 14:56:23:059 EST] 000000a3 NodeSyncTask  A   ADMS0036E: The configuration synchronization failed.
[18/05/16 14:56:24:088 EST] 000000a4 NodeSync      E   ADMS0012E: The system is unable to create an administrative client connection: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr
 at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:532)
 at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:407)
 at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:248)
 at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)
 at java.lang.Thread.run(Thread.java:790)
.
[18/05/16 14:56:24:088 EST] 000000a4 NodeSync      E   ADMS0005E: The system is unable to generate synchronization request: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr
 at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:532)
 at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:407)
 at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:248)
 at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)
 at java.lang.Thread.run(Thread.java:790)


Environment details: WAS 8.5.5.9 on Windows,  with both DMGR and Node agent created on the same system.


Steps tried to resolve Synchronization issue
1.      Stopped the Node agent and did a manually sync using the command syncNode.bat. Sync was successful. Started the node agent but on the console, still it showed the status as not synchronized.

2.      Tried to check the NODE_DISCOVERY_ADDRESS port for the node agent whether it is listening using the command:

 netstat -anbo | findstr "NODE_DISCOVERY_ADDRESS port number "

3.      NODE_DISCOVERY_ADDRESS port number was not listening though the node agent was running.

4.      Rebooted the Windows server and it fixed the issue as there would be some windows policy set and applied and requires a reboot.
Now Node agent status shows synchronized.


No comments:

Post a Comment