Apache timeout error R12.2 exiting with status 150

[satish]

Dear Erman,

We tried bouncing the application services and we ended up with error in apache services on node1.
On node2,we are able to start opmn and apache. Uploaded the logs. Can you please advice

Node 1:
=======

[applprod@erpprodapp01 opmn]$ adopmnctl.sh start

You are running adopmnctl.sh version 120.0.12020000.2

Starting Oracle Process Manager (OPMN) ...

adopmnctl.sh: exiting with status 0

adopmnctl.sh: check the logfile /u02/PRODINST/fs1/inst/apps/PRODDB_erpprodapp01/logs/appl/admin/log/adopmnctl.txt for more information ...

[applprod@erpprodapp01 opmn]$



[applprod@erpprodapp01 opmn]$ adapcctl.sh start

You are running adapcctl.sh version 120.0.12020000.6

Starting OPMN managed Oracle HTTP Server (OHS) instance ...

adapcctl.sh: exiting with status 152

adapcctl.sh: check the logfile /u02/PRODINST/fs1/inst/apps/PRODDB_erpprodapp01/logs/appl/admin/log/adapcctl.txt for more information ...

[applprod@erpprodapp01 opmn]$


Log:
===
02/08/23-22:52:58 :: adapcctl.sh: starting OPMN managed OHS instance

opmnctl startproc: starting opmn managed processes...
================================================================================
opmn id=erpprodapp01.ttd.com:6207
Response: 0 of 1 processes started.

ias-instance id=EBS_web_OHS1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------------------------------------------
ias-component/process-type/process-set:
EBS_web/OHS/OHS/

Error
--> Process (index=1,uid=1365061158,pid=24326)
time out while waiting for a managed process to start
Log:
/u01/PRODAPPS/fs1/FMW_Home/webtier/instances/EBS_web_OHS1/diagnostics/logs/OHS/EBS_web/console~OHS~1.log

[satish]

Dear Erman,

Not sure what happended. Issue fixed when we use adstartall.sh script.
Not sure why apache is not getting started and giving timeout error with adapcctl.sh

Thanks,
Satish

[ErmanArslansOracleBlog]

Good.

According to the outputs that you provided, your return code is 152, not 150.
That 152 probably comes from the opmn..
We should see the console log, but it is probably due to a lock or cache file or an opmn related file preventing the apache to start.
adstrtall.sh (with or without an adstpall.sh run just before that) probably takes care about those files and let apache start successfully.. But this is just an idea. We need to see the logs.