EM 12c, EM 13c: Enterprise Manager Cloud Control Agent Start Fails With Error: TM Listener Failed at Startup and Possible Port Conflict (Doc ID 1390802.1)

Last updated on MAY 06, 2017

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
Information in this document applies to any platform.

Symptoms

The command: $/AGENT_INST/bin/emctl start agent

fails with the following error:

Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
Starting agent ........... failed  
TM Listener failed at Startup 
Possible port conflict: Retrying the operation....... 
Failed to start the agent after 5 attempts. Please check that the port is available.
Consult the log files in: /u01/agent12c/agent_inst/sysman/log

OR

Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
Starting agent ......... failed.
HTTP Listener failed at Startup
Possible port conflict on port(3872): Retrying the operation...


.../agent_inst/sysman/log/gcagent.log  reports the following message

2012-01-02 10:33:10,496 [1:3305B9] WARN - *jetty*: FAILED SslSelectChannelConnector@0.0.0.0:3872: java.net.BindException: Address already in use
2012-01-02 10:33:10,498 [1:3305B9] WARN - *jetty*: FAILED org.eclipse.jetty.server.Server@5db5ae: java.net.BindException: Address already in use
2012-01-02 10:33:10,508 [1:3305B9] WARN - Agent failed to Startup for TM Listener in step 0
oracle.sysman.gcagent.comm.agent.FatalException: unable to start the HTTP server on port: 3872
2014-10-29 04:36:23,047 [1:3305B9:main] INFO - Agent is starting up
2014-10-29 04:36:24,604 [1:3305B9] WARN - Agent failed to Startup for HTTP Listener in step 0
oracle.sysman.gcagent.comm.agent.FatalException: unable to start the HTTP server on port: 3872
at oracle.sysman.gcagent.comm.agent.http.HTTPListener.start(HTTPListener.java:875)
Caused by: java.net.BindException: Address already in use

OR

.../agent_inst/sysman/log/emdctlj.log reports the following exceptions

2014-11-29 14:19:20,474 [main] INFO - unable to connect to the agent at https://virtcnn.oracle.com:3872/emd/lifecycle/main/ [No route to host]
oracle.sysman.emSDK.agent.comm.exception.ConnectException: unable to connect to the agent at https://cmkm.oracle.com:3872/emd/lifecycle/main/ [No route to host]
.....
at oracle.sysman.gcagent.clients.emdctlj.EmdCtl.parseAndExecute(EmdCtl.java:151)
at oracle.sysman.gcagent.clients.emdctlj.EmdCtl.main(EmdCtl.java:416)
Caused by: java.net.NoRouteToHostException: No route to host



Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms