MustGather: Crash on Linux
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for problems with a IBM® WebSphere® Application Server (WSAS) crash on the Linux® platform. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
 
Resolving the problem

Do you want to automate the collection of MustGather data?
Collecting the following MustGather information has now been automated in the IBM Support Assistant. For more information about automating data collection, see Using IBM Support Assistant to collect MustGather data.

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

Crash on Linux specific MustGather information
  1. Make a backup copy of the core file.

  2. At the command line, run the following:

    gdb -x gdb_commands.txt [JAVA_PATH] [CORE_PATH] > gdbtrace_out.txt

    Where:
    [JAVA_PATH] is <install_root>/java/jre/bin/java
    [CORE_PATH] is the path/filename for the core file
    gdb_commands.txt is attached to this document

  3. Execute the following command from the install_root/java/jre/bin directory:

    For WSAS 5.x and WSAS 6.0:
    jextract -o core.sdff [CORE_PATH]

    For WSAS 6.1
    jextract [CORE_PATH]

    Where:
    core.sdff is the output file
    [CORE_PATH] is the path/filename for the core file

  4. At the command line, run the following:

./libsgrabber.sh [JAVA_PATH] [CORE_PATH]

Where:
[JAVA_PATH] is install_root/java/jre/bin
[CORE_PATH] is the path/filename for the core file

5. Collect the following files:
  1. For all releases:
    • Any javacore*.txt files produced
    • gdbtrace_out.txt
    • core.sdff
    • /var/log/messages

  2. For all releases of V6.0 and V6.1
    • All files in the following directory:

      install_root/profiles/profile_name/logs/server_name

      Note: If you have configured the application server to write the logs into a different location, send them accordingly.

    • The server.xml file located in the following directory:

      install_root/profiles/profile_name/config/cells/
      cell_name
      /nodes/node_name/servers/server_name

  3. For all releases of V5.0 and V5.1:
    • Include all of the files from the following directory:

      install_root/logs/server_name

      Note: Include the Application Server stderr and stdout files, if they are located in a different directory.

    • The server.xml file located in the following directory:

      install_root/config/cell/cell_name/nodes/
      node_name/servers/server_name

6. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Crash component, search the WebSphere Application Server support site.
 
Related information
Steps to Getting Support
Crash on Linux produces no core or truncated core
Node agent crash on zSeries®
Submitting Diagnostic Information To IBM Support
MustGather: Readme first
Troubleshooting guide
 
gdb_commands.txt libsgrabber.sh
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express Hangs/performance degradation Linux 6.0, 5.1, 5.0
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Crash
Operating system(s): Linux
Software version: 6.1
Software edition:
Reference #: 1104706
IBM Group: Software Group
Modified date: Nov 10, 2008