time out while waiting for a managed process to stop HTTP_Server
This is a generic error that everybody will come across, but it may be for different process like HTTP_Server, OC4J_SECURITY etc.,
In my case, I got it while restarting/stopping the HTTP_Server as shown below.
[oracle@mahendra.domain.com bin]$ ./opmnctl stopallopmnctl: stopping opmn and all managed processes…
=======================
opmn id=mahendra.domain.com:7017
2 of 3 processes stopped.
ias-instance id=oasinfra.mahendra.domain.com
++++++++++++++++++++++++++++
—————————————-
ias-component/process-type/process-set:
HTTP_Server/HTTP_Server/HTTP_Server
Error
–> Process (pid=6047)
time out while waiting for a managed process to stop
Log:
/u01/osinfra/opmn/logs/HTTP_Server~1
opmnctl: graceful stop of processes failed, trying forceful shutdown…
Even the shutdown was not successful as shown below.
[oracle@mahendra.domain.com bin]$ ./opmnctl shutdownopmnctl: shutting down opmn and all managed processes…
Unacceptable request: OPMN is terminating
<?xml version=’1.0′ encoding=’ISO-8859-1′?>
<response>
<opmn id=”mahendra.domain.com:7017″ http-status=”406″ http-response=”OPMN is terminating”>
</opmn>
</response>
Then I checked the status of opmnctl processes as shown below.
[oracle@mahendra.domain.com bin]$ ./opmnctl statusProcesses in Instance: oasinfra.mahendra.domain.com
——————-+——————–+———+———
ias-component | process-type | pid | status
——————-+——————–+———+———
DSA | DSA | N/A | Down
LogLoader | logloaderd | N/A | Down
dcm-daemon | dcm-daemon | N/A | Down
OC4J | OC4J_SECURITY | N/A | Down
HTTP_Server | HTTP_Server | 6047 | Stop
OID | OID | N/A | Down
All the processes except HTTP_Server were down and even several attempts to stop HTTP Server alone could not succeed.
So, I have checked the process id that the HTTP_Server is being assigned to as shown below.
[oracle@mahendra.domain.com bin]$ ./opmnctl status -lProcesses in Instance: oasinfra.mahendra.domain.com
——————-+——————–+———+—–
ias-component | process-type | pid | status | uid | memused | uptime | ports
——————-+——————–+———+—–
DSA | DSA | N/A | Down | N/A | N/A | N/A | N/A
LogLoader | logloaderd | N/A | Down | N/A | N/A | N/A | N/A
dcm-daemon | dcm-daemon | N/A | Down | N/A | N/A | N/A | N/A
OC4J | OC4J_SECURITY | N/A | Down | N/A | N/A | N/A | N/A
HTTP_Server | HTTP_Server | 6047 | Stop | 1912078433 | 12328 | 00:23:20 | N/A
OID | OID | N/A | Down | N/A | N/A | N/A | N/A
So, I have searched for the process identifier as shown below and it is to be killed.
[oracle@mahendra.domain.com bin]$ ps -ef | grep 1912078433oracle 6047 1 0 12:08 ? 00:00:00 /u01/osinfra/Apache/Apache/bin/httpd -d /u01/osinfra/Apache/Apache -U 1912078433
oracle 10820 27210 0 12:31 pts/4 00:00:00 grep 1912078433
Killing the process as shown below.
[oracle@mahendra.domain.com bin]$ kill -9 6047Few seconds later, the opmnctl processes showed not connected as shown below.
[oracle@mahendra.domain.com bin]$ ./opmnctl statusUnable to connect to opmn.
Opmn may not be up.
Other way is to search for opmn process as ps -ef | grep opmn and killing the associated process of http server.
Now, I have started the opmnctl processes and this time I am through.
About the Author Mahendra
I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com