My Oracle Support Banner

13.2 Manual Discovery Fails Discovering the BDA emoms.log Reports: "ERROR applicationModule.BDASSHHelper logp.251 - Connection timed out" (Doc ID 2212585.1)

Last updated on MAY 12, 2018

Applies to:

Enterprise Manager for Big Data Appliance - Version and later
Linux x86-64


13.2 manual discovery fails for BDA. The emoms.log from the OMS host indicates a "Connection timed out" on "BDA SSH":

2016-11-17 11:22:25,563 [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)']
  ERROR console.ConsolePerfCollector logp.251 - Session Expired while processing page with
  viewId null,so tracing for the page is not recorded. ConsolePerfTraceData is
  m_uriPath:/em/console/database/util/Flex ; m_viewId:null ;
  m_jSessionId:* ; m_requestReceivedAt:1479342145549 ; m_requestEndTime:1479342145563 ;
  m_jdbcSelectTime:6 ; m_jdbcFetchTime:0 ; m_noOfSqls:4 ; m_initialRender:false ; m_reqEventType:null ; m_streamRequest:false
2016-11-17 11:22:28,006 [Thread-2885607] ERROR applicationModule.BDASSHHelper logp.251 - Connection timed out
oracle.sysman.emInternalSDK.core.util.ssh.SSHCommException: Connection timed out
  at oracle.sysman.core.util.ssh.SSHClientImpl.runCommandUsingRI(
  at oracle.sysman.core.util.ssh.SSHClientImpl.runCommand(
  at oracle.sysman.bda.discovery.model.applicationModule.BDASSHHelper.executeSSHCommand(
  at oracle.sysman.bda.discovery.model.applicationModule.BDADiscovery.checkIfBDACliPresent(
  at oracle.sysman.bda.discovery.model.applicationModule.BDADiscovery.doHardwareDiscovery(
  at oracle.sysman.bda.discovery.model.applicationModule.BDADiscoveryAMImpl.initializeBDAs(
  at oracle.sysman.bda.discovery.ui.BdaDiscoveryThread.doHardwareDiscovery(



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

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