addNode fails - Websphere

This is a discussion on addNode fails - Websphere ; Hi all, I am facing some issue while trying to federate primary node in the deployment manager, In my case my DMGR is on the same machine as the Primary Node, The addnode always fails with following message ..............................." [1/25/08 ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: addNode fails

  1. addNode fails

    Hi all,

    I am facing some issue while trying to federate primary node in the deployment manager, In my case my DMGR is on the same machine as the Primary Node, The addnode always fails with following message ..............................."

    [1/25/08 19:24:30:367 GMT+05:30] 0000000a AdminTool A ADMU0014I: Adding node CNDAE configuration to cell: etmgrc1
    [1/25/08 19:26:00:786 GMT+05:30] 0000000a NodeFederatio E ADMU0011E: Error creating configuration in the cell repository com.ibm.websphere.management.filetransfer.client.T ransferFailedException: 409 Conflict (for: /tmp/CNDAE__31748.car).
    at com.ibm.ws.management.filetransfer.client.FileTran sferClientImpl.uploadFileInternal(FileTransferClie ntImpl.java(Compiled Code))
    at com.ibm.ws.management.filetransfer.client.FileTran sferClientImpl.uploadFile(FileTransferClientImpl.j ava:420)
    at com.ibm.ws.management.filetransfer.client.FileTran sferClientImpl.uploadFile(FileTransferClientImpl.j ava:305)
    at com.ibm.ws.management.tools.NodeFederationUtility. copyToServer(NodeFederationUtility.java:2986)
    at com.ibm.ws.management.tools.NodeFederationUtility. doUploadConfigDocumentsToDMgr(NodeFederationUtilit y.java:876)
    at com.ibm.ws.management.tools.NodeFederationUtility. doAllConfigUpdates(NodeFederationUtility.java:665)
    at com.ibm.ws.management.tools.NodeFederationUtility. doAddNode(NodeFederationUtility.java:608)
    at com.ibm.ws.management.tools.NodeFederationUtility. runTool(NodeFederationUtility.java:439)
    at com.ibm.ws.management.tools.AdminTool.executeUtili ty(AdminTool.java:229)
    at com.ibm.ws.management.tools.NodeFederationUtility. main(NodeFederationUtility.java:246)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:219)
    at java.lang.Thread.run(Thread.java:570)

    [1/25/08 19:26:00:806 GMT+05:30] 0000000a AdminTool A ADMU0027E: An error occurred during federation 409 Conflict (for: /tmp/CNDAE__31748.car).; rolling back to original configuration.
    [1/25/08 19:26:00:821 GMT+05:30] 0000000a AdminTool A ADMU0211I: Error details may be seen in the file: /websphere/etize/AppServer/profiles/wp_profile/logs/addNode.log
    [1/25/08 19:26:00:822 GMT+05:30] 0000000a AdminTool E ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminExcept ion: com.ibm.websphere.management.filetransfer.client.T ransferFailedException: 409 Conflict (for: /tmp/CNDAE__31748.car).
    at com.ibm.ws.management.util.Utils.makeAdminExceptio n(Utils.java:350)
    at com.ibm.ws.management.tools.NodeFederationUtility. runTool(NodeFederationUtility.java:444)
    at com.ibm.ws.management.tools.AdminTool.executeUtili ty(AdminTool.java:229)
    at com.ibm.ws.management.tools.NodeFederationUtility. main(NodeFederationUtility.java:246)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:219)
    at java.lang.Thread.run(Thread.java:570)
    Caused by: com.ibm.websphere.management.filetransfer.client.T ransferFailedException: 409 Conflict (for: /tmp/CNDAE__31748.car).
    at com.ibm.ws.management.filetransfer.client.FileTran sferClientImpl.uploadFileInternal(FileTransferClie ntImpl.java(Compiled Code))
    at com.ibm.ws.management.filetransfer.client.FileTran sferClientImpl.uploadFile(FileTransferClientImpl.j ava:420)
    at com.ibm.ws.management.filetransfer.client.FileTran sferClientImpl.uploadFile(FileTransferClientImpl.j ava:305)
    at com.ibm.ws.management.tools.NodeFederationUtility. copyToServer(NodeFederationUtility.java:2986)
    at com.ibm.ws.management.tools.NodeFederationUtility. doUploadConfigDocumentsToDMgr(NodeFederationUtilit y.java:876)
    at com.ibm.ws.management.tools.NodeFederationUtility. doAllConfigUpdates(NodeFederationUtility.java:665)
    at com.ibm.ws.management.tools.NodeFederationUtility. doAddNode(NodeFederationUtility.java:608)
    at com.ibm.ws.management.tools.NodeFederationUtility. runTool(NodeFederationUtility.java:439)
    ... 9 more

    ................................"" ..
    I searched IBM technotes, wherein they asked to clear tmp directories for a similar issue

    2. I cleared all the tmp locations in WebSphere and the tmp mount point, and there is no CNDA*.car present in system before I run the command in any of tmp directory

    3. After that I enabled trace and run the command again, It is giving me some socket error, where it appears to be some error with parsing the URL

    [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status line


    com.ibm.websphere.management.exception.ConnectorNo tAvailableException: Failed to get a connection with IP address associated with hostname CNDAETIZAPZP01.airtelworld.in

    4. I have my hostfile /etc/hosts file updates with the ipaddress shortname fully qualified domainname in file
    and I can ping the machine with ip address, hostname as well as fully qualified name.

    Any Thoughts ..

    Regards,
    Seema

  2. Re: addNode fails

    dmgr should be running during addnode. also ensure that you pass the right soap port (i.e. dmgr soap port) and hostname (localhost in your case).

  3. Re: addNode fails

    Managed to solve it by increasing the number of TCP IP connections in the DMGR condole.

    Thanks
    Seema

  4. Re: addNode fails

    Hello
    I have the same problem. Do you can tell me what part of the change dmgr
    the configuration of tcp connections?

+ Reply to Thread