Oracle Big Data Appliance - Starting the Event Server in Cloudera Manager During Upgrade Step 8 Raises: ERROR com.cloudera.cmf.eventcatcher.server.EventCatcherService: Error starting EventServer
(Doc ID 1580399.1)
Last updated on APRIL 16, 2017
Applies to:
Big Data Appliance Integrated Software - Version 2.0.1 and laterLinux x86-64
Symptoms
Starting the Event Server in Cloudera Manager (CM) on the Oracle Big Data Appliance (BDA) during a BDA upgrade when the CM version is updated may raise the errors below during Step 8 of the upgrade. The example here is from a BDA upgrade from V2.0.1 to V2.2.1 where CM is being upgraded from CM Version 4.1.2 to CM Version 4.6.3. Errors may be seen at other times/upgrade steps as well.
Note: The Event Server is down in CM as see by navigating: Home > mgmt > Event Server
Errors look like:
1. Errors look like below in earlier BDA versions:
java.lang.RuntimeException: Destination /var/lib/cloudera-scm-eventserver/v2 is not an empty directory
at com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager.upgradeIndex(IndexVersionManager.java:312)
at com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager.ensureIndexUpgraded(IndexVersionManager.java:455)
at com.cloudera.cmf.eventcatcher.server.EventCatcherService.main(EventCatcherService.java:104)
2. Errors may also look like below in later BDA versions:
java.io.FileNotFoundException: /var/lib/cloudera-scm-eventserver/v3/_2onp7.fnm (No such file or directory)
at org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:292)
at org.apache.lucene.index.SegmentInfo.sizeInBytes(SegmentInfo.java:299)
at org.apache.lucene.index.LogMergePolicy.sizeBytes(LogMergePolicy.java:190)
at org.apache.lucene.index.LogByteSizeMergePolicy.size(LogByteSizeMergePolicy.java:45)
3. More complete messaging from the upgrade is below.
2013-08-29 12:46:52,656 INFO com.cloudera.enterprise.Translator: Loading bundle 'tsquery' from 'tsquery_zh_CN.properties'
2013-08-29 12:46:52,870 INFO com.cloudera.cmf.BasicScmProxy: Authenticated to SCM.
2013-08-29 12:46:53,042 INFO com.cloudera.cmf.eventcatcher.server.EventCatcherService: SCM descriptor fetched successfully
2013-08-29 12:46:53,049 INFO com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager: Creating IndexVersionManager for /var/lib/cloudera-scm-eventserver
2013-08-29 12:46:53,049 INFO com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager: Checking for version directory at /var/lib/cloudera-scm-eventserver/version
2013-08-29 12:46:53,049 INFO com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager: Checking for version file at /var/lib/cloudera-scm-eventserver/version/event_schema.version
2013-08-29 12:46:53,057 INFO com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager: Version from file is 0
2013-08-29 12:46:53,057 INFO com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager: Events index upgrade is required.
2013-08-29 12:46:53,057 INFO com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager: Starting Events Index Upgrade
2013-08-29 12:46:53,057 INFO com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager: Upgrading from version 0 to 2
2013-08-29 12:46:53,057 ERROR com.cloudera.cmf.eventcatcher.server.EventCatcherService: 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(IndexVersionManager.java:312)
at com.cloudera.cmf.eventcatcher.upgrade.IndexVersionManager.ensureIndexUpgraded(IndexVersionManager.java:455)
at com.cloudera.cmf.eventcatcher.server.EventCatcherService.main(EventCatcherService.java:104)
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 |
| Solution Steps |
| The steps to restart the Event Server service |