IBM Support

MustGather: Collective and Controller in WebSphere Liberty Profile

Troubleshooting


Problem

Collecting Data (Must Gather) for Collective and Controller issues for Liberty. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving The Problem


If the problem involves a remote operation, for example start or stop on a remote collective member server, you need to verify the RXA configuration.

Please review and complete the steps from Setting up RXA for Liberty collective operations.

Note : If using ssh for RXA connections, Have you verified that ssh is working between the machines involved? ie.

From collective controller server host

# ssh [options] member_hostname

From collective member server host

# ssh [options] controller_hostname

If still have issues, please follow these steps to enable traces on the collective controller and the member server, reproduce the issue and collect diagnostics.

1. Trace String to enable on collective controller and member server :

com.ibm.ws.ui.*=all:com.ibm.ws.collective.*=all:com.ibm.ws.frappe.*=all:
SSLChannel=all:com.ibm.ws.ssl.*=all:com.ibm.websphere.ssl=all:com.ibm.wsspi.ssl.*=all

To enable Trace

Open the server.xml file and add the <logging> tag to the server.xml file with the following elements:

<logging traceSpecification="com.ibm.ws.ui.*=all:com.ibm.ws.collective.*=all:com.ibm.ws.frappe.*=all:
SSLChannel=all:com.ibm.ws.ssl.*=all:com.ibm.websphere.ssl=all:com.ibm.wsspi.ssl.*=all"
traceFileName="trace.log"
maxFileSize="100"
maxFiles="10"
traceFormat="BASIC" />

2. Enable RXA trace by adding the following line to both the collective controller and collective member server.xml configuration file.

<hostAccess enableRXATrace="true" />

3. Before recreating the issue(s), stop the servers and clear the logs and trace. Then restart the servers with the trace enabled and recreate the issue.

4. Collect diagnostics information

4.1. Run server dump for both collective controller and collective member to collect configuration and diagnostics.

<LIBERTY_HOME>/bin/server dump <controller-name>
<LIBERTY_HOME>/bin/server dump <member-name>

4.2. Output of the following commands from controller and member. ie.

<LIBERTY_HOME>/bin/productInfo version
<LIBERTY_HOME>/bin/productInfo featureInfo

4.3. Describe issue seen and with screenshots capturing the issue and error message

4.4 Send us

a. Zip files created by server dump command from both controller and member from 4.1
b. Output of commands in 4.2
c. Any screen shots and any additional details on setup.

Follow instructions to send diagnostic information to IBM support.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Liberty","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":"Liberty;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg22008266