Ahh, ok, I misunderstood and thought you were saying there was a different
error for the workaround.  Are you able to send me the share string
(directly if you want, feel free to drop the list) so that I might take a
look?  There should be no change at all in your instances from before the
new release when using the workaround.

On Fri, Jul 26, 2013 at 8:17 AM, Deniz Erezyilmaz <deniz...@gmail.com>wrote:

> Dannon- the problems that I saw were with the workaround (see last post).
> The instance launches, but the program stops when it can't find something
> (module/dependencies).
> There were also some different steps in setting up the instance. I had to
> create my own key pair, whereas in the past I never had to do that. I guess
> that simply using the share string that Greg at Janelia created made this
> step automatic.
> The cluster was working well at the end of June. The problem arose
> suddenly Saturday June 29, when the share string would not load. Thanks
> again, Deniz
> On Thu, Jul 25, 2013 at 5:19 PM, Dannon Baker <dannon.ba...@gmail.com>wrote:
>> On Thu, Jul 25, 2013 at 4:47 PM, Deniz Erezyilmaz <deniz...@gmail.com>wrote:
>> The workaround doesn't seem to work
>> Can you tell me what happens when you launch with the workaround
>> mentioned previously (
>> https://main.g2.bx.psu.edu/cloudlaunch?ami=ami-da58aab3&bucket_default=gxy-workshop)?
>> This should launch the pre-migration AMI and Cloudman and shouldn't have
>> any issues at all unless your cluster was already wonky.
>> -Dannon
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:

To search Galaxy mailing lists use the unified search at:

Reply via email to