<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Host Monitor and Service Monitor is not starting after kerberos in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Host-Monitor-and-Service-Monitor-is-not-starting-after/m-p/49214#M51069</link>
    <description>I fixed the issue, by doing below&lt;BR /&gt;&lt;BR /&gt;Seems Level Database DB is corrupted, and did below&lt;BR /&gt;&lt;BR /&gt;mv /var/lib/cloudera-service-monitor /var/lib/cloudera-service-monitor.moved&lt;BR /&gt;&lt;BR /&gt;mv /var/lib/cloudera-host-monitor /var/lib/cloudera-host-monitor.moved&lt;BR /&gt;&lt;BR /&gt;Then restarted the services again, it worked</description>
    <pubDate>Mon, 09 Jan 2017 16:03:04 GMT</pubDate>
    <dc:creator>kchaitanya</dc:creator>
    <dc:date>2017-01-09T16:03:04Z</dc:date>
    <item>
      <title>Host Monitor and Service Monitor is not starting after kerberos</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Host-Monitor-and-Service-Monitor-is-not-starting-after/m-p/49207#M51068</link>
      <description>&lt;P&gt;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&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Host Monitor error log&lt;/P&gt;
&lt;PRE&gt;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.&amp;lt;init&amp;gt;(LDBTimeSeriesMetadataStore.java:139)
	at com.cloudera.cmon.firehose.Main.main(Main.java:450)&lt;/PRE&gt;
&lt;P&gt;Service Monitor error log&lt;/P&gt;
&lt;PRE&gt;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.&amp;lt;init&amp;gt;(LDBTimeSeriesMetadataStore.java:139)
	at com.cloudera.cmon.firehose.Main.main(Main.java:450)&lt;/PRE&gt;
&lt;P&gt;What is the issue&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2017 13:47:33 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Host-Monitor-and-Service-Monitor-is-not-starting-after/m-p/49207#M51068</guid>
      <dc:creator>kchaitanya</dc:creator>
      <dc:date>2017-01-09T13:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: Host Monitor and Service Monitor is not starting after kerberos</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Host-Monitor-and-Service-Monitor-is-not-starting-after/m-p/49214#M51069</link>
      <description>I fixed the issue, by doing below&lt;BR /&gt;&lt;BR /&gt;Seems Level Database DB is corrupted, and did below&lt;BR /&gt;&lt;BR /&gt;mv /var/lib/cloudera-service-monitor /var/lib/cloudera-service-monitor.moved&lt;BR /&gt;&lt;BR /&gt;mv /var/lib/cloudera-host-monitor /var/lib/cloudera-host-monitor.moved&lt;BR /&gt;&lt;BR /&gt;Then restarted the services again, it worked</description>
      <pubDate>Mon, 09 Jan 2017 16:03:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Host-Monitor-and-Service-Monitor-is-not-starting-after/m-p/49214#M51069</guid>
      <dc:creator>kchaitanya</dc:creator>
      <dc:date>2017-01-09T16:03:04Z</dc:date>
    </item>
  </channel>
</rss>

