Hi Martin,
Deleting those volumes would be a problem because all of the data that you upload onto the cloud and analyze through Galaxy are stored on the external EBS volumes. That is the only way to persist the data across cluster instantiations. It looks like we should include a better error/log message if requested volume is not found indicating what happened... 
At this point, you will not be able to retrieve your data. The best thing to do now would be to go to the S3 tab in your AWS console and delete any buckets that were associated with the cluster(s) you created. The names of all of those buckets will start with 'gc-'. Then, you can instantiate a completely new cluster.

BTW, the 2GB EBS volume you see as attached to the running master instance is the actual instance itself. Galaxy Cloud is using EBS AMI's and every running instance will have a volume like like that attached to it. 

Enis

On Wed, Jun 16, 2010 at 1:50 PM, Martin Paradesi <p.martin.samuel.rao@gmail.com> wrote:
Hi Enis,

    Here is the cluster status log:
  • 17:38:19 - Master starting...
  • 17:38:19 - No existing instances found; starting fresh.
  • 17:38:23 - User's bucket 'gc-6658d20fda911b5847f71e33723ea78d' found; retrieving previously used snapshots.
    I see that a 2GB EBS volume is attached to my cluster. Nothing gets appended to this log even after I request Galaxy to start 1 node with 100GB space. I must mention that I performed the following actions before this whole problem started:

   1. I terminated the main Galaxy instance last week on AWS.
   2. I came back this week to find that 2 EBS volumes were still listed in "My Resources" on my dashboard.
   3. After seeing that my bill for these EBS volumes was around $50, I immediately went to EBS instances and detached and deleted those volumes.

   Do you think that this could have caused some problems with starting the Galaxy cloud?

Martin


On Wed, Jun 16, 2010 at 1:22 PM, Enis Afgan <eafgan@emory.edu> wrote:
Hi Martin, 
In the cluster status log, do you maybe get a message like following:
...
  • 17:14:28 - EC2 insufficient capacity error: BotoServerError: 500 Internal Server Error InsufficientInstanceCapacityWe 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
  • 17:14:28 - Encountered problems when starting instances. Currently, keeping track of '0' instances
    • ...

    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. 
    At the same time, we have not made any changes to the public Galaxy Cloud code so it should be operating normally. 
    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's wrong. You can access full instance log at http://ec2-xxxxx/cloud/log

    Enis


    On Wed, Jun 16, 2010 at 11:51 AM, Martin Paradesi <p.martin.samuel.rao@gmail.com> wrote:
    Hi,

       I've been experimenting with Galaxy on the cloud for quite a while. Recently, I faced this problem:

       Whenever I visit http;//ec2xxxxxxx.com/cloud, I can see the Galaxy cloud console. When I click on "Start cluster" and fill out the number of nodes and size of the cluster, nothing happens. More specifically, I still see the "Start cluster" and do not see the "Access Galaxy" 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?

    Thanks,
    Martin

    _______________________________________________
    galaxy-dev mailing list
    galaxy-dev@lists.bx.psu.edu
    http://lists.bx.psu.edu/listinfo/galaxy-dev