<?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 Cloudera Manager 5.7.3 archive missing in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49645#M51861</link>
    <description>&lt;P&gt;Hi, I got stuck in a pretty difficult situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wanted to upgrade my cloudera manager from 5.7.3 to 5.9 and launched stop services with the CM UI.&lt;/P&gt;&lt;P&gt;However I stopped the services but the active commands haven't been finished.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I receive an error message when I want to start the new version of cloudera manager server. I saw in the logs of cloudera-scm-server that I need to go back to the older version (5.7.3) to abort or finish these commands.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue is I can't find anywhere the archive or tarballs of this version of cloudera... &lt;A href="https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.7.3/" target="_blank"&gt;https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.7.3/&lt;/A&gt; doesn't exist...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For information, the command service cloudera-scm-server force_start doesn't work and don't kill the active commands... How can I do? Is there a place where I can get the archive of CM 5.7.3? Or is there a way to delete the active commands? I'm not sure but I think there are written in the amon database in the embedded cloudera manager server database.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your response.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jan 2017 20:25:36 GMT</pubDate>
    <dc:creator>Vjarry</dc:creator>
    <dc:date>2017-01-18T20:25:36Z</dc:date>
    <item>
      <title>Cloudera Manager 5.7.3 archive missing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49645#M51861</link>
      <description>&lt;P&gt;Hi, I got stuck in a pretty difficult situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wanted to upgrade my cloudera manager from 5.7.3 to 5.9 and launched stop services with the CM UI.&lt;/P&gt;&lt;P&gt;However I stopped the services but the active commands haven't been finished.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I receive an error message when I want to start the new version of cloudera manager server. I saw in the logs of cloudera-scm-server that I need to go back to the older version (5.7.3) to abort or finish these commands.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue is I can't find anywhere the archive or tarballs of this version of cloudera... &lt;A href="https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.7.3/" target="_blank"&gt;https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.7.3/&lt;/A&gt; doesn't exist...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For information, the command service cloudera-scm-server force_start doesn't work and don't kill the active commands... How can I do? Is there a place where I can get the archive of CM 5.7.3? Or is there a way to delete the active commands? I'm not sure but I think there are written in the amon database in the embedded cloudera manager server database.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your response.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2017 20:25:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49645#M51861</guid>
      <dc:creator>Vjarry</dc:creator>
      <dc:date>2017-01-18T20:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudera Manager 5.7.3 archive missing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49654#M51862</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/20279"&gt;@Vjarry&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry you hit this issue. &amp;nbsp;I am not certain what happened to Cloudera Manager 5.7.3, but it was likely pulled due to a critical issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In your situation, then, there is a way to work around this as long as you are OK with the commands that are running being killed without completing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If so, you can run the following with the CM 5.9:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;# server cloudera-scm-server force_start&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This tells Cloudera Manager to forcably terminate any running commands and start. &amp;nbsp;If you have any questions or concerns about the commands that are still running, you can post them here as that information should be visible in the error. &amp;nbsp;Note that the error also mentions using force_start (as you should see in your /var/log/cloudera-scm-server/cloudera-scm-server.log.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most times it is OK to kill the commands as your cluster is down anyway, but proceed with caution. &amp;nbsp;We can't tell if it is safe without seeing the commands that are running.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2017 00:46:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49654#M51862</guid>
      <dc:creator>bgooley</dc:creator>
      <dc:date>2017-01-19T00:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudera Manager 5.7.3 archive missing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49655#M51863</link>
      <description>&lt;P&gt;There was no version of CM 5.7.3 released to the public.&lt;/P&gt;&lt;P&gt;We did release&lt;A href="https://community.cloudera.com/t5/Community-News-Release/CDH-5-7-3-released/td-p/44873" target="_self"&gt; CDH 5.7.3.&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You might have had CM 5.7.4 and CDH 5.7.3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2017 02:48:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49655#M51863</guid>
      <dc:creator>surajacharya</dc:creator>
      <dc:date>2017-01-19T02:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudera Manager 5.7.3 archive missing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49664#M51864</link>
      <description>Thanks a lot. I got confused between CM and CDH version. It was in fact CM 5.7.0 which was installed on my other machines.</description>
      <pubDate>Thu, 19 Jan 2017 09:20:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudera-Manager-5-7-3-archive-missing/m-p/49664#M51864</guid>
      <dc:creator>Vjarry</dc:creator>
      <dc:date>2017-01-19T09:20:14Z</dc:date>
    </item>
  </channel>
</rss>

