<?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: Cloudbreak cluster creation in AWS failing in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160305#M122690</link>
    <description>&lt;P&gt;I used us-east-1 public cloud image ami-5e20c033 to provision the cloud deployer container, performed a cbd update too.&lt;/P&gt;</description>
    <pubDate>Sat, 21 May 2016 11:59:12 GMT</pubDate>
    <dc:creator>tsg_cquensys</dc:creator>
    <dc:date>2016-05-21T11:59:12Z</dc:date>
    <item>
      <title>Cloudbreak cluster creation in AWS failing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160304#M122689</link>
      <description>&lt;P&gt;I created the role based credentials, and tried to create a cluster M3.large ec2s with the template(miniviable-aws) and  hdp-small-default blueprint, I got the below event logs&lt;/P&gt;&lt;PRE&gt;5/20/2016 11:08:33 PM finaltry - create in progress: Creating infrastructure5/20/2016 11:10:41 PM finaltry - update in progress: Infrastructure creation took 127 seconds5/20/2016 11:10:43 PM finaltry - available: Infrastructure metadata collection finished5/20/2016 11:12:40 PM finaltry - update in progress: Bootstrapping infrastructure cluster5/20/2016 11:13:19 PM finaltry - update in progress: Setting up infrastructure metadata5/20/2016 11:13:19 PM finaltry - update in progress: Starting Ambari cluster containers5/20/2016 11:13:50 PM finaltry - update in progress: Starting Ambari cluster5/20/2016 11:17:02 PM finaltry - update in progress: Building Ambari cluster; Ambari ip:xx.xx.xx.xxxx 5/20/2016 11:44:53 PM finaltry - create failed: Ambari cluster could not be created. Reason: com.sequenceiq.cloudbreak.service.cluster.AmbariOperationFailedException: Cluster installation failed to complete, please check the Ambari UI for more details. You can try to reinstall the cluster with a different blueprint or fix the failures in Ambari and sync the cluster with Cloudbreak later.&lt;/PRE&gt;&lt;PRE&gt;I got this error, when I saw the error log in ambari, Python script has been killed due to timeout after waiting 1800 secs&lt;/PRE&gt;&lt;PRE&gt;So, I changed the timeout to 3600 (agent.package.install.task.timeout=3600) in /etc/ambari-server/conf/ambari.properties in the container&lt;/PRE&gt;&lt;PRE&gt;and restarted the installations individually in Ambari, MySQL server installation takes forever. Is there any workaround please?&lt;/PRE&gt;&lt;PRE&gt;any help is appreciated.Thanks!
                                                &lt;/PRE&gt;</description>
      <pubDate>Sat, 21 May 2016 11:57:16 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160304#M122689</guid>
      <dc:creator>tsg_cquensys</dc:creator>
      <dc:date>2016-05-21T11:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak cluster creation in AWS failing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160305#M122690</link>
      <description>&lt;P&gt;I used us-east-1 public cloud image ami-5e20c033 to provision the cloud deployer container, performed a cbd update too.&lt;/P&gt;</description>
      <pubDate>Sat, 21 May 2016 11:59:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160305#M122690</guid>
      <dc:creator>tsg_cquensys</dc:creator>
      <dc:date>2016-05-21T11:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak cluster creation in AWS failing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160306#M122691</link>
      <description>&lt;P&gt;I've been using cloud break for nearly 4 months. I just started facing this issue past few days. It seems like cloud break deployment on AWS contains some bug that's causing this failure. Can someone help to resolve it please?&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2016 01:31:17 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160306#M122691</guid>
      <dc:creator>praveenmohan197</dc:creator>
      <dc:date>2016-05-24T01:31:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak cluster creation in AWS failing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160307#M122692</link>
      <description>&lt;P&gt;Which version of CBD are you using (&lt;EM&gt;&lt;STRONG&gt;cbd version&lt;/STRONG&gt;&lt;/EM&gt;)?&lt;/P&gt;&lt;P&gt;There was an issue in 1.2.2 (due to an updated systemd version) which has been fixed - download the latest 1.2.3 binary or do a &lt;EM&gt;&lt;STRONG&gt;cbd update&lt;/STRONG&gt;. After that you should do a &lt;/EM&gt;&lt;EM&gt;&lt;STRONG&gt;cbd kill &amp;amp;&amp;amp; cbd regenerate &amp;amp;&amp;amp; cbd start&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2016 02:53:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160307#M122692</guid>
      <dc:creator>jmatyas</dc:creator>
      <dc:date>2016-05-25T02:53:21Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak cluster creation in AWS failing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160308#M122693</link>
      <description>&lt;P&gt;Thanks Janos!&lt;/P&gt;&lt;P&gt;I was using the CBD 1.2.3&lt;/P&gt;&lt;P&gt;I did the below in the image&lt;/P&gt;&lt;P&gt;cbd doctor&lt;/P&gt;&lt;P&gt;===&amp;gt; Deployer doctor: Checks your environment, and reports a diagnose.&lt;/P&gt;&lt;P&gt;uname: Linux ip-xxxxxxx.ec2.internal xxxxxxxxxx.x86_64 #1 SMP Sat Jan 23 04:54:55 EST 2016 x86_64 x86_64 x86_64 GNU/Linux&lt;/P&gt;&lt;P&gt;local version:1.2.2&lt;/P&gt;&lt;P&gt;latest release:1.2.3&lt;/P&gt;&lt;P&gt;[WARN] !!!!!!!!!!!!!!!!!!!!!!!!!!!!&lt;/P&gt;&lt;P&gt;[WARN] Your version is outdated&lt;/P&gt;&lt;P&gt;[WARN] !!!!!!!!!!!!!!!!!!!!!!!!!!!!&lt;/P&gt;&lt;P&gt;[WARN] Please update it by:&lt;/P&gt;&lt;P&gt;  cbd update&lt;/P&gt;&lt;P&gt;docker command exists: OK&lt;/P&gt;&lt;P&gt;docker client version: 1.9.1&lt;/P&gt;&lt;P&gt;docker client version: 1.9.1&lt;/P&gt;&lt;P&gt;ping 8.8.8.8 on host: OK&lt;/P&gt;&lt;P&gt;ping github.com on host: OK&lt;/P&gt;&lt;P&gt;ping 8.8.8.8 in container: OK&lt;/P&gt;&lt;P&gt;ping github.com in container: OK&lt;/P&gt;&lt;P&gt;[cloudbreak@ip-xxxxxxxxxxx cloudbreak-deployment]$ cbd update&lt;/P&gt;&lt;P&gt;Updating /usr/bin/cbd from url: &lt;A href="https://github.com/sequenceiq/cloudbreak-deployer/releases/download/v1.2.3/cloudbreak-deployer_1.2.3_Linux_x86_64.tgz"&gt;https://github.com/sequenceiq/cloudbreak-deployer/releases/download/v1.2.3/cloudbreak-deployer_1.2.3_Linux_x86_64.tgz&lt;/A&gt;&lt;/P&gt;&lt;P&gt;mv: try to overwrite '/usr/bin/cbd', overriding mode 0755 (rwxr-xr-x)? y&lt;/P&gt;&lt;P&gt;[cloudbreak@ip-xxxxxxx cloudbreak-deployment]$ cbd update&lt;/P&gt;&lt;P&gt;I have done the cbd regenerate as well. I will try in the order you advised(&lt;EM&gt;&lt;STRONG&gt;cbd kill &amp;amp;&amp;amp; cbd regenerate &amp;amp;&amp;amp; cbd start) and see what happens. I will post my findings here. Thanks!&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2016 12:28:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160308#M122693</guid>
      <dc:creator>tsg_cquensys</dc:creator>
      <dc:date>2016-05-25T12:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak cluster creation in AWS failing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160309#M122694</link>
      <description>&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Thanks @&lt;/STRONG&gt;&lt;/EM&gt;&lt;A href="https://community.hortonworks.com/users/374/jmatyas.html"&gt;Janos Matyas&lt;/A&gt; &lt;/P&gt;&lt;P&gt;I updated the cbd to 1.2.3 and issued the following commands&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;cbd kill &amp;amp;&amp;amp; cbd regenerate &amp;amp;&amp;amp; cbd start&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;It worked perfectly and built the cluster. Thanks for the help!&lt;/P&gt;,&lt;P&gt;@&lt;A href="https://community.hortonworks.com/users/374/jmatyas.html"&gt;Janos Matyas&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Thank you so much Janos, I updated it to 1.2.3 and issued the commands &lt;EM&gt;&lt;STRONG&gt;cbd kill &amp;amp;&amp;amp; cbd regenerate &amp;amp;&amp;amp; cbd start&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;it worked perfectly and created a cluster, thanks! I am building a spark cluster, with sample blueprint, I will post my experience with spark cluster as well here. &lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2016 10:14:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160309#M122694</guid>
      <dc:creator>tsg_cquensys</dc:creator>
      <dc:date>2016-05-26T10:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak cluster creation in AWS failing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160310#M122695</link>
      <description>&lt;P&gt;Spark cluster also built successfully with cbd1.2.3!&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2016 10:38:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudbreak-cluster-creation-in-AWS-failing/m-p/160310#M122695</guid>
      <dc:creator>tsg_cquensys</dc:creator>
      <dc:date>2016-05-26T10:38:49Z</dc:date>
    </item>
  </channel>
</rss>

