My Oracle Support Banner

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 13.1.1.0.0 and later
Information in this document applies to any platform.

Symptoms

In some of the environments, due to intermittent network latency between the OMS and agents, EM generates agent unreachable alerts.

Example alert as follows:

Host=<host name>
Target type=Agent
Target name=<AgentName>
Categories=Availability
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)
Severity=Critical

$<AGENT_INST>/sysman/log/emagent.nohup reports following errors in some of these cases.

oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Error: Timed out waiting 120 seconds executing command on target.

$<AGENT_INST>/sysman/log/gcagent.log reports following errors:

2020-01-09 09:36:13,195 [580:CDEB16E1] WARN - Ping communication error
o.s.emSDK.agent.comm.exception.CommIOException [failed to read status code in ping HTTP response]
java.net.SocketTimeoutException [Read timed out]

 

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.