Yes- I know that it loads in the workaround that you created, but it doesn't run. The non-workaround version running fine until the last Saturday of June. I know that Greg, who installed it, hasn't touched it in months. Could this be related to the update that was recently completed? That was supposed to be fixed last week. Is there any news? Thanks, Deniz


On Tue, Jul 30, 2013 at 11:35 AM, Dannon Baker <dannon.baker@gmail.com> wrote:
Yes, I tried it and everything appeared to load fine using the url indicated above.  The data volume was mounted correctly, and it appears the custom installation is in place though I would have no idea what it is or does.

Did you install all the custom stuff originally?  If not, it may be useful to talk to the person that did to find out if they're able to poke at it.  That file that's indicated as missing (csamtools.so) is actually there if you take a look, and I'd expect it should all work if initialized correctly.


On Tue, Jul 30, 2013 at 10:10 AM, Deniz Erezyilmaz <denizere@gmail.com> wrote:
HI - did you find anything with the share string? Thanks, Deniz


On Fri, Jul 26, 2013 at 3:32 PM, Dannon Baker <dannon.baker@gmail.com> wrote:
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 <denizere@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.baker@gmail.com> wrote:
On Thu, Jul 25, 2013 at 4:47 PM, Deniz Erezyilmaz <denizere@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