Listener Down unexpectedly
- From: <Ravi_Kulkarni@xxxxxxxx>
- To: <racdba@xxxxxxxxxxxxx>
- Date: Mon, 29 Aug 2005 08:45:42 -0500
Has any of you seen this before ?
Listener on Node 3 died unexpectedly. CRS tried to restart but could
not. (RHEL 3-Hugemem/Oracle 10.1.0.4/6-Node RAC). Point of concern is
none of the users were able to connect till we kill the queued up tns
processes and use srvctl start nodeapps to start the listener.
from $OH/racg/dump, we have info that CRS tried to query the status of
listener but timed out waiting for the response. "ps" output at the time
had these tns processes.
15:42 :
0 S oracle 11270 1 0 77 0 - 9459 wait4 Aug20 ?
00:02:55 /db/db01/home/oracle/product/10.1.0/bin/tnslsnr
LISTENER_AUSM2GDAODB03 -inherit ===> shows a "wait4" state for the
original listener from "scheduled" state a minute before (is this a
hung process?)
1 S oracle 29918 11270 0 77 0 - 9459 schedu 15:41 ?
00:00:00 /db/db01/home/oracle/product/10.1.0/bin/tnslsnr
LISTENER_AUSM2GDAODB03 -inherit ===> at the same time, we see another
listener process cropping up from nowhere which started at 15:41.
15:44:
0 S oracle 11270 1 0 77 0 - 9459 wait4 Aug20 ?
00:02:55 /db/db01/home/oracle/product/10.1.0/bin/tnslsnr
LISTENER_AUSM2GDAODB03 -inherit
1 S oracle 29918 11270 0 77 0 - 9459 schedu 15:41 ?
00:00:00 /db/db01/home/oracle/product/10.1.0/bin/tnslsnr
LISTENER_AUSM2GDAODB03 -inherit
0 S oracle 30394 30391 0 85 0 - 4049 schedu 15:44 ?
00:00:00 /db/db01/home/oracle/product/10.1.0/bin/lsnrctl status
LISTENER_AUSM2GDAODB03
==> This status check is the one we are seeing in CRS logs which failed.
Thanks,
Ravi.
Other related posts:
- » Listener Down unexpectedly
