Starting HTTP Server fails with "Time Out While Waiting For a Managed Process to Start" with WebGate is Configured (Doc ID 1916960.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle HTTP Server - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.0 version,

The Oracle HTTP Server will not start using "opmnctl startproc process-type=OHS" and it returns the following errors:

-->  Process (index=1,uid=##,pid=##)
  time out while waiting for a managed process to start
  Log:
  <instance_home>/diagnostics/logs/OHS/ohs1/console~OHS~1.log

The <instance_home>/diagnostics/logs/OHS/ohs1/console~OHS~1.log shows the following message:

<webTier>/ohs/bin/apachectl hardstop:  httpd stopped

 

Changes

The following steps were taken to determine what was preventing OHS from starting.

1.  The processes for httpd were grepped using "ps -ef | grep httpd" and then "kill -9 <pid>"; remove the opmn/states directory and use "opmnctl startproc process-type=HTTP_Server".  OHS still fails to start.

2.  The <start timeout="300" /> was added to opmn.xml file as described within < Note: 821419.1> (OPMN Fails to Start HTTP Server - "Time Out While Waiting For a Managed Process to Start"), but the OHS still failed to start.

3.  The "apachectl start -f $httpd_conf" allows OHS to start. 

a.  Create a script, call it startup.sh, and put in these commands:

5. Now uncomment each include line in the httpd.conf file one by one.   When the webgate.conf file is uncommented out, then OHS does not start.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms