My Oracle Support Banner

EM13c : Agent Unreachable Alerts After OMS Stop Command Executed (Doc ID 2434567.1)

Last updated on AUGUST 13, 2018

Applies to:

Enterprise Manager Base Platform - Version 13.2.0.0.0 to 13.2.0.0.0 [Release 13c]
Information in this document applies to any platform.

Symptoms

In Enterprise Manager (EM) Cloud Control, trying to stop OMS using the 'emctl stop oms' command as part of maintenance, before the OMS completely went down, the following agent unreachable alerts gets generated:

Agent is unable to communicate with the OMS. (REASON = Agent is Unreachable (REASON : Agent to OMS Communication is broken. unable to connect to http
server at https://<OMS Hostname>:4901/empbs/upload. [peer not authenticated] ).

From the OMS emctl log files the following stack is observed between 00:32 to 00:34:

OMS1:
2018-06-11 00:32:05,708 [main] INFO wls.OMSController main.220 - Executing emctl command : stop
2018-06-11 00:34:57,745 [main] INFO commands.BaseCommand logAndPrint.653 - Oracle Management Server Successfully Stopped

OMS2:
2018-06-11 00:32:03,345 [main] INFO wls.OMSController main.220 - Executing emctl command : stop
2018-06-11 00:33:07,517 [main] INFO commands.BaseCommand logAndPrint.653 - Oracle Management Server is Down

Several alerts with the following message generated between 00:32 to 00:34:

Agent is unable to communicate with the OMS. (REASON = Agent is Unreachable (REASON : Agent to OMS Communication is broken. unable to connect to http
server at https://<OMS Hostname>:4901/empbs/upload. [peer not authenticated] ).

 

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!


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