MustGather: Crash on Solaris
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for problems with a WebSphere® Application Server crash on a Solaris system. 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 have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.

Crash on Solaris specific MustGather information
  1. Important: Before issuing any of the following instructions, make a backup copy of the core file. Perform the following for each core file (the core file will be in the working directory, which is /opt/WebSphere/AppServer/bin by default).

  2. If you are running Solaris 8, or later, enter the following from a command-line:

    /usr/proc/bin/pstack [core] >pstack.out
    /usr/proc/bin/pmap [core] >pmap.out
    /usr/proc/bin/pldd [core] >pldd.out

    Where,
    [core] is the name of the core file
    pstack.out is changed for each core file
    pmap.out is changed for each core file
    pldd.out is changed for each core file

  3. In addition to the preceding information, capture the following:
    • For all releases:
      • env > env.out
      • ulimit -a > ulimit.out
      • uname -a > uname.out
      • showrev -p > showrev.out
      • pkginfo -l > pkginfo.out
      • /var/adm/messages
      • All hs_err_pid*.log files
    • For V6.0 releases:
      • Include all of the files from the following directory:

        install_root/profiles/profile_name/logs/server_name

      • A copy of the server.xml file located in the following directory:

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

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

        install_root/logs/server_name

      • A copy of the server.xml file located in the following directory:

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

    Note: For all versions, if you have configured the Application Server to write logs into a different location, send them accordingly.

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

For a listing of all technotes, downloads, and educational materials specific to Crash, search the WebSphere Application Server support site.
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
MustGather: Crash on Solaris produces no core or trunca
IBM Support Assistant
Using IBM Support Assistant to collect MustGather data
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express Hangs/performance degradation Solaris 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): Solaris
Software version: 6.1
Software edition:
Reference #: 1049530
IBM Group: Software Group
Modified date: Nov 10, 2008