My Oracle Support Banner

After Step 3 of BDA V4.7 Upgrade Rebooted Nodes Come Back Online with "/root/BDA_REBOOT_FAILED" Due to "ERROR: Wrong Hadoop parcel version" or "/root/BDA_REBOOT_WARNINGS" Due to "WARNING:Wrong Alternatives for Hadoop" (Doc ID 2218123.1)

Last updated on JULY 01, 2018

Applies to:

Big Data Appliance Integrated Software - Version 4.7.0 to 4.8.0 [Release 4.7 to 4.8]
Linux x86-64

Symptoms

During upgrade to BDA V4.7 after the Step 3 reboot it is found that one or more nodes come back online but /root/BDA_REBOOT_SUCCEEDED is not present. Instead one of these files is found:

/root/BDA_REBOOT_FAILED
or
/root/BDA_REBOOT_WARNINGS

 

Detailed symptoms are as below. The output here is based on a BDA V4.6 to 4.7 upgrade.

1. On one or more nodes: /root/BDA_REBOOT_FAILED or /etc/BDA_REBOOT_WARNINGS is found instead of /root/BDA_REBOOT_SUCCEEDED.

2. The file /root/BDA_REBOOT_FAILED contains output like below on a 4.6 to 4.7 upgrade: 

# more /root/BDA_REBOOT_FAILED
  
ERROR: Wrong Hadoop parcel version :
INFO: Expected Hadoop parcel version : 5.8.0
ERROR: Big Data Appliance failed software validation checks

The file /root/BDA_REBOOT_WARNINGS contains output like below: 

# more /root/BDA_REBOOT_WARNINGS
  
WARNING: Wrong Alternatives for Hadoop :
INFO: Expected Alternatives for Hadoop : non-empty
WARNING: Big Data Appliance warnings during software validation checks

  

3. The file /root/bda_reboot_status contains the content of the /etc/BDA_REBOOT_FAILED or /etc/BDA_REBOOT_WARNINGS although everything else is fully healthy.  

For example in the case of /root/BDA_REBOOT_FAILED /root/bda_reboot_status contains the error, with everything else being reported as healthy.

# more /root/bda_reboot_status
  
SUCCESS: Found BDA v3 server : SUN SERVER X4-2L
SUCCESS: Correct processor info : Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
SUCCESS: Correct number of types of CPU : 1
SUCCESS: Correct number of CPU cores : 32
SUCCESS: Sufficient GB of memory (>=63): 63
...
SUCCESS: Correct puppet version : 3.6.2
SUCCESS: Correct MySQL version : 5.6.32
SUCCESS: All required programs are accessible in $PATH
SUCCESS: Correct bda-monitor status : bda monitor is running
ERROR: Wrong Hadoop parcel version :
INFO: Expected Hadoop parcel version : 5.8.0
ERROR: Big Data Appliance failed software validation checks 

4. Running "hadoop version" on the node shows the expected 5.8.0 version: 

# hadoop version
  
Hadoop 2.6.0-cdh5.8.0
Subversion http://github.com/cloudera/hadoop -r 19981e671bd2be423f95454301b15d230e8a29e9
Compiled by jenkins on 2016-07-25T20:18Z
Compiled with protoc 2.5.0
From source with checksum 30d94697b6a69ad7b72ac431285a52a
This command was run using /opt/cloudera/parcels/CDH-5.8.0-1.cdh5.8.0.p1769.1751/jars/hadoop-common-2.6.0-cdh5.8.0.jar

5. Running "bdachecksw" on the node as 'root'  is fully successfully. No errors are raised. 

# bdachecksw 
...
SUCCESS: Correct bda-monitor status : bda monitor is running
SUCCESS: Hadoop parcel version is correct: CDH-5.8.0
SUCCESS: Hadoop parcel native libraries are correct
SUCCESS: Alternatives for Hadoop version is correct: CDH-5.8.0
SUCCESS: Big Data Appliance software validation checks succeeded

  

 

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.