OPMN Fails to Start Oracle HTTP Server 10g After Changing 'apachectl' to Root Ownership and 6750 Permissions
(Doc ID 735023.1)
Last updated on AUGUST 10, 2020
Applies to:Oracle Fusion Middleware - Version 220.127.116.11.0 to 10.1.4.3.0 [Release AS10g to AS10gR3]
Oracle HTTP Server - Version 18.104.22.168.1 to 10.1.3.5.0 [Release AS10g to AS10gR3]
Information in this document applies to any platform.
Except the MS Windows platform.
Checked for relevance on 24-Jul-2013
Oracle HTTP Server, residing on a Unix platform, fails to start using OPMN. For example, OPMN reports the generic error
opmnctl: starting opmn and all managed processes...
0 of 1 processes started.
--> Process (pid=<pid>)
Failed to start a managed process after the maximum retry limit Log::
The HTTP_Server~1 OPMN log file just reports that the HTTP Server has been started, but there are actually no httpd processes present on the system.
There is also nothing written to the $ORACLE_HOME/apache/apache/logs directory even when HTTP Server logLevel is set to debug.
Furthermore there are no core / segmentation fault files created.
In order for the HTTP Server to listen on ports < 1024 e.g 80 and 443 the ownership and permissions of the Oracle HTTP Server binary - '.apachectl' - have been changed as follows:
chmod 6750 .apachectl
If the ownership and permissions of this binary are reverted back to the default settings HTTP Server starts up fine using OPMN.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document