EM Event: Warning – Agent has stopped monitoring. The following errors are reported : Read timed out.

Receiving false alert ‘Host
Down – Detected by Partner Agent
‘ for agent shutdown

OR

Following notification is
reported frequently for agent

Agent has stopped monitoring. The following errors are reported :
Read timed out

after few seconds, would
receive the following notification  from partner Agent

Host Up(Unmonitored) – Detected by partner Agent
Agent is UP and healthy
during the timestamp of issue
This is due to Bug
19821060.
The partner agent sends
false notification due to network issues. To avoid this apply
the latest patch as per MOS note id 1900943.1. or use the workaround below.



1. To know partner agent name , execute the following query from repository database :
SQL>select target_agent.target_name “Target Agent”, partner_agent.target_name “Partner Agent”
from EM_AGENT_BUDDY_MAP eabm, mgmt_targets target_agent, mgmt_targets partner_agent
where eabm.buddy_target_guid = partner_agent.target_guid
and eabm.agent_target_guid = target_agent.target_guid;

1. Stop agent
$/AGENT_INST/bin/emctl stop agent

2. Set property AgentPersistenceTimeout value to 120

$/AGENT_INST/bin/emctl setproperty agent  -allow_new -name AgentPersistenceTimeout -value 120
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
EMD setproperty succeeded

$/AGENT_INST/bin/emctl getproperty agent -name AgentPersistenceTimeout
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
AgentPersistenceTimeout=120
3. Start agent

$/AGENT_INST/bin/emctl start agent

  • September 15, 2015 | 20 views
  • Comments