Appreciate the fast reply! I'm at a training session where I hope to
spin up 24 cloudman managed galaxy instances so each student can have a
1:1 ownership of their own cluster

I used this URL to fire up my test cluster:

https://usegalaxy.org/cloudlaunch

... but the test cluster is running out of RAM building bowtie2 index
files so I was trying to start a new cluster based on the currently
running system but started on an instance type with more memory.

And today when I go back to the https://usegalaxy.org/cloudlaunch I'm
getting  the errors I posted

If there is anything in the logs I'd appreciate it. Not sure if I'm
doing anything wrong on my end.

Currently launching the pure base AMI without the cloudlaunch interface
to see if I get further ...

Regards,
Chris


Dannon Baker wrote:
> Just realized you said cloudlaunch in the subject there, so I'm assuming
> that's what you used.  For both working and non-working clusters?  And
> this is cloudlaunch on usegalaxy.org <http://usegalaxy.org>?  I can
> check the logs for more detailed launch failures, if so.
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to