IBM Support

MustGather: Web server administration problems for IBM HTTP Server

Question & Answer


Question

Unable to start or stop your IBM® HTTP Server using the IBM WebSphere® Application Server Administrative Console? Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Answer

The following instructions demonstrate how to collect the files and information that is needed for debugging IBM HTTP Server administration issues through the administrative console:
Before gathering the MustGather data for the failed Start, use the following steps to verify that the status is being handled correctly.

First, verify that the STATUS is working

Start IHS from a Unix Machine using Apachectl -start from the command line or with Windows Services on Windows, then open the WebSphere Administration console and verify that the Status is properly reflected as Green.

Stop IHS from a Unix Machine using Apachectl -stop from the command line or with Windows Services on Windows, then open the WebSphere Administration console and verify that the Status is properly reflected as RED.

Status is accomplished by a Java socket connect from the Deployment Manager (DMGR) machine to the target web server machine. The DMGR will attempt to connect using the hostname and port as defined in the Web Server definition in the WebSphere Administration Console. If you are not getting the correct Status, this is an indication that something is preventing the DMGR from connecting to the web server machine. It could be configuration or a firewall issue.

Review the following troubleshooting technotes for further suggestions:
http://www-01.ibm.com/support/docview.wss?uid=swg21431586
http://www-01.ibm.com/support/docview.wss?uid=swg21261119

Proceed to gathering the MustGather data below if the above troubleshooting suggestions do not help in resolving the problem.

Trace instructions for Unmanaged (remote) web server definition:

  1. Stop the IBM HTTP Server (IHS) and IHS administration server
  2. Edit IHS_install_root/conf/admin.conf and change the directive LogLevel warn to LogLevel debug
  3. Edit IHS_install_root/conf/httpd.conf and change the directive LogLevel warn to LogLevel debug
  4. Backup and then delete the files under IHS_install_root/logs
  5. Restart IHS administration server
  6. Backup and then delete the files and folders in the following directories:
    1. WebSphere_install_root/profiles/Dmgr01/logs
    2. install_root/logs/profiles/AppSrv01/nodeagent/logs
7. Enable logging for the Deployment Manager (DMGR) process using the following trace string: 8. Save the changes to the master configuration and reproduce the problem
9. Collect the following data:
    1. Run the Collector tool on the Network Deployment (for federated environment only) or base Application Server profiles. This should include the trace.log file from the Node Agent and the trace.log file from the DMGR and all of the configuration files. Provide the collector output file.
    2. IBM Http Server: httpd.conf, error.log, and access.log
    3. IBM Administration Server: admin.conf, admin_error.log, and admin_access.log
    4. For Unix on the web server machine, issue this command to obtain the IHS Administration user ID and provide the output file:
    ps -ef | grep admin > admin.proc
    e. While the web server is started, issue the commands on the web server and send the output:
    netstat -an > netstat.out
    Unix:
    ifconfig -a > ifconfig.out
    Windows
    ipconfig /all > ipconfig.out
    f. Send output of IBM Http Server version:
      Windows: IHS_install_root/bin/ Apache.exe -V
      Unix: IHS_install_root/bin/ Apachectl.sh -V
    g. If using Windows, export the Windows event log from the Web Server experiencing the problem.

10. Follow instructions to send diagnostic information to IBM support


Trace instructions for Managed (local) web server definition:
  1. Stop the IBM HTTP Server (IHS)
  2. Backup and delete the files under IHS_install_root/logs
  3. Edit IHS_install_root/conf/httpd.conf and change the directive LogLevel warn to LogLevel debug
  4. Backup and then delete the files and folders in the following directories:
    1. WebSphere_install_root/profiles/Dmgr01/logs
    2. WebSphere_install_root/logs/profiles/AppSrv01/nodeagent/logs
  5. Enable logging for the Deployment Manager (Dmgr) and the node agent processes using the following trace string:

      6. DMGR
      *=info:
      com.ibm.ws.console.*=all:com.ibm.ws.management.webserver.*=all:com.ibm.ws.process.*=all
      NODEAGENT
      *=info:
      com.ibm.ws.management.nodeagent.NodeAgent=all=enabled:
      com.ibm.ws.management.metadata.NodeAgentCollector=all=enabled:
      com.ibm.ws.management.tools.GenericServerProcHelper=all=enabled:
      com.ibm.ws.console.core.*=all=enabled:
      com.ibm.ws.process.*=all=enabled:

    Click on this url for instructions on enabling a Diagnostic Trace in the WebSphere Administration console
    http://www-01.ibm.com/support/docview.wss?uid=swg21254706
6. Save the changes to the master configuration and reproduce the problem

7. Collect the following data:
    1. Run the collector tool on the Network Deployment (for federated environment only) or base Application Server profiles. This should include the trace.log file from the Node Agent and the trace.log file from the DMGR and all of the configuration files. Provide the collector output file.
    2. IBM Http Server: httpd.conf, error.log, and access.log
    3. For Unix: Issue the following command on the Node agent machine:
      ps -ef | grep java > was.proc
      Send the was.proc file
    d. Send output of IBM Http Server version:
      Windows: IHS_install_root/bin/ Apache.exe -V
      Unix: IHS_install_root/bin/ apachectl.sh -V 
    e. If using Windows, export the Windows event log from the Web Server experiencing the problem.

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

[{"Product":{"code":"SSEQTJ","label":"IBM HTTP Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Admin GUI","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;8.5;8.0;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
07 September 2022

UID

swg21285057

Page Feedback