Skip to content

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

Collecting data manually,

If an Application Server, dmgr or nodeagent 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="10"
  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 filename 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 on Logs and Trace.

  3. Click on the link for your server.
  4. Click on 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 10.
  7. Click on Apply and save and synchronize your configuration.
  8. Stop and restart the Application Server, dmgr, or nodeagent.
  9. Run the collector tool on both Network Deployment (for federated environment only) and Base Application Server profiles.
  10. Follow directions in MustGather: Readme First to open a PMR and send data to IBM Support.
  11. Follow instructions to send diagnostic information to IBM support.