IBM Support

MustGather: Start or Stop failures from WebSphere Administration Console for IBM HTTP Server

Troubleshooting


Problem

Collecting data for connection problems with the IBM HTTP Server Administration Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Diagnosing The Problem

1. Please verify that the STATUS is correct in the WebSphere Administration Console:


    Start IHS from Linux Machine CommandLine or Windows Services or Windows commandline. Is the Status properly reflected Green in the WebSphere Administration Console?

    Stop IHS from Linux Machine CommandLine or Windows Services or Windows commandline. Is the Status properly reflected RED in the WebSphere Administration Console?

    Status is accomplished by Java socket connect from DMGR to the Target Web Server. So DMGR is attempting to connect using Hostname and port as defined in Web Server definition. Please Confirm that Status is working correctly.

    If status is not being reflected correctly, then gather this Doc:

    • Issue nslookup of Web Server hostname from the DMGR machine

        • nslookup <Web hostname > nslookup
    • Issue the following after Start of the Web Server on Web Server machine from CommandLine:

        • netstat -an > netstat.out

        Linux: ifconfig -a > ifconfig.out Windows: ipconfig /all > ipconfig.out

2. Determine if the Web server is defined to a Managed node or an Unmanaged node.

    a.) For WebSphere ND with Deployment Manager the Node is Unmanaged if you see "Not applicable" in the "Version" for the Web server in the Web server collection Panel (Servers -> Web servers)

    If you do not see "Not Applicable" , but the actual "version" (i.e. 8.5.5.5) Info then the Node is Managed.

    b.) For WebSphere is Base Application Server then Node is Unmanaged .


3. Set Logging and traces:

    a.) For a Web server defined on an Unmanaged node we need to gather the following traces:
      • Set the Loglevel debug in the admin.conf
      • Stop and Start the IBM Administration Sever (./adminctl or Apache service)
      • Issue Command on Web Server machine: For UNIX: ps -ef | grep admin > admin.proc For Windows: tasklist | findstr "http" > admin.proc
    b.) For a Web server defined on a Managed node we need to gather the following traces:

      Set the NodeAgent traces:

      System Administration -> NodeAgents -> Click <nodeagent name>

      click "Change log detail levels"

      Node agent

      *=info:

      com.ibm.ws.management.nodeagent.NodeAgent=all:

      com.ibm.ws.management.metadata.NodeAgentCollector=all:

      com.ibm.ws.management.tools.GenericServerProcHelper=all:

      com.ibm.ws.console.core.*=all:

      com.ibm.ws.process.*=all:

      com.ibm.ws.management.launcher.*=all:

      com.ibm.websphere.plugincfg.*=all:

      com.ibm.ws.management.filetransfer.*=all:

      com.ibm.ws.management.fileservice.*=all:

      com.ibm.ws.management.webserver.*=all

      Issue Command on Node agent machine:

      ps -ef | grep java > was.proc


    c.) Please set the DMGR trace for Web server on Managed or Unmanaged node:

      *=info:

      com.ibm.ws.console.web.webserver.*=all:

      com.ibm.ws.console.web.util.impl.ServerUtilImpl=all:

      com.ibm.ws.console.web.webserver.ServerController=all:

      com.ibm.ws.management.webserver.RemoteIhsWebServerControl=all:

      com.ibm.ws.management.webserver.ManagedWebServerControl=all:

      com.ibm.ws.management.webserver.WebServer=all:

      com.ibm.ws.process.*=all:

      com.ibm.websphere.plugincfg.*=all:

      com.ibm.websphere.management.filetransfer.*=all:

      com.ws.management.filetransfer.*=all:

      com.ibm.ws.management.fileservice.*=all


    d.) Please update the LogLevel debug in the httpd.conf

4. Recreate the Failed Start and capture Screenshot

5. Please ZIP Contents of the DMGR repository or the Base WebSphere repository


    If Base Application Server:

      cd BaseApplication Server Profile/config/cells

    If DMGR

      cd DMGRProfile/config/cells

    ZIP all files and sub directories

6 Please send in the following information and traces:

    Unmanaged Node:

      admin.conf, admin_error.log, admin_access.log, admin.proc

    Managed Node:

      Nodeagent: trace.log, SystemOut.log, SystemErr.log all FFDC files

      Node Agent: was.proc


    Both:

    httpd.conf, error.log

    DMGR: trace.log, System Out.log, SystemErr.log all FFDC files

    DMGR Repository ZIP

    Screenshot of the failure

[{"Product":{"code":"SSEQTJ","label":"IBM HTTP Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Base Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IBM HTTP Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.1;6.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
07 September 2022

UID

swg21202150

Page Feedback