EM 13c: Post Upgrade to EM 13.4 / 13.5 Version, All the Agents Failed to Communicate with OMS and Console Access Fails With SLB URL
(Doc ID 2671586.1)
Last updated on OCTOBER 13, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.4.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
After upgrading the Multi-OMS environment with SLB to 13.4 or 13.5,
1. Users are unable to access Enterprise Manager console using the SLB host name in the browser.
However, Connections to the Enterprise Manager Console using actual OMS host names in the browser works fine.
2. All agents failed to communicate with the OMS Servers.
$emctl status agent command output 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.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
Health Monitors for Upload as well as Console are shown as DOWN in SLB Console.
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 |