Getting 'Failed to launch process' error while setting ssh key based authentication for Unix machines in 12c
(Doc ID 1537714.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Enterprise Manager Base Platform - Version 12.1.0.2.0 to 12.1.0.2.0 [Release 12.1]Information in this document applies to any platform.
Symptoms
Trying to create Named Credential with ssh key-based authentication for machines in 12.1 Cloud Control gives following errors:
Failed to launch process: java.net.ConnectException: Connection refused
gcagent.log in agent logs has following errors:
2012-12-26 12:45:48,600 [220424:5F805C27] INFO - >>> Reporting exception: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: java.net.ConnectException: Connection refused (request id 1) <<<
oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: java.net.ConnectException: Connection refused
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.executeJobTask(PerformOperationAction.java:228)
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.satisfyRequest(PerformOperationAction.java:121)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction._call(ProcessRequestAction.java:128)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction.call(ProcessRequestAction.java:93)
at oracle.sysman.gcagent.dispatch.InlineDispatchCoordinator.dispatchRequest(InlineDispatchCoordinator.java:223)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:109)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:49)
oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: java.net.ConnectException: Connection refused
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.executeJobTask(PerformOperationAction.java:228)
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.satisfyRequest(PerformOperationAction.java:121)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction._call(ProcessRequestAction.java:128)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction.call(ProcessRequestAction.java:93)
at oracle.sysman.gcagent.dispatch.InlineDispatchCoordinator.dispatchRequest(InlineDispatchCoordinator.java:223)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:109)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:49)
This works fine for non-Exadata machines
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 |