My Oracle Support Banner

EM13c, EM12c: SSH Key Credential Test Fails: Failed to launch process: java.net.ConnectException: Connection refused (Doc ID 2300398.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

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

Symptoms

Enterprise Manager Cloud Control 12c or 13c:

Testing or using an SSH Key credential fails with the error message: Failed to launch process: java.net.ConnectException: Connection refused

The issue may be constant or intermittent - the credential may work sometimes.

The SSH Key credential works on the command line.

 

The following entry appears in <agent_inst>/sysman/log/gcagent.log:

2017-08-16 07:54:09,343 [68164:62B64A69] 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:315)
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.satisfyRequest(PerformOperationAction.java:146)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction._call(ProcessRequestAction.java:145)
at oracle.sysman.gcagent.dispatch.ProcessRequestAction.call(ProcessRequestAction.java:106)
at oracle.sysman.gcagent.dispatch.InlineDispatchCoordinator.dispatchRequest(InlineDispatchCoordinator.java:237)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:111)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:51)

 

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
 Solution A: Allow sshd to listen on IPv4 and IPv6 addresses
 Solution B: Force agent to prefer IPv4 addresses (this requires an agent restart)
 Solution C: Force agent to use a different hostname (and/or port) for ssh key credentials (does not require an agent restart)
References


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