My Oracle Support Banner

Upgrading Oracle Big Data Appliance from 2.5.0 to 3.0.1 Release Fails during Step 7 on Addyarn Can Not Log into Cloudera Manager (Doc ID 1910417.1)

Last updated on NOVEMBER 12, 2019

Applies to:

Big Data Appliance Integrated Software - Version 3.0.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.

  

The symptoms are:

1. When upgrading to BDA V3.0.1 from BDA 2.5 Step 7 of the Mammoth upgrade fails with:

Error [8425]: (//bdanode01.example.com//Stage[main]/Hadoop::Addyarn/Exec[add_yarn]/returns) change from notrun to 0 failed:
 /opt/oracle/BDAMammoth/bdaconfig/tmp/addyarn.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/addyarn.out returned 1
instead of one of [0] at /opt/oracle/BDAMammoth/puppet/modules/hadoop/manifests/addyarn.pp:46

After this you can not log into Cloudera Manager (CM):

2.  From Node 3 checking the CM server status shows:

  

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.