IBM Support

MustGather: Cluster RippleStart problems with WebSphere Application Server



Collecting data for Cluster RippleStart problems with the IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving The Problem

Collecting data manually

  1. Stop all servers and clear the entire log directory for each server. The log directory for each server can be found in the following location for each profile:

  2. Set tracing of the Admin component for the dmgr, nodeagent, and all cluster members for the cluster:
    • If the problem is general issue with RippleStart:
      Trace setting for Deployment Manager (server: dmgr)

      Trace setting for Node Agent (server:nodeagent)**=all

      Note: You do not need Application Server traces unless you suspect a problem in a cluster member.
    • If the problem is more specific to a 'Cluster Member' during RippleStart:
      Trace setting for the Deployment Manager (server: dmgr)*=all

      Trace setting for the Node Agent (server:nodeagent)**=all

      Trace setting for the Application Server (cluster member)**=all
    • Note:
      • If the problem is with a particular node in the cluster, then traces would only be needed from that node's nodeagent and its application server plus dmgr.
      • If the problem is with a particular cluster member, then traces would only be needed from that application server plus that cluster member's nodeagent and dmgr.

        Make sure the trace output Maximum File Size limit is large (20 MB recommended) and the Maximum Number of Historical Files is greater than 5.
    • For addititional information on enabling tracing, see the following technote: Setting up a trace.

  3. Recreate the problem by issuing the RippleStart on the desired Cluster.
  4. Run the Collector tool on all installs. See the appropriate Information Center for additional information on running the Collector tool.
  5. Send the diagnostic information to IBM support, using the instructions in this technote: Exchanging information with IBM Technical Support for problem determination.
For a listing of all technotes, downloads, and educational materials specific to Cluster Ripple Start, search the WebSphere Application Server support site.

Related information

Submitting information to IBM support
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server

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:

Read first and related MustGathers

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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;6.1;6.0","Edition":"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:
06 August 2020