IBM HTTP Server on a managed node

When the IBM HTTP Server on a managed node is started using WebSphere administration tools. The node agent issues the same command that you would use from a command line, that is: <Web_server_home>/bin/apachectl

Check to make sure the Web server can be started via other means, such as through the Windows control panel or from the command line. If it cannot be started, return to Approach to Problem Determination in WebSphere Application Server V6 to see how to proceed with Web server problems. You can find this paper at:

http://www.redbooks.ibm.com/redpapers/pdfs/redp4073.pdf

The deployment manager does not log any messages when you try to start a Web server. The node agent logs a simple message to tell you that it is trying to start the Web server as shown in Example 4-16. If the Web server fails to start, then you get a failure message in the administrative console and a message in the node agent log, as shown in Example 4-16.

———————————————————————————

Example 4-16 Node agent messages starting a Web server
[7/12/05 14:56:15:658 EDT] 000000a6 AdminHelper A ADMN1001I: An attempt is made to launch webserver1 on node m23vnx60Node01.
[7/12/05 14:56:15:661 EDT] 000000a6 NodeAgent W ADML0065W: A sync operation prior to starting an application server failed.

[7/12/05 14:56:22:843 EDT] 000000a6 NodeAgent W ADML0040E: The process timed out waiting for server “webserver1″ initialization: 1200 seconds

————————————————————

You need to review the Web server logs to determine what went wrong. Also, you can trace both the deployment manager and node agent process, as described in “Collecting data” on page 122, to gather further information about the source of a failure.