Support Questions
Find answers, ask questions, and share your expertise

Host Monitor and Service Monitor is not starting after kerberos

Solved Go to solution
Highlighted

Host Monitor and Service Monitor is not starting after kerberos

Expert Contributor

I have sucessfully installed Kerberos and integrated with Cloudera Mnagaer, while starting the cloudera manager services i'm getting below error for Host Monitor and Service Monitor

 

Host Monitor error log

Jan 9, 5:24:56.202 PM 	ERROR 	com.cloudera.cmon.firehose.Main 	

Error creating LevelDB timeseries store in directory /var/lib/cloudera-host-monitor/ts
org.fusesource.leveldbjni.internal.NativeDB$DBException: Invalid argument: /var/lib/cloudera-host-monitor/ts/ts_entity_metadata: does not exist (create_if_missing is false)
	at org.fusesource.leveldbjni.internal.NativeDB.checkStatus(NativeDB.java:194)
	at org.fusesource.leveldbjni.internal.NativeDB.open(NativeDB.java:212)
	at org.fusesource.leveldbjni.JniDBFactory.open(JniDBFactory.java:168)
	at com.cloudera.cmon.tstore.leveldb.LDBUtils.openVersionedDB(LDBUtils.java:246)
	at com.cloudera.cmon.tstore.leveldb.LDBTimeSeriesMetadataStore.openMetadataDB(LDBTimeSeriesMetadataStore.java:149)
	at com.cloudera.cmon.tstore.leveldb.LDBTimeSeriesMetadataStore.<init>(LDBTimeSeriesMetadataStore.java:139)
	at com.cloudera.cmon.firehose.Main.main(Main.java:450)

Service Monitor error log

Jan 9, 5:24:56.475 PM 	ERROR 	com.cloudera.cmon.firehose.Main 	

Error creating LevelDB timeseries store in directory /var/lib/cloudera-service-monitor/ts
org.fusesource.leveldbjni.internal.NativeDB$DBException: Invalid argument: /var/lib/cloudera-service-monitor/ts/ts_entity_metadata: does not exist (create_if_missing is false)
	at org.fusesource.leveldbjni.internal.NativeDB.checkStatus(NativeDB.java:194)
	at org.fusesource.leveldbjni.internal.NativeDB.open(NativeDB.java:212)
	at org.fusesource.leveldbjni.JniDBFactory.open(JniDBFactory.java:168)
	at com.cloudera.cmon.tstore.leveldb.LDBUtils.openVersionedDB(LDBUtils.java:246)
	at com.cloudera.cmon.tstore.leveldb.LDBTimeSeriesMetadataStore.openMetadataDB(LDBTimeSeriesMetadataStore.java:149)
	at com.cloudera.cmon.tstore.leveldb.LDBTimeSeriesMetadataStore.<init>(LDBTimeSeriesMetadataStore.java:139)
	at com.cloudera.cmon.firehose.Main.main(Main.java:450)

What is the issue

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Host Monitor and Service Monitor is not starting after kerberos

Expert Contributor
I fixed the issue, by doing below

Seems Level Database DB is corrupted, and did below

mv /var/lib/cloudera-service-monitor /var/lib/cloudera-service-monitor.moved

mv /var/lib/cloudera-host-monitor /var/lib/cloudera-host-monitor.moved

Then restarted the services again, it worked

View solution in original post

1 REPLY 1
Highlighted

Re: Host Monitor and Service Monitor is not starting after kerberos

Expert Contributor
I fixed the issue, by doing below

Seems Level Database DB is corrupted, and did below

mv /var/lib/cloudera-service-monitor /var/lib/cloudera-service-monitor.moved

mv /var/lib/cloudera-host-monitor /var/lib/cloudera-host-monitor.moved

Then restarted the services again, it worked

View solution in original post