IBM Support

MustGather: Application Server, dmgr, and nodeagent start and stop problems

Troubleshooting


Problem

Collecting data for problems with the start and stop of IBM WebSphere Application Server, dmgr, and node agent. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving The Problem


  • Read first and related MustGathers

    MustGather: Read first for WebSphere Application Server and Liberty

    Administrative console problem Cluster ripple start problem Deployment problem Discovery problem on Deployment Manager Discovery problem on Node Agent JMX problem Profile wizard problem System administration problem WASService problem (Windows only) WSAdmin problem

  • Collecting data manually

    If an Application Server, dmgr or node agent is not able to start when issuing the command startServer servername, startManager, or startNode at the command line, or if an Application Server is unable to start or stop using the Network Deployment administrative console, collect the following documents using one of the tracing methods below.

    Tracing from the WAS_PROFILE/bin command line:

    1. Backup and purge the logs in the following directories:
      WAS_PROFILE/logs/server_name
      WAS_PROFILE/logs/FFDC
       
    2. Open the following file:
      WAS_PROFILE/config/cells/cell_name/nodes/node_name/servers/server_name/server.xml
       
    3. Change the following string:
      • From:

        startupTraceSpecification="*=info"
         
      • To:

        startupTraceSpecification="*=info:com.ibm.ws.*=all"
         
    4. Change the following string:
      • From:

        maxNumberOfBackupFiles="1"
         
      • To:

        maxNumberOfBackupFiles="20"
         
    5. Save the changes.
    6. Run the following command:
      startServer servername -trace
      This will log the trace to the startserver.log file located in the following directory:
      WAS_PROFILE/logs/server_name
      If you want the trace to be written to a unique file, run the following command:
      startServer server_name -trace -logfile path_to/servertrace.out
      Note: If you specify the -logfile option with only a file name and you do not specify a directory path for the log file, the file will be created in the WAS_PROFILE/bin directory.
       
    7. Similarly, if the Application Server does not stop when issuing the command: stopServer server_name, stopManager, or stopNode. Follow the same procedure documented above for collecting trace documents, running the command stopServer. stopManager, or stopNode in place of startServer.
       
    8. Run the collector tool on both Network Deployment (for federated environment only) and Base Application Server profiles.
       
    9. Follow instructions to send diagnostic information to IBM support.

    Tracing in the administrative console:

    1. Backup and purge the logs in the following directories:
      WAS_PROFILE/logs/server_name
      WAS_PROFILE      /logs/FFDC
       
    2. In the administrative console, expand the Troubleshooting section and click Logs and Trace.
       
    3. Click the link for your server.
       
    4. Click Change Log Detail Levels.
       
    5. Change the following string:
      • From:

        *=info
         
      • To:

        *=info:com.ibm.ws.*=all
         
    6. Increase the Maximum Number of Historical Files from 1 to 20.
       
    7. Click Apply and save and synchronize your configuration.
       
    8. Stop and restart the application server, deployment manager, or node agent.
       
    9. Run the collector tool on both Network Deployment (for federated environment only) and Base Application Server profiles.
       
    10. Follow directions on the WebSphere Application Server support portal to open a case and send data to IBM Support.
       
    11. Follow instructions to send diagnostic information to IBM support.
     
    For a listing of all technotes, downloads, and educational materials specific to the System Management Repository component, search the WebSphere Application Server support portal.


  • 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:

    • Service Request (SR)
    • Email
    • FTP to the Enhanced Customer Data Repository (ECuRep)

    Instructions for exchanging information with IBM Support

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"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","Edition":"Base;Express;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"}},{"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":null,"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;6.1;6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 July 2022

UID

swg21201014

Page Feedback