My Oracle Support Banner

EM 13C: Exadata Storage Server Root Credentials Failing With Error "Failed to get operation result within specified timeout: 30000 msec" During Exadata Machine Discovery (Doc ID 3073448.1)

Last updated on FEBRUARY 25, 2025

Applies to:

Enterprise Manager for Exadata - Version 13.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

During Exadata Machine discovery, Exadata Storage Server Root Credentials Failing With Error "Failed to get operation result within specified timeout: 30000 msec"

Error stack from Agent log showing : <AGENT_INST>/sysman/log/gcagent.log

2025-02-05 16:40:43,634 [399:D5C77768:HTTPListener--399 (DispatchRequests OMS.console@189297@oracle-oem=>[173875204360001])] INFO - >>> Dispatching request: PerformOperationRequest (perl authscheme=SSH_PASSWORD username:root @ [HostInfo:10.10.10.10 22]! jobId=OMS.console@189297@oracle-oem=>[173875204360001]) <<<
2025-02-05 16:40:43,635 [399:D5C77768] INFO - Job Attributes: {JobID=OMS.console@189297@oracle-oem=>[173875204360001], KeepAliveRequest=false} Job Command: {perl}
2025-02-05 16:41:13,638 [399:D5C77768] INFO - >>> Reporting exception: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: DefaultConnectFuture[root@/10.10.10.10:22]: Failed to get operation result within specified timeout: 30000 (request id 1) <<<
oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: DefaultConnectFuture[root@/10.10.10.10:22]: Failed to get operation result within specified timeout: 30000
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.executeJobTask(PerformOperationAction.java:385)
at oracle.sysman.gcagent.dispatch.cxl.PerformOperationAction.satisfyRequest(PerformOperationAction.java:159)
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:245)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:114)
at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:53)
at oracle.sysman.gcagent.task.DiagWrappedAction.call(DiagWrappedAction.java:52)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at oracle.sysman.gcagent.task.SingleActionTask.run(SingleActionTask.java:76)
at oracle.sysman.gcagent.dispatch.DispatchRequestsTask.run(DispatchRequestsTask.java:67)

 

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.