Topic
  • 2 replies
  • Latest Post - ‏2013-04-27T04:55:11Z by aditya483
aditya483
aditya483
6 Posts

Pinned topic NodeSync E ADMS0005E

‏2013-04-26T14:49:55Z |

I got a cluster with two nodes. The admin console shows the nodes to be stopped even though they are running, and I am unable to synchronize the nodes. The following error is written in SystemOut.log file for nodeagent:

 

[4/26/13 17:27:17:103 GMT+05:30] 00000b0e 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:521)
        at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:396)
        at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:261)
        at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:181)
        at java.lang.Thread.run(Thread.java:811)
 

Need assistance in resolving this issue. Appreciate your help!

  • alle
    alle
    1 Post

    Re: NodeSync E ADMS0005E

    ‏2013-04-26T18:04:02Z  

     

    Check the below:

    1) Can you ping the Dmgr from the node?

    2) Are there any other errors during dmgr or nodeagent start up? Check SystemOut.log and startServer.log for errors on the respective machines.

     

    
    PS: The postings on this site are my opinions and do not necessarily align with IBM's stance or strategies on the subject.
    
     
  • aditya483
    aditya483
    6 Posts

    Re: NodeSync E ADMS0005E

    ‏2013-04-27T04:55:11Z  
    • alle
    • ‏2013-04-26T18:04:02Z

     

    Check the below:

    1) Can you ping the Dmgr from the node?

    2) Are there any other errors during dmgr or nodeagent start up? Check SystemOut.log and startServer.log for errors on the respective machines.

     

    <pre class="ctntValue" dir="ltr"> PS: The postings on this site are my opinions and do not necessarily align with IBM's stance or strategies on the subject. </pre>
     

    Hi Alle,

    Thanks for your response.

    Yes i am able to ping the dmgr from the node. The Dmgr and nodeagents have started successfully without any exceptions in the SystemOut.log and startServer.log files.

    Nodeagent start file:

    [4/26/13 20:25:11:000 GMT+05:30] 0000001b VSyncAlgo1    I   DCSV2004I: DCS Stack DefaultCoreGroup at Member MINEPHPRDFINWAS1Cell01\MINEPHPRDFINWAS1Node01\nodeagent: Vie
    w synchronization completed successfully. The View Identifier is (20:0.MINEPHPRDFINWAS1Cell01\MINEPHPRDFINWAS1CellManager01\dmgr). The internal details are None.
    [4/26/13 20:25:11:015 GMT+05:30] 0000001c CoordinatorIm I   HMGR0228I: The Coordinator is not an Active Coordinator for core group DefaultCoreGroup.
    [4/26/13 20:25:11:032 GMT+05:30] 0000001c CoordinatorIm I   HMGR0218I: A new core group view has been installed. The core group is DefaultCoreGroup. The view identifier
     is (21:0.MINEPHPRDFINWAS1Cell01\MINEPHPRDFINWAS1CellManager01\dmgr). The number of members in the new view is 5.
    [4/26/13 20:25:11:034 GMT+05:30] 0000001c CoreGroupMemb I   DCSV8050I: DCS Stack DefaultCoreGroup at Member MINEPHPRDFINWAS1Cell01\MINEPHPRDFINWAS1Node01\nodeagent: New
     view installed, identifier (21:0.MINEPHPRDFINWAS1Cell01\MINEPHPRDFINWAS1CellManager01\dmgr), view size is 5 (AV=5, CD=5, CN=5, DF=5)
    [4/26/13 20:25:11:059 GMT+05:30] 00000a76 ViewReceiver  I   DCSV1033I: DCS Stack DefaultCoreGroup at Member MINEPHPRDFINWAS1Cell01\MINEPHPRDFINWAS1Node01\nodeagent: Con
    firmed all new view members in view identifier (21:0.MINEPHPRDFINWAS1Cell01\MINEPHPRDFINWAS1CellManager01\dmgr). View channel type is View|Ptp.