Re: [galaxy-dev] galaxy cloud help
Sure, I'm happy to help, though in the future it's probably best to mail galaxy-dev (cc'd for ticket tracking) directly as there are several of us that may be able to answer and get a response out sooner. That said, your problem is likely due to a permissions issue with the new tool snapshot(snap-b28be9d5) created yesterday that I've fixed, it should work next time you start an instance. Let me know if this doesn't resolve things for you. Thanks! -Dannon On Feb 14, 2012, at 10:57 AM, brennac2@mskcc.org wrote:
I got your email from a [galaxy-dev] entry. Could I ask you for help with a cloud installation problem or could you point me to the best place to submit the question? I will describe the problem below but understand if you are not able to provide support.
Thank you in advance,
Cameron Brennan, MD Human Oncology and Pathogenesis Program Memorial Sloan-Kettering Cancer Center New York
Problem: I have gotten Cloudman running on EC2 but the “Service Status” shows yellow for Applications (green for Data). The Galaxy Daemon won’t start. The log points to a problem mounting galaxyTools and indeed when I SSH in, /mnt/galaxyTools is absent. The log errors are:
“Cannot retrieve reference to volume ‘None’; setting volume id to None. Error: EC2ResponseError: …’.0fb <… lots of characters> … c3aa9
And
Error mounting file system ‘/mnt/galaxyTools’ from ‘/dev/sdg3’, running command ‘/bin/mount /dev/sdg3 /mnt/galaxyTools’ returned code ‘32’ and following stderr” ‘mount: you must specify the filesystem type ‘
=====================================================================
Please note that this e-mail and any files transmitted from Memorial Sloan-Kettering Cancer Center may be privileged, confidential, and protected from disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this communication or any of its attachments is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting this message, any attachments, and all copies and backups from your computer.
Perfect-- it works now. I will email to Galaxy-Dev next time Thank you, -CB On 2/14/12 11:50 AM, "Dannon Baker" <dannonbaker@me.com> wrote:
Sure, I'm happy to help, though in the future it's probably best to mail galaxy-dev (cc'd for ticket tracking) directly as there are several of us that may be able to answer and get a response out sooner.
That said, your problem is likely due to a permissions issue with the new tool snapshot(snap-b28be9d5) created yesterday that I've fixed, it should work next time you start an instance. Let me know if this doesn't resolve things for you.
Thanks!
-Dannon
On Feb 14, 2012, at 10:57 AM, brennac2@mskcc.org wrote:
I got your email from a [galaxy-dev] entry. Could I ask you for help with a cloud installation problem or could you point me to the best place to submit the question? I will describe the problem below but understand if you are not able to provide support.
Thank you in advance,
Cameron Brennan, MD Human Oncology and Pathogenesis Program Memorial Sloan-Kettering Cancer Center New York
Problem: I have gotten Cloudman running on EC2 but the ³Service Status² shows yellow for Applications (green for Data). The Galaxy Daemon won¹t start. The log points to a problem mounting galaxyTools and indeed when I SSH in, /mnt/galaxyTools is absent. The log errors are:
³Cannot retrieve reference to volume ŒNone¹; setting volume id to None. Error: EC2ResponseError: Š¹.0fb <Š lots of characters> Š c3aa9
And
Error mounting file system Œ/mnt/galaxyTools¹ from Œ/dev/sdg3¹, running command Œ/bin/mount /dev/sdg3 /mnt/galaxyTools¹ returned code Œ32¹ and following stderr² Œmount: you must specify the filesystem type Œ
=====================================================================
Please note that this e-mail and any files transmitted from Memorial Sloan-Kettering Cancer Center may be privileged, confidential, and protected from disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this communication or any of its attachments is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting this message, any attachments, and all copies and backups from your computer.
participants (2)
-
brennac2＠mskcc.org -
Dannon Baker