My Oracle Support Banner

BDA Mammoth Fails Extending CDH Cluster on Step 9 (Doc ID 1618335.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.

Running Mammoth step 9 on expansion fails with:

# ./mammoth -s 9 bda 1
INFO: Logging all actions in /opt/oracle/BDAMammoth/bdaconfig/tmp/STEP-09-20140129161443.log and traces in
/opt/oracle/BDAMammoth/bdaconfig/tmp/STEP-09-20140129161443.trc
INFO: Checking configuration file /opt/oracle/BDAMammoth/bdaconfig/../mammoth-bda-1.params...
INFO: This is the install of an additional rack
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: Loading configuration file /opt/oracle/BDAMammoth/bdaconfig/../mammoth-bda-1.params...
INFO: Loading configuration file /opt/oracle/bda/install/state/mammoth-bda-saved.params...
INFO: Reading component versions from /opt/oracle/BDAMammoth/bdaconfig/COMPONENTS
==================================================================================
INFO: Wed Jan 29 16:14:43 CET 2014

INFO: Step 9  SetupMySQL
INFO: Acquiring run lock ...
INFO: Creating nodelist files...
INFO: Creating environment.pp file ...
INFO: Making sure all puppet agents can be accessed.
INFO: Pinging puppet agents
INFO: Setting up MySQL databases. This will take some time ...
INFO: Puppet script successfully sent to node bdanode07
INFO: Puppet script successfully sent to node bdanode08
INFO: Puppet script successfully sent to node bdanode09
INFO: Pinging puppet agents
INFO: Puppet agent run on node bdanode07 completed successfully.
INFO: Check the log file in /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-bdanode07-20140129161519.log
INFO: Puppet agent run on node bdanode08 completed successfully.
INFO: Check the log file in /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-bdanode08-20140129161519.log
INFO: Puppet agent run on node bdanode09 completed successfully.
INFO: Check the log file in /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-bdanode09-20140129161519.log
INFO: Making sure all puppet agents can be accessed.
INFO: Pinging puppet agents
INFO: Adding access from additional nodes to MySQL database. This will take some time ...
INFO: Puppet script successfully sent to node bdanode01
INFO: Pinging puppet agents
ERROR: Puppet agent run on node bdanode01 had errors. List of errors follows

************************************


Many errors seen in output like the following:

Error [6070]: (//bdanode01.example.com//Stage[main]/Mysql::Addnodesmysql/Mysqldb_add[hive]/Exec[grant-hive-db-user]/returns) change
from notrun to 0 failed: /usr/bin/mysql -hbdanode03.example.com -uroot -p'<PASSWORD>' hive -e " grant all on hive.* to
hive@'bdanode07.example.com' identified by '<PASSWORD>' with grant option ;  grant all on hive.* to
hive@'bdanode08.example.com' identified by '<PASSWORD>' with grant option ;  grant all on hive.* to
hive@'bdanode09.example.com' identified by '<PASSWORD>' with grant option ;   "  returned 1 instead of one of [0] at
/opt/oracle/BDAMammoth/puppet/modules/mysql/manifests/addnodesmysql.pp:5




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.