EM 13c: How to Avoid False Agent Unreachable Alerts Followed by Clear Alerts Despite Agents are UP and Running
(Doc ID 2634649.1)
Last updated on NOVEMBER 26, 2021
Applies to:Enterprise Manager Base Platform - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
In some of the environments, due to intermittent network latency between the OMS and agents, EM generates agent unreachable alerts.
Example alert as follows:
Message=Agent is unable to communicate with the OMS. (REASON = Agent is Unreachable (REASON : Agent to OMS Communication is broken. failed to read status code in ping HTTP response)
$<AGENT_INST>/sysman/log/emagent.nohup reports following errors in some of these cases.
$<AGENT_INST>/sysman/log/gcagent.log reports following errors:
o.s.emSDK.agent.comm.exception.CommIOException [failed to read status code in ping HTTP response]
java.net.SocketTimeoutException [Read timed out]
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