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. Nothing obvious in the AWS console. I'm using both my root AWS keys as well as IAM generated keys with full admin rights and no love.
I do have one running cluster; does that need to be stopped or paused before I try to launch more?
Regards, Chris
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 dag@sonsorol.org wrote:
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. Nothing obvious in the AWS console. I'm using both my root AWS keys as well as IAM generated keys with full admin rights and no love.
I do have one running cluster; does that need to be stopped or paused before I try to launch more?
Regards, Chris
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/
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 dannon.baker@gmail.com wrote:
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 dag@sonsorol.org wrote:
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. Nothing obvious in the AWS console. I'm using both my root AWS keys as well as IAM generated keys with full admin rights and no love.
I do have one running cluster; does that need to be stopped or paused before I try to launch more?
Regards, Chris
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/
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.
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 c3.8xlarge instance type (compute optimized 8x, 60GB memory), which will launch successfully.
On Fri, Oct 10, 2014 at 1:35 PM, Chris Dagdigian dag@sonsorol.org wrote:
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.
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 interface for my currently running cluster to finish the EBS snapshot process needed to instantiate a shared cluster. I just need to feed it the shared cluster string but the EBS snapshot is going pretty slowly.
If I run into issues I'll tear down my hand-launched version and will go back to cloudlaunch and c3.8xlarge. Thanks!
Regards, Chris
Dannon Baker wrote:
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 c3.8xlarge instance type (compute optimized 8x, 60GB memory), which will launch successfully.
galaxy-dev@lists.galaxyproject.org
-
Chris Dagdigian -
Dannon Baker