Stopping Blackout Fails Due to Agent Unavailability with error "Unable to stop blackout due to agent unavailability" and "remote api has timed out"

(Doc ID 1335191.1)

Last updated on AUGUST 28, 2013

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.5 to 11.1.0.1 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 28-Aug-2013***

Symptoms

The error below is reported on the Enterprise Manager Grid Control Console when stopping a blackout :

'Error: Unable to stop blackout due to agent unavailability'. Retry 'stop blackout' when agent becomes available.


However, the agent is running and available on the targer server:

[agent11g]/opt/app/oracle/product/agent11g>$ORACLE_HOME/bin/emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home : /opt/app/oracle/product/agent11g
Agent binaries : /opt/app/oracle/product/agent11g
Agent Process ID : 3391498
Parent Process ID : 381158
Agent URL : https://AGENTHOSTNAME.DOMAIN:3872/emd/main/
Repository URL : https://OMSHOSTNAME.DOMAIN:4900/em/upload
Started at : 2011-12-05 10:18:58
Started by user : oracle
Last Reload : 2011-12-05 10:24:09
Last successful upload : 2011-12-05 11:09:12
Total Megabytes of XML files uploaded so far : 6.15
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 14.31%
Last successful heartbeat to OMS : 2011-12-05 11:49:47
---------------------------------------------------------------
Agent is Running and Ready

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms