Anyone else having issues using cloudman version of galaxy?
No matter what set of AWS keys I use to try to start a new galaxy
cluster I always get the vague
Bad Request : Instance failure, but no specific error was detected.
Please check your AWS Console.
... error on the launch screen.
Hi Chris,
How are you trying to start these clusters?
And, the one you started successfully, how did you start it?
-Dannon
On Fri, Oct 10, 2014 at 1:24 PM, Chris Dagdigian d...@sonsorol.org wrote:
Anyone else having issues using cloudman version of galaxy?
No matter what set of AWS keys I
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? I can check the logs for more detailed
launch failures, if so.
On Fri, Oct 10, 2014 at 1:27 PM, Dannon Baker
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
The errors I'm seeing in the logs relate to virtualization required baked
into the AMI for the large memory instances. This is an error on our side
related to new instance types.
What I'd recommend to get off the ground immediately (with reasonable
memory on a node) would be to use the
Much appreciated - thanks again for the diagnosis and helping me confirm
that I was not fat-fingering anything on my end!
Currently I have a c3.4xlarge instance that booted directly from the AWS
console using the current AMI referenced on the cloudlaunch page. It's
waiting at the cloudman admin
