EM13 - SSH Keys Fails With "Algorithm Negotiation Fail"
(Doc ID 2982829.1)
Last updated on OCTOBER 24, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.4.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Enterprise Manager Base Cloud Control (OEM) Setup -> Security -> Named Credentials -> SSH Keys Credentials fails with "Algorithm negotiation fail"
$ <Agent_Base>/agent_inst/sysman/log/gcagent.log
INFO - SSHProcessBuilder: Setting ServerAliveInterval=150000 ms
INFO - >>> Reporting exception: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: Algorithm negotiation fail (request id 1) <<<
oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: Algorithm negotiation fail
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.executeJobTask(PerformOperationAction.java:385)
INFO - >>> Reporting exception: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: Algorithm negotiation fail (request id 1) <<<
oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: Algorithm negotiation fail
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.executeJobTask(PerformOperationAction.java:385)
Changes
Enterprise Manager Agent communication was working fine until Solaris 11.4 upgraded from SRU54 to SRU61.
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 |
Changes |
Cause |
Solution |
References |