Mammoth 2.0.1 Fails at Step 12 with "Validation of directories of namenode (bda01node02) failed" (Doc ID 1522753.1)

Last updated on MARCH 23, 2014

Applies to:

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

Symptoms

Installing a fresh install (not an upgrade) of Mammoth version 2.0.1 fails at step 12. The puppet scripts failed on one of the nodes:

ERROR: Puppet agent run on node bda01node03 had errors. List of errors follows

Jan 22 13:15:02 bda01node01 puppet-master[25994]: (//bda01node03.example.com//Stage[main]/Hadoop::Startsvc2/Exec[setup_scm]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm.out returned 1 instead of one of [0] at /opt/oracle/BDAMammoth/puppet/modules/hadoop/manifests/startsvc2.pp:247

 

On node03 the log file  (/opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm.out) just shows this:

==============================================================

Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_commands.out

Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_service_commands_restart.out

Command ID is 28

......

Command 28 finished after 35 seconds

Operation completed successfully

Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_bda_services_hdfs_roles.out

Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_bda_services_hdfs_commands_hdfsEnableHa.out

Command ID is 41

..

Command 41 finished after 15 seconds

Operation failed

Result Message is:   "Validation of directories of namenode (bda01node02) failed. See error log for details. See error message and logs for cause of failure. After addressing the cause of failure, press 'Retry'. Alternatively, revert the performed steps using the 'Disable High Availability' action and try 'Enable High Availability' again. Note that the contents of the shared edits directory and the Standby NameNode's name directories need to be deleted before trying again. If this is undesirable, perform the remaining steps manually using the commands available in 'Actions'.",

 

 The BDA install log on node01 shows a similar message:

============== cat /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-bda01node03-20130122131402.log ==============

Jan 22 13:14:08 bda01node01 puppet-master[25994]: Compiled catalog for bda01node03.example.com in environment production in 0.48 seconds

Jan 22 13:15:02 bda01node01 puppet-master[25994]: (//bda01node03.example.com//Stage[main]//Yumrepo[bda]/baseurl) baseurl changed 'http://bda01node01-master.example.com/bda' to 'http://bda01node01.example.com/bda'

Jan 22 13:15:02 bda01node01 puppet-master[25994]: (//bda01node03.example.com//Stage[main]/Hadoop::Startsvc2/Exec[setup_scm]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm.out returned 1 instead of one of [0] at /opt/oracle/BDAMammoth/puppet/modules/hadoop/manifests/startsvc2.pp:247

Jan 22 13:15:02 bda01node01 puppet-master[25994]: (//bda01node03.example.com/Puppet) Finished catalog run in 53.87 seconds

=============================================================================================

 

Changes

 This occurred during an installation of Mammoth version 2.0.1 after Mammoth version 1.0.3 was installed previously. The version 2.0.1 image was also installed prior to running Mammoth 2.0.1.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms