My Oracle Support Banner

EM 13c: Enterprise Manager 13c Cloud Control Agent Goes Down Due to Agent Unreachable (REASON = Unable To Connect To The Agent) (Doc ID 2737114.1)

Last updated on JANUARY 17, 2023

Applies to:

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


Frequent alerts are observed from Enterprise Manager (EM) Cloud Control agents. Example:

Agent Unreachable (REASON = Unable to connect to the agent at https://<my agent host>:<my agent port>/emd/main/ [Connection refused (Connection refused)]). Host is reachable.

Looking at the agent_inst/sysman/log/emagent.nohup file, entries like these are observed as a match with the alert timestamp.:

----- 2020-12-14 08:52:59,235::25166::EMAgent exited at 2020-12-14 08:52:59,235 with signal 9 -----
----- 2020-12-14 08:52:59,235::25166::EMAgent has been forcibly killed. -----
----- 2020-12-14 08:52:59,235::25166::Stopping other components. -----
----- 2020-12-14 08:52:59,236::25166::Commiting Process death. -----
----- 2020-12-14 08:52:59,236::25166::writeAbnormalExitTimestampToAgntStmp: exitCause=KILLED : restartRequired=0 -----


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

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