IBM Support

MustGather: Nodeagent and Deployment Manager discovery problems

Troubleshooting


Problem

Collecting data for problems with the IBM WebSphere Application Server node agent and deployment manager discovery process component. Gathering this MustGather information before you call IBM support can help you understand the problem and save time analyzing the data.

Resolving The Problem


Tab navigation

Collecting data for problems with the IBM WebSphere Application Server node agent and Deployment Manager discovery process component. Gathering this MustGather information before you call IBM support can help you understand the problem and save time analyzing the data.

  • Read first and related MustGathers

    MustGather: Read first for WebSphere Application Server and Liberty

    Administrative console problem Cluster ripple start problem Deployment problem JMX problem Profile wizard problem Start problem Stop problem System administration problem WASService problem (Windows only) WSAdmin problem

  • Exchanging data with IBM Support

    To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:

    • IBM Support Assistant (ISA)
    • Service Request (SR)
    • Email
    • FTP to the Enhanced Customer Data Repository (ECuRep)

    Instructions for exchanging information with IBM Support

  • Collecting data manually
    In the administrative console under System Administration > Nodes, the node in question has a status of Unknown, or it is using wsadmin and is not able to get the $AdminControl MBean object for the node agent. However, the node agent and the Deployment Manager are running.

    The node agent and deployment manager must discover each other to have synchronization and administrative commands work properly on the base node. There are multiple reasons why the node agent and the deployment manager might not be able to talk to each other correctly.
     

    Tracing the discovery process on the node agent and dmgr:

    1. Stop all Application Server processes (no Java processes).
       
    2. Modify the server.xml files for both node agent and dmgr:
      1. Enable discovery tracing on the dmgr:
        1. Edit the server.xml file for the dmgr located in the following directory:

          ND_PROFILE/config/cells/cell_name/nodes/node_name/servers/dmgr
        2. Find the TraceService XML tag section.
           
        3. Modify the startupTraceSpecification entry to look like the following:

          com.ibm.ws.management.*=all
        4. Make sure enable is set to true.
           
      2. Enable discovery tracing on the node agent:
        1. Edit the server.xml file for the node agent located in the following directory:

          BASE_PROFILE/config/cells/cell_name/nodes/node_name/servers/nodeagent
           
        2. Find the TraceService XML tag section.
           
        3. Modify the startupTraceSpecification entry to look like the following:

          com.ibm.ws.management.*=all
        4. Make sure enable is set to true.
           
    3. Clear all the files in the following directories:

      BASE_PROFILE/logs


      and


      ND_PROFILE/logs
    4. Issue the following command:

      netstat -an > before.txt
       
    5. Start the node agent and dmgr.
       
    6. Open the administrative console and navigate to System administration > Nodes to see if the node still has a status of Unknown.
       
    7. Issue the following command:

      netstat -an > after.txt
       
    8. Stop the node agent and dmgr.
       
    9. Run the collector tool on both Network Deployment and base.

    10.  Follow directions in MustGather: Read first to open a PMR and send data to IBM Support.
     
    What to do Next?

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"System Management\/Repository","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.5;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 July 2022

UID

swg21196220

Page Feedback