My Oracle Support Banner

BDA Mammoth Fails Extending CDH Cluster on Step 2 (Doc ID 1618326.1)

Last updated on OCTOBER 30, 2019

Applies to:

Big Data Appliance Integrated Software - Version 2.3.1 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

Extending the CDH cluster with BDA software version 2.3.1 fails running step 2:

The following succeeds creating the mammoth-params file:

[root@bdanode01 BDAMammoth]# ./mammoth -e bdanode07 3
INFO: Logging all actions in /opt/oracle/BDAMammoth/bdaconfig/tmp/bdanode01-20140122192527.log and traces in /opt/oracle/BDAMammoth/bdaconfig/tmp/bdanode01-20140122192527.trc
INFO: Checking configuration file /opt/oracle/bda/install/state/mammoth-saved.params...
INFO: Using saved configuration file /opt/oracle/bda/install/state/mammoth-saved.params
INFO: To use the generated configuration file, remove /opt/oracle/bda/install/state/mammoth-saved.params
INFO: Loading configuration file /opt/oracle/bda/install/state/mammoth-saved.params...
INFO: Reading component versions from /opt/oracle/BDAMammoth/bdaconfig/COMPONENTS
INFO: Nodes from this rack are already in the cluster
Enter extension number (or just if none): 1

SUCCESS: Successfully generated parameter file mammoth-<RACK_NAME>-1.params



However the following error is seen while running step 2 of the mammoth installation:

[root@bdanode01 BDAMammoth]# ./mammoth -s 2
INFO: Logging all actions in /opt/oracle/BDAMammoth/bdaconfig/tmp/STEP-02-20140122192620.log and traces in /opt/oracle/BDAMammoth/bdaconfig/tmp/STEP-02-20140122192620.trc
INFO: Checking configuration file /opt/oracle/BDAMammoth/bdaconfig/../mammoth-<RACK_NAME>.params...
ERROR: An Appliance of name <RACK_NAME> has already been installed.
ERROR: Cannot continue with install. #Step 2#
INFO: Time spent in step 2 SetupPuppet is 0 seconds.
Exiting...

The trace shows that it failed at step 2:

# cat /opt/oracle/BDAMammoth/bdaconfig/tmp/STEP-02-20140122192646.trc
2014-01-22 19:26:46:
  GridSteps::DieTrap('Exiting...') called at GridSteps.pm line 1063
  GridSteps::MsgPrint('EE', 'Cannot continue with install', 2) called at GridSteps.pm line 790
  GridSteps::CheckStepAndLock(2) called at /opt/oracle/BDAMammoth/bdaconfig/GridInst.pl line 272

 

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


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