APPLIES TO:
Oracle E-Business Suite Technology Stack - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

SYMPTOMS:
E-Business Suite 12.1.3, IAS for Applications Technology
After instance maintenance or patching the HTTP Server status is reported as down after starting all services.
Further investigation showsthe below errors in HTTP server log file:

ERROR:
-----------------------
adapcctl.txt :
opmnctl: starting opmn managed processes...
================================================================================
opmn id=ebsapp101.doyensys.com:6220
0 of 1 processes started.

ias-instance id=UAT_ebsapp101.ebsapp101.doyensys.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------------------------------------------
ias-component/process-type/process-set:
HTTP_Server/HTTP_Server/HTTP_Server/

Error
--> Process (index=1,uid=2050903338,pid=20024)
failed to start a managed process after the maximum retry limit
Log:
/u01/app/oracle/inst/apps/UAT_ebsapp101/logs/ora/10.1.3/opmn/HTTP_Server~1.log

11/03/20-13:21:27 :: adapcctl.sh: exiting with status 0

HTTP_Server~1.log:
------------------
11/03/20-13:21:27 Start process
--------
apachectl is not owned by this user

STEPS:
-----------------------
The issue can be reproduced at will with the following steps:
1. Run $ADMIN_SCRIPTS_HOME/adappclt.sh start
2. Check the HTTP_server status via the log file

CAUSE:
$INST_TOP/ora/10.1.3/Apache/bin/apachectl was owned by a user other than the application owner.
Ownership of $INST_TOP/ora/10.1.3/Apache/Apache/bin/apachectl shows it is own by a user other than the unix applications user account.

SOLUTION:
To implement the solution, test the following steps in a development instance and then migrate the changes accordingly:

1. Check permissions of $INST_TOP/ora/10.1.3/Apache/Apache/bin/apachectl / $INST_TOP/ora/10.1.3/Apache/Apache/bin/.apachectl and confirm they reflect the following:

-rwx------ 1 applmgr apps 1 apachectl

2. Retest the services after any changes (eg. apachectl.sh start) and confirm the services start successfully.
Recent Posts

Start typing and press Enter to search