My Oracle Support Banner

On Oracle Big Data Appliance(BDA) Errors are Noticed During Restarting CDH Services in Cloudera Manager(CM) (Doc ID 1913995.1)

Last updated on APRIL 08, 2020

Applies to:

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

 

On Oracle Big Data Appliance(BDA) trying to restart some/All of the CDH services(Yarn, Hue, Hive ..etc) in Cloudera Manager fail with below error

Command failed to start: com.cloudera.cmf.service.DaemonRoleHandler$ProcessSupplierException: com.cloudera.cmf.service.config.ConfigGenException: Unable to parse XML safety valve

There are NO manual configuration changes made for any of the CDH services failing to start. But error seems to be on the following safety valve parameters:

  1. JobHistory Server Default Group / Advanced JobHistory Server Advanced Configuration Snippet (Safety Valve) for mapred-site.xml
  2. NodeManager Default Group / Advanced NodeManager Advanced Configuration Snippet (Safety Valve) for yarn-site.xml
  3. Oozie Server Default Group / Advanced Oozie Server Advanced Configuration Snippet (Safety Valve) for oozie-site.xml
  4. Service-Wide / Advanced Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml
  5. Gateway Default Group / Advanced Hive Client Advanced Configuration Snippet (Safety Valve) for hive-site.xml

If the safety valve parameters are removed in an attempt to remove the syntax error neither the hdfs service nor yarn service comes up. The errors are:

1. For the hdfs service

NameNode summary: bdanode01.example.com
(Availability: Unknown, Health, Good),
bdanode02.example.com (Availability: Unknown, Health:
Good). This health test is bad because the Service
Monitor did not find an active NameNode


2. For the yarn service

ResourceManger summary:
bdanode03.example.com (Availability: Unknown, Health:
Good),bdanode04.example.com (Availability: Unknown,
Health, Good). This health test is bad because the
Service Monitor did not find an active

This error can be noticed

a) After installing CDH Non-Secure cluster using mammoth 3.0.1 on a 2.6 Image.

OR

b) Adding a Edge server to the Cluster

OR

c) Just restart of Cluster needed for maintainence purpose

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.