My Oracle Support Banner

Cloudera Management Services in Bad Health - Event Server/Activity Monitor Do Not Start During Oracle Big Data Appliance V2.2.1 Upgrade at Step 8 (Doc ID 1597195.1)

Last updated on APRIL 01, 2017

Applies to:

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


1. During a Mammoth upgrade to BDA V2.2.1 Cloudera Manager(CM) reports that the Cloudera Management Services are in "Bad Health".  This occurs when restarting the Cloudera Manager Service in preparation for reconfiguring roles.  This is at Step 8 of the upgrade.

2. Selecting "mgmt", Cloudera Management Services, reports that the Activity Monitor and Event Server are "Down".  Neither is running.

3. Drilling down into the Event Server logs shows errors like:

Error starting EventServer
java.lang.RuntimeException: Destination /var/lib/cloudera-scm-eventserver/v2 is not an empty directory
at com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager.upgradeIndex(
at com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager.ensureIndexUpgraded(
at com.cloudera.cmf.eventcatcher.server.EventCatcherService.main(

4. Drilling down into the Activity Monitor logs reports MySQL errors indicating duplicate columns/indices like:

ERROR com.cloudera.enterprise.dbutil.SqlFileRunner   
Exception while executing dll scripts
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'BEGIN_TS'
  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance(
  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.