My Oracle Support Banner

EM 13c, 12c: EM Agent Upload or emctl pingOMS Fails with Error: Failure connecting to https://oms_hostname:port/empbs/upload : err Connection refused, Connection establishment timed out (Doc ID 1500066.1)

Last updated on OCTOBER 03, 2019

Applies to:

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

Symptoms

This problem was initially discovered in EM 12.1.0.1 but the solution still applies in the EM 13c product.

 

<Agent instance base>/agent_inst/bin/emctl upload agent

fails with the following error:
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error:full upload has failed: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors. (OMS_DOWN)

<Agent instance base>/agent_inst/bin/emctl pingOMS

Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD pingOMS error: Failure connecting to https://<OMS_HOSTNAME>.<DOMAINNAME>:1159/empbs/upload , err Connection refused

OR

<Agent instance base>/agent_inst/bin/emctl upload agent

fails with the following error

Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
EMD upload error:Unable to connect to the agent at https://<Agent_HOSTNAME>.<DOMAINNAME>:3872/emd/main/ [Connection establishment timed out]

 

<Agent instance base>/agent_inst/sysman/log/gcagent.log reports the following error /exception

2014-10-06 10:04:03,674 [41:C09F1BB3:GC.Upload[2]] INFO - attempting initial heartbeat
2014-10-06 10:04:33,677 [37:88AC468A:GC.SysExecutor.0 (Ping OMS)] WARN - Ping communication error
o.s.emSDK.agent.comm.exception.ConnectException [Failure connecting to https://<OMS_HOSTNAME>.<DOMAINNAME>:4903/empbs/upload, err Connection establishment timed out] java.io.InterruptedIOException [Connection establishment timed out]

 

The following values are shown as 'unknown/none' executing 'emctl status agent'

OMS Version : (unknown)
Last successful upload : (none)
Last attempted upload : (none)
Last successful heartbeat to OMS : (none)

<Agent instance base>/agent_inst/bin/emctl status agent
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 12.1.0.1.0
OMS Version : (unknown)
Protocol Version : 12.1.0.1.0
Agent Home : <Agent instance base>/agent_inst
Agent Binaries : <Agent ORACLE_HOME>/12.1.0.1.0
Agent Process ID : 11263
Parent Process ID : 11182
Agent URL : https://<Agent_HOSTNAME>.<DOMAINNAME>:3872/emd/main/
Repository URL : https://<OMS_HOSTNAME>.<DOMAINNAME>:1159/empbs/upload
Started at : 2012-09-26 10:40:13
Started by user : <USER>
Last Reload : (none)
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0
Number of XML files pending upload : 243
Size of XML files pending upload(MB) : 0.43
Available disk space on upload filesystem : 89.72%
Collection Status : Collections enabled
Last attempted heartbeat to OMS : 2012-09-26 10:40:37
Last successful heartbeat to OMS : (none)

<Agent instance base>/agent_inst/bin/emctl pingOMS

fails with the following error

Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
EMD pingOMS error: Unable to connect to the agent at https://<Agent_HOSTNAME>.<DOMAINNAME>:3872/emd/main/ [Connection establishment timed out]

<Agent instance base>/agent_inst/bin/emctl start agent

fails with the following error

Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
Agent status could not be determined.  Check the agent process
Consult emctl.log and emagent.nohup in: <Agent instance base>/agent_inst/agent_inst/sysman/log/

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.