Hi, Can somebody please help me? I'm trying for hours to connect to Galaxy on Amazon EC2. I did everything according the instructions, but did not succeed. The "Access Galaxy" button in the instance remains grey out. I copied the screen print and the log to the attached file. Can anyone help me please? and another questions: I want to use it to analyze MiSeq results (to align to the human genome). 100 Gb EBS and a large machine are enough? too much? Many thanks, Lilach.
and I terminated a created from the beginning new instanced for the last several hours (at least 5 different instances). All don't work. Lilach 2012/6/14 Lilach Friedman <lilachfr@gmail.com>
Hi, Can somebody please help me? I'm trying for hours to connect to Galaxy on Amazon EC2. I did everything according the instructions, but did not succeed. The "Access Galaxy" button in the instance remains grey out. I copied the screen print and the log to the attached file. Can anyone help me please?
and another questions: I want to use it to analyze MiSeq results (to align to the human genome). 100 Gb EBS and a large machine are enough? too much?
Many thanks, Lilach.
Hi Lilach, It seems you ran into a bug that was introduced in the most recent CloudMan update. It's been fixed now. If you still have your instance up, the way to get around the issue is to simply strip off '/cloud' part of the URL and you'll get to Galaxy. Any new instances will work fine. Thanks for reporting this issue, Enis On Thu, Jun 14, 2012 at 7:49 AM, Lilach Friedman <lilachfr@gmail.com> wrote:
and I terminated a created from the beginning new instanced for the last several hours (at least 5 different instances). All don't work. Lilach
2012/6/14 Lilach Friedman <lilachfr@gmail.com>
Hi, Can somebody please help me? I'm trying for hours to connect to Galaxy on Amazon EC2. I did everything according the instructions, but did not succeed. The "Access Galaxy" button in the instance remains grey out. I copied the screen print and the log to the attached file. Can anyone help me please?
and another questions: I want to use it to analyze MiSeq results (to align to the human genome). 100 Gb EBS and a large machine are enough? too much?
Many thanks, Lilach.
___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at:
From the log, it looks like your cluster is trying to restart from an existing instance and failing. This happens (by design) when you use the same cluster name. Can you send me the galaxy log to see where the failure might be happening? This is available at:
http://<your_ec2_instance>/cloud/root/service_log?service_name=Galaxy&show=all Additionally, when you go directly to your instance (remove /cloud from the url, so it's just http://<your_ec2_instance>/), what do you see? -Dannon On Jun 13, 2012, at 5:47 PM, Lilach Friedman wrote:
Hi, Can somebody please help me? I'm trying for hours to connect to Galaxy on Amazon EC2. I did everything according the instructions, but did not succeed. The "Access Galaxy" button in the instance remains grey out. I copied the screen print and the log to the attached file. Can anyone help me please?
and another questions: I want to use it to analyze MiSeq results (to align to the human genome). 100 Gb EBS and a large machine are enough? too much?
Many thanks, Lilach. <Cluster status log.docx>___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at:
Hi Dannon and Enis, I succeeded to enter cloudman today. Thanks for fixing the bug! Lilach 2012/6/14 Dannon Baker <dannonbaker@me.com>
From the log, it looks like your cluster is trying to restart from an existing instance and failing. This happens (by design) when you use the same cluster name. Can you send me the galaxy log to see where the failure might be happening? This is available at:
http:// <your_ec2_instance>/cloud/root/service_log?service_name=Galaxy&show=all
Additionally, when you go directly to your instance (remove /cloud from the url, so it's just http://<your_ec2_instance>/), what do you see?
-Dannon
On Jun 13, 2012, at 5:47 PM, Lilach Friedman wrote:
Hi, Can somebody please help me? I'm trying for hours to connect to Galaxy on Amazon EC2. I did everything according the instructions, but did not succeed. The "Access Galaxy" button in the instance remains grey out. I copied the screen print and the log to the attached file. Can anyone help me please?
and another questions: I want to use it to analyze MiSeq results (to align to the human genome). 100 Gb EBS and a large machine are enough? too much?
Many thanks, Lilach. <Cluster status log.docx>___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (3)
-
Dannon Baker -
Enis Afgan -
Lilach Friedman