<?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: CM machine crashes, re-install CM on new machine and add existing Hosts(datanodes) in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CM-machine-crashes-re-install-CM-on-new-machine-and-add/m-p/81357#M84488</link>
    <description>Thanks a lot, this works for me.</description>
    <pubDate>Mon, 22 Oct 2018 17:58:51 GMT</pubDate>
    <dc:creator>manjj</dc:creator>
    <dc:date>2018-10-22T17:58:51Z</dc:date>
    <item>
      <title>CM machine crashes, re-install CM on new machine and add existing Hosts(datanodes)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CM-machine-crashes-re-install-CM-on-new-machine-and-add/m-p/81337#M84486</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a situation where the whole cluster was installed and managed by CM6/CDH6, 1 machine for CM, 4 other machines for CDH, embedded DB is not use, mysql is deployed as external DB. It runs well but then the CM machine crashed due to hardware failure. It there a way to replace the hardware and reinstall teh same version of CM and add existing hosts(datanodes) to the same cluster again?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If only there is a way to re-install the CM machine after it crashes, and be able to add hosts machines to an existing cluster that is previously installed/managed by the same version of CM, it will be sufficient for us.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried to add existing hosts(datanodes) but installation stopped with below message at Cluster Installation -&amp;gt; Install Parcels&lt;BR /&gt;Src file /opt/cloudera/parcels/.flood/CDH-5.15.1-1.cdh5.15.1.p0.4-el6.parcel/CDH-5.15.1-1.cdh5.15.1.p0.4-el6.parcel does not exist&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ParcelError.png" style="width: 600px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/4942i2F17F25AD8CDF671/image-size/large?v=v2&amp;amp;px=999" role="button" title="ParcelError.png" alt="ParcelError.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestion? am I doing right way, is there any othe correct way to achive this?&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 05:56:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CM-machine-crashes-re-install-CM-on-new-machine-and-add/m-p/81337#M84486</guid>
      <dc:creator>manjj</dc:creator>
      <dc:date>2018-10-22T05:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: CM machine crashes, re-install CM on new machine and add existing Hosts(datanodes)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CM-machine-crashes-re-install-CM-on-new-machine-and-add/m-p/81354#M84487</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/30046"&gt;@manjj&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you lost your database and then reinstalled CM, the agents will not complete the heartbeat to the new CM since the cm_guid does not match the value in CM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To correct this, on all hosts with agents running:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- # rm /var/lib/cloudera-scm-agent/cm_guid&lt;/P&gt;&lt;P&gt;- # service cloudera-scm-agent restart&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think the reason you are seeing those errors in the parcels page is because the agents are in bad health... due to the cm_guid.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the cm_guid is generated by CM and the agent stores it to make sure the agent does not communicate with a CM / database that is unexpeted.&amp;nbsp; The process of removing it will allow the agent to see that it should now accept communication with the new CM server/db that you have.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 16:47:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CM-machine-crashes-re-install-CM-on-new-machine-and-add/m-p/81354#M84487</guid>
      <dc:creator>bgooley</dc:creator>
      <dc:date>2018-10-22T16:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: CM machine crashes, re-install CM on new machine and add existing Hosts(datanodes)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CM-machine-crashes-re-install-CM-on-new-machine-and-add/m-p/81357#M84488</link>
      <description>Thanks a lot, this works for me.</description>
      <pubDate>Mon, 22 Oct 2018 17:58:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CM-machine-crashes-re-install-CM-on-new-machine-and-add/m-p/81357#M84488</guid>
      <dc:creator>manjj</dc:creator>
      <dc:date>2018-10-22T17:58:51Z</dc:date>
    </item>
  </channel>
</rss>

