My Oracle Support Banner

EM 13.4: All Agents Failed to Communicate with OMS After Upgrade to EM 13.4 (OMS Servers behind Server Load Balancer) (Doc ID 2723036.1)

Last updated on NOVEMBER 23, 2020

Applies to:

Enterprise Manager Base Platform - Version 13.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Multi OMS Servers behind SLB.

OMS servers are upgraded to EM 13.4. Since then, all agents failed to communicate with the OMS Servers.

$emctl status agent shows:

OMS Version : (unknown)

Heartbeat Status : OMS is unreachable
Last attempted heartbeat to OMS : <Date>
Last successful heartbeat to OMS : (none)

$emctl secure agent fails with the following error:

2020-10-25 04:24:02,341 [main] INFO agent.SecureAgentCmd secureAgent.447 - Checking if HTTPS Upload URL is accessible from the agent...
2020-10-25 04:24:02,341 [main] INFO agent.SecureAgentCmd secureAgent.448 - Accessing: https://<SLBHostName>:4900/empbs/upload
2020-10-25 04:24:02,370 [main] ERROR agent.SecureAgentCmd main.353 - Failed to secure the Agent:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.ibm.jsse2.bc.getPeerCertificateChain(bc.java:179)

From the agent server, wget with the SLB Upload URL hangs / fails

$wget https://<SLBHostName>:4900/empbs/upload --no-check-certificate

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.