IBM HTTP Server or Apache will not start after installing plug-in

Technote (FAQ)
Problem
This is a list of things to check when Web server fails to start after installing plug-in.
Solution
The IBM® HTTP Server, or Apache Web servers, are impacted by any WebSphere Application Server or OSE Remote plug-in problems.
  1. Verify that the path to the plug-in modules is correct in httpd.conf and the path to the bootstrap.properties files is correct.

    Insure that the settings for the administrative server in the bootstrap.properties file is correct.:
    ose.srvgrp.ibmappserve.type=FASTLINK
    ose.srvgrp.ibmappserve.clonescount=1
    ose.srvgrp.ibmappserve.clone1.port=8081
    ose.srvgrp.ibmappserve.clone1.type=local
    ose.srvgrp.ibmappserve.clone1.host=localhost

    In the above example the administrative server queue is local; when the administrative server is remote, ensure that the host and port are correct.
  2. Verify syntax of IBM HTTP Server configuration files: httpd -t or apache -t (depending on platform):
    • On Windows® NT, apache.exe is in home directory where IBM HTTP Server was installed (typically c:\Program Files\IBM HTTP Server, change to home directory and enter apache -t conf/httpd.conf
    • On AIX®, httpd is in the bin directory (typically /usr/HTTPServer/bin). If this directory is on the path, enter ./httpd -t httpd/httpd.conf
    • On Solaris™, httpd is in the bin directory (typically /opt/IBMHTTPD/bin). If this directory is on the path, enter ./httpd -t httpd/httpd.conf
    • On Linux®, httpd is in the bin directory (typically /opt/IBMHTTPServer/bin). If this directory is on the path, enter httpd -t httpd/httpd.conf
  3. Try starting IBM HTTP Server from a command line to see if error messages display.
    • On Windows NT, apache.exe is in home directory where IBM HTTP Server was installed (typically c:\Program Files\IBM HTTP Server, change to home directory and enter apache -f conf/httpd.conf
    • On AIX, httpd is in the bin directory (typically /usr/HTTPServer/bin). If this directory is on the path, enter ./httpd -f httpd/httpd.conf
    • On Solaris, httpd is in the bin directory (typically /opt/IBMHTTPD/bin). If this directory is on the path, enter ./httpd -f httpd/httpd.conf
    • On Linux, httpd is in the bin directory (typically /opt/IBMHTTPServer/bin). If this directory is on the path, enter httpd -f httpd/httpd.conf
  4. Comment out plug-in, then stop and restart Web server:
    • The line in the httpd.conf file will look something like this (Windows NT example):
      LoadModule ibm_app_server_module d:/WebSphere/AppServer/bin/mod_ibm_app_server.dll
      Alias /IBMWebAS/samples/ "D:/WebSphere/AppServer/samples/" Alias /IBMWebAS/ "D:/WebSphere/AppServer/web/" NcfAppServerConfig BootFile D:\WEBSPH~1\APPSER~1\properties\bootstrap.properties

      a. Save a copy of the httpd.conf before altering
      b. httpd.conf file is located in the conf subdirectory of the IBM HTTP Server installation
      c. Stop IBM HTTP Server using apachectl stop on AIX and Solaris (use services dialog in Windows NT)
      d. Start IBM HTTP Server using apachectl start on AIX and Solaris (use services dialog in Windows NT)
  5. If Web Server starts, the plug-in problem must be analyzed. Update the WebSphere Application Server properties/bootstrap.properties to trace plug-in:
    1. Add INFORM|TRACE values to the 2 lines below:
      ose.native.log.level=ERROR|WARNING|INFORM|TRACE ose.plugin.log.level=ERROR|WARNING|INFORM|TRACE
    2. Make sure that ose.logs.dir is set; for example (Windows NT example): ose.logs.dir=d:/WEBSPH~1/APPSER~1/logs
    3. Make sure the Web server process has authority to write to the logs directory (UNIX only):
      chmod ugo+w /usr/WebSphere/AppServer/logs
    4. If the administrative console starts, select OSE settings dialog and enable trace.











    Document Information

    Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Install
    Operating system(s): All Platforms
    Software version: 3.5
    Software edition: Advanced, Single Server
    Reference #: 1040938
    IBM Group: Software Group
    Modified date: 2004-12-16