Hi Martin, <div>In the cluster status log, do you maybe get a message like following:</div><div>...</div><div><li>17:14:28 - EC2 insufficient capacity error: BotoServerError: 500 
Internal Server Error

<code>InsufficientInstanceCapacity</code>We
 currently do not have sufficient m1.large capacity in the Availability 
Zone you requested (us-east-1b). Our system will be working on 
provisioning additional capacity. You can currently get m1.large 
capacity by not specifying an Availability Zone in your request or 
choosing us-east-1a.b2bec3a6-28be-4650-9757-57c1c08c2606</li><li>17:14:28
 - Encountered problems when starting instances. Currently, keeping 
track of &#39;0&#39; instances</li><div>...</div><div><br></div><div>If you are, as you can see, the problem is caused by the cloud (i.e., Amazon) and unfortunately there is nothing we can do about it but wait a few hours. </div>

<div>At the same time, we have not made any changes to the public Galaxy Cloud code so it should be operating normally. </div><div>Let us know if this was the problem or something else. If the insufficient capacity is not the problem, could you please send us the contents of the log so we can get a bit better of an idea what&#39;s wrong. You can access full instance log at <a href="http://ec2-xxxxx/cloud/log">http://ec2-xxxxx/cloud/log</a></div>

<div><br></div><div>Enis</div><div><br></div><br><div class="gmail_quote">On Wed, Jun 16, 2010 at 11:51 AM, Martin Paradesi <span dir="ltr">&lt;<a href="mailto:p.martin.samuel.rao@gmail.com">p.martin.samuel.rao@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br><br>   I&#39;ve been experimenting with Galaxy on the cloud for quite a while. Recently, I faced this problem:<br>

<br>   Whenever I visit http;//<a href="http://ec2xxxxxxx.com/cloud" target="_blank">ec2xxxxxxx.com/cloud</a>, I can see the Galaxy cloud console. When I click on &quot;Start cluster&quot; and fill out the number of nodes and size of the cluster, nothing happens. More specifically, I still see the &quot;Start cluster&quot; and do not see the &quot;Access Galaxy&quot; button or whatever used to appear when Galaxy began running. When I go back and look at the EC2 dashboard, I see that only 1 instance is running (the actual Galaxy cloud instance). I refreshed the Galaxy cloud console page several times and waited for about 15 minutes after I entered the required parameters for starting Galaxy cluster. Can you please fix this?<br>


<br>Thanks,<br><font color="#888888">Martin <br>
</font><br>_______________________________________________<br>
galaxy-dev mailing list<br>
<a href="mailto:galaxy-dev@lists.bx.psu.edu">galaxy-dev@lists.bx.psu.edu</a><br>
<a href="http://lists.bx.psu.edu/listinfo/galaxy-dev" target="_blank">http://lists.bx.psu.edu/listinfo/galaxy-dev</a><br>
<br></blockquote></div><br></div>