During Upgrade to BDA V4.4 Step 3 Fails-CM Server Process Can Not Start--cloudera-scm-server.out Shows Failure Accessing /usr/java/jdk1.8.0_31 (Doc ID 2118558.1)

Last updated on APRIL 16, 2017

Applies to:

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

Symptoms

During upgrade to BDA V4.4 Step 3 fails because the CM server process will not start. Starting the process on Node 3 fails with:

Monitoring the Cloudera Manager (CM) server logs with tail -f shows:

a) That nothing is written to: /var/log/cloudera-scm-server/cloudera-scm-server.log.
b) But /var/log/cloudera-scm-server/cloudera-scm-server.out reports a failure accessing JAVA_HOME at /usr/java/jdk1.8.0_31 which does not exist on the system. At Step 3, Java has been upgraded to 1.8.0_66. 

 

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