Home » RDBMS Server » Enterprise Manager » EM is not running? try to start but failed (oracle 11.2.0.1 RAC of two nodes,solaris10)
EM is not running? try to start but failed [message #545678] Thu, 01 March 2012 11:42 Go to next message
janakors
Messages: 177
Registered: September 2009
Senior Member
hi,
we have RAC of two nodes and EM is not running on one instance and running on another instance. when i issue emctl start dbconsole
command it trying to start for 50 minutes but at the end, it fails
i have checked the log (emagent.log) which is as follows

2012-02-29 14:18:48,971 Thread-1 Starting Agent 10.2.0.4.2 from /u01/app/oracle/product/11.2.0/dbhome (00701)
2012-02-29 14:18:48,973 Thread-1 <Agent Startup> : Startup of HTTP LISTENER failure (00716)
2012-03-01 10:25:43,414 Thread-1 Starting Agent 10.2.0.4.2 from /u01/app/oracle/product/11.2.0/dbhome (00701)
2012-03-01 10:25:43,525 Thread-1 <Agent Startup> : Startup of HTTP LISTENER failure (00716)
2012-03-01 11:15:57,307 Thread-1 Starting Agent 10.2.0.4.2 from /u01/app/oracle/product/11.2.0/dbhome (00701)
2012-03-01 11:15:57,355 Thread-1 <Agent Startup> : Startup of HTTP LISTENER failure (00716)
2012-03-01 11:38:41,818 Thread-1 Starting Agent 10.2.0.4.2 from /u01/app/oracle/product/11.2.0/dbhome (00701)
2012-03-01 11:38:41,837 Thread-1 <Agent Startup> : Startup of HTTP LISTENER failure (00716)
2012-03-01 13:08:06,112 Thread-1 Starting Agent 10.2.0.4.2 from /u01/app/oracle/product/11.2.0/dbhome (00701)
2012-03-01 13:08:06,114 Thread-1 <Agent Startup> : Startup of HTTP LISTENER failure (00716)


and output of tail -100 emagent.trc is

2012-02-29 09:24:39,821 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-02-29 09:24:39,821 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-02-29 09:43:29,057 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-02-29 09:43:29,057 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-02-29 09:43:29,057 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-02-29 12:07:07,743 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-02-29 12:07:07,743 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-02-29 12:07:07,743 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-02-29 13:00:41,872 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-02-29 13:00:41,880 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-02-29 13:00:41,880 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-02-29 14:18:48,972 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-02-29 14:18:48,973 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-02-29 14:18:48,973 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-03-01 10:25:43,493 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-03-01 10:25:43,525 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-03-01 10:25:43,525 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-03-01 11:15:57,339 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-03-01 11:15:57,339 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-03-01 11:15:57,355 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-03-01 11:38:41,837 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-03-01 11:38:41,837 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-03-01 11:38:41,837 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-03-01 13:08:06,114 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-03-01 13:08:06,114 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-03-01 13:08:06,114 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.
2012-03-01 13:42:54,766 Thread-1 ERROR http: snmehl_allocateListenerPort: failed to listen on all sockets for hostname  and port 2928
2012-03-01 13:42:54,766 Thread-1 ERROR http: nmehl_startHttpListener: failed to listen to HTTP(s) port for https://db1:2928/emd/main
2012-03-01 13:42:54,766 Thread-1 ERROR main: nmehl_startHttpListener failed starting http listener.



kindly guide

regards
Re: EM is not running? try to start but failed [message #545681 is a reply to message #545678] Thu, 01 March 2012 11:54 Go to previous messageGo to next message
BlackSwan
Messages: 22837
Registered: January 2009
Senior Member
https://www.google.com/search?sourceid=chrome&ie=UTF-8&q=Startup+of+HTTP+LISTENER+failure+(00716)
Re: EM is not running? try to start but failed [message #545689 is a reply to message #545678] Thu, 01 March 2012 12:45 Go to previous messageGo to next message
John Watson
Messages: 4610
Registered: January 2010
Location: Global Village
Senior Member
You can't start the console on two nodes. On the second node, you start only the agent.
Re: EM is not running? try to start but failed [message #545731 is a reply to message #545689] Fri, 02 March 2012 00:14 Go to previous messageGo to next message
janakors
Messages: 177
Registered: September 2009
Senior Member
hi,
yes infact the agent is not running on this node when i checked the status of emctl status agent it throws fol errors
Quote:
Error connecting to HTTPS://Hostname:3938/emd/main


kindly guide
Re: EM is not running? try to start but failed [message #545740 is a reply to message #545731] Fri, 02 March 2012 01:52 Go to previous messageGo to next message
John Watson
Messages: 4610
Registered: January 2010
Location: Global Village
Senior Member
Do you actually have a problem? Can you connect to the dbconsole or not?
Re: EM is not running? try to start but failed [message #547362 is a reply to message #545740] Tue, 13 March 2012 23:45 Go to previous messageGo to next message
janakors
Messages: 177
Registered: September 2009
Senior Member
we have two instances ,INST1 AND INST2
i run emctl start dbconsole and it was successfully done on INST2
i run emctl status dbconsole on INST1 and found agent is not running

so EM is not running and i searched internet but was unable to solve the issue.

kindly advice

Regards
Janakors
Re: EM is not running? try to start but failed [message #547389 is a reply to message #547362] Wed, 14 March 2012 02:17 Go to previous messageGo to next message
John Watson
Messages: 4610
Registered: January 2010
Location: Global Village
Senior Member
Quote:
Do you actually have a problem? Can you connect to the dbconsole or not?
Re: EM is not running? try to start but failed [message #547510 is a reply to message #547389] Wed, 14 March 2012 09:11 Go to previous messageGo to next message
BlackSwan
Messages: 22837
Registered: January 2009
Senior Member
EM can only be configured to interact with a single instance at a time.
Re: EM is not running? try to start but failed [message #547547 is a reply to message #547510] Wed, 14 March 2012 12:01 Go to previous messageGo to next message
janakors
Messages: 177
Registered: September 2009
Senior Member
@john, Yes on 2nd node, but cant open EM in internet explorer on this node and the error at 1st node
2012-02-29 14:18:48,971 Thread-1 Starting Agent 10.2.0.4.2 from /u01/app/oracle/product/11.2.0/dbhome (00701)
2012-02-29 14:18:48,973 Thread-1 <Agent Startup> : Startup of HTTP LISTENER failure (00716)


Regards
Re: EM is not running? try to start but failed [message #547550 is a reply to message #547547] Wed, 14 March 2012 12:24 Go to previous messageGo to next message
John Watson
Messages: 4610
Registered: January 2010
Location: Global Village
Senior Member
Quote:
Yes on 2nd node,
So it's working. Thank heavens we finally have the answer: you do not have a problem.
Re: EM is not running? try to start but failed [message #547561 is a reply to message #547550] Wed, 14 March 2012 13:16 Go to previous message
janakors
Messages: 177
Registered: September 2009
Senior Member
but then what does this mean on 2nd node
2012-02-29 14:18:48,971 Thread-1 Starting Agent 10.2.0.4.2 from /u01/app/oracle/product/11.2.0/dbhome (00701)
2012-02-29 14:18:48,973 Thread-1 <Agent Startup> : Startup of HTTP LISTENER failure (00716)


any guideline

Regards

and thank you for your time
Previous Topic: Job giving error at Schedule page
Next Topic: Overwriting Dump FIles in Enterprise Manager
Goto Forum:
  


Current Time: Tue Sep 30 05:09:16 CDT 2014

Total time taken to generate the page: 0.12126 seconds