My Oracle Support Banner

BDA v4.* Rack Expansion Fails on Timeout [setup_scm_params]/returns Change From Notrun To 0 Failed: Command Exceeded Timeout (Doc ID 2014067.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.1.0 to 4.2.0 [Release 4.1 to 4.2]
Linux x86-64

Symptoms

A BDA V4.1 cluster extension from a full rack to add 3 additional nodes from a starter rack fails as described in:

BDA V4.1 Install of Multirack Cluster Fails at Step 9 with: Command exceeded timeout (Doc ID 1983937.1),

The error from the log is like:
...

Stage[main]/Hadoop::Installpkg2/Exec[start_cloudera_agents]/returns) executed successfully
Apr 23 13:27:47 <HOSTNAME1> puppet-master[12034]: (//<HOSTNAME1>.<DOMAINNAME>/Puppet) Command exceeded timeout
Apr 23 13:27:47 <HOSTNAME1> puppet-master[12034]: (//<HOSTNAME1>.<DOMAINNAME>/Puppet) Wrapped exception:
Apr 23 13:27:47 <HOSTNAME1> puppet-master[12034]: (//<HOSTNAME1>.<DOMAINNAME>/Puppet) execution expired
Apr 23 13:27:47 <HOSTNAME1> puppet-master[12034]: (//<HOSTNAME1>.<DOMAINNAME>//Stage[main]/Hadoop::Installpkg2/Exec[setup_scm_params]/returns) change from notrun to 0 failed: Command exceeded timeout
Apr 23 13:27:47 <HOSTNAME1> puppet-master[12034]: (//<HOSTNAME1>.<DOMAINNAME>//Stage[post]/Miscsetup::Endstep/Notify[end_step])
   Dependency Exec[setup_scm_params] has failures: true


However the workaround from Doc ID 1983937.1 to raise the timeout from: 1200 to 2400 or even 5400 does not resolve the failure.


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.