MustGather: Nodeagent and Deployment Manager discovery problems
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems with the IBM® WebSphere® Application Server nodeagent and Deployment Manager discovery process component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
 
Resolving the problem

1. Learning more 2. Troubleshooting 3. Collecting data 4. Analyzing data


If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.

Discovery component specific MustGather information
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 nodeagent. However, the nodeagent and the Deployment Manager are running.

The nodeagent 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 nodeagent and the Deployment Manager might not be able to talk to each other correctly.

  1. Tracing the discovery process on the nodeagent and dmgr:
    1. Stop all Application Server processes (no Java processes).

    2. Modify the server.xml files for both nodeagent 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/cellname/nodes/nodename/servers/dmgr

        2. Find the TraceService XML tag section.

        3. Modify the startupTraceSpecification entry to look like the following:
          • For V5.0 and V5.1:

            com.ibm.ws.management.*=all=enabled

          • For V6.0 and V6.1:

            com.ibm.ws.management.*=all

        4. Make sure enable is set to true.

      2. Enable discovery tracing on the nodeagent:
        1. Edit the server.xml file for the nodeagent located in the following directory:

          BASE_PROFILE/config/cells/cellname/nodes/nodename/servers/nodeagent

        2. Find the TraceService XML tag section.

        3. Modify the startupTraceSpecification entry to look like the following:
          • For V5.0 and V5.1:

            com.ibm.ws.management.*=all=enabled

          • For V6.0 and V6.1:

            com.ibm.ws.management.*=all

        4. Make sure enable is set to true.

    3. Clear all the files in the following directories:
      1. For V5.0 and V5.1:

        install_root/logs

      2. For V6.0 and V6.1:

        BASE_PROFILE/logs

        and

        ND_PROFILE/logs

    4. Issue the following command:

      netstat -an > before.txt

    5. Start the nodeagent and dmgr.

    6. Open the administrative console and navigate to System administration > Nodes to see if the node is still has a status of Unknown.

    7. Issue the following command:

      netstat -an > after.txt

    8. Stop the nodeagent and dmgr.

    9. Run the collector tool on both Network Deployment and base.
  2. Follow directions in MustGather: Read first to open a PMR and send data to IBM® Support.


What to do Next?
Once you have collected the preceding information, you can begin Analyzing the data or simply submit the diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to Discovery, search the WebSphere Application Server support site.
 
Related information
Submitting information to IBM Support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1196220
IBM Group: Software Group
Modified date: Jun 6, 2006