My Oracle Support Banner

BDA V4.2 bdacheckcluster Fails with: /tmp/bdacheckcluster_1443553416/hadoophealthsummary.out could not be opened (Doc ID 2061826.1)

Last updated on JANUARY 13, 2020

Applies to:

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

  

1.  Running bdacheckcluster on a BDA V4.2 Kerberos enabled cluster with TLS enabled in Cloudera Manager (CM) fails with:

SUCCESS: Mammoth configuration file is valid.
/tmp/bdacheckcluster_1443553416/hadoophealthsummary.out could not be opened at /opt/oracle/bda/bin/bdacheckcluster line 480, <STDIN> line 2.


Line 480 is checking the health of the Cloudera Manager service and trying to write a health check to  hadoophealthsummary.out in the log directory.


2. Checking the directory "/tmp/bdacheckcluster_1443553492":

a) Shows that there is no hadoophealthysummary.out file:


4. It is noticed that the certificate file  /usr/java/default/jre/lib/security/jssecacerts exits.

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.