IBM Support

MustGather: WebSphere Fails to Start on IBM i

Troubleshooting


Problem

Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data. MustGather information for WebSphere Application Server startup failures.

Symptom

The WebSphere Application Server instance/job will not stay started or is not functional when started.

Environment

IBM i
IBM WebSphere Application Server Traditional

Resolving The Problem

MustGather information for WebSphere startup failures.

WebSphere V7.0 Express (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V7/Express/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V7/Express/profiles/

WebSphere V7.0 Base (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V7/Base/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V7/Base/profiles/

WebSphere V7.0 Network Deployment (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V7/ND/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V7/ND/profiles/

WebSphere V8.0 Express (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V8/Express/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V8/Express/profiles/

WebSphere V8.0 Base (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V8/Base/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V8/Base/profiles/

WebSphere V8.0 Network Deployment (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V8/ND/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V8/ND/profiles/

WebSphere V8.5 Express (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V85/Express/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V85/Express/profiles/

WebSphere V 8.5 Base (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V85/Base/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V85/Base/profiles/

WebSphere V8.5 Network Deployment (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V85/ND/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V85/ND/profiles/

WebSphere V9.0 Base (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V9/Base/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V9/Base/profiles/

WebSphere V9.0 Network Deployment (Default Location)
<installRoot> - /QIBM/ProdData/WebSphere/AppServer/V9/ND/
<profileRoot> - /QIBM/UserData/WebSphere/Appserver/V9/ND/profiles/

For all WebSphere Application server installations not installed in the default location, you should run the following commands to locate the <installRoot> and <profileRoot>.

STRQSH
<installRoot>/bin/queryWASinstalls
OR (WAS v8.0 and earlier)
/QIBM/WAS/bin/queryWASinstalls

You should follow these steps to create and gather important diagnostic information.

1. Clear the <profileRoot>/<profileName>/logs/ directory.

2. Attempt to start your WebSphere Application Server using the startServer command and the -trace option.

STRQSH
<installRoot>/bin/startServer -profileName <profileName> -trace

3. Review the <profileRoot>/logs/<profileName>/ directory.  Do any SystemOut.log and SystemErr.log files get created?
SystemOut.log and SystemErr.log creation is an indication the JVM did start and ended.  If not, did any native_stdout.log and native_stderr.log files get created?

4. Run the WebSphere Application Server collector tool. Once complete, reference the collector script JAR file..

STRQSH
<profileRoot>/bin/collector -JarOutName /home/wasdata.jar
i.e.  
/QIBM/UserData/WebSphere/AppServer/<version>/<edition>/profiles/<profile>/bin/collector -JarOutName /home/wasdata.jar

5. Check for IBM i LIC Logs:

a. Issue the STRSST command.
b. Enter SST UserID/PWD.
c. Option 1. Start a service tool (press Enter).
d. Option 5. Licensed Internal Code log (press Enter).
e. Option 1. Select entries from the Licensed Internal Code (LIC) log (press Enter two times).
f. Specify a Enty type: Major code of 4700 and minor code of 0000. Then, press Enter.

6. Look at the date and time the entry was produced. If a log exists at the time of the issue, then enter a 1 next to it and press Enter to print the log.  This will print the LIC log to a QPCSMPRT spooled file.

7. Does the following IFS file exist?  If so, please provide IBM with a copy of this file's contents.

WKRLNK '/QIBM/UserData/Java400/SystemDefault.properties'

8. Gather authority on the IFS object /tmp. Ensure *PUBLIC user is not listed as *EXCLUDE.
  • WRKLNK '/tmp'
  • Option 9 on tmp
9. Gather the following for IBM Support Review.
  • JAR file created from collector script
  • Spooled output from LIC Logs
  • WebSphere Application Server Job Log
  • SystemDefault.properties, if it exists
  • Authority on IFS /tmp

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

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHUAA2","label":"WebSphere Application Server"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

521615602

Document Information

Modified date:
19 December 2023

UID

nas8N1013001

Page Feedback