[galaxy-user] CloudMan Launch Page - Hanging

2012-01-10 Thread mailing list
Hi guys, Is the launch page down today? https://biocloudcentral.herokuapp.com/launch It seems to just hang for me and not load. Let me know if there's anything I can do Thanks Greg ___ The Galaxy User list should be used for the

Re: [galaxy-user] CloudMan Launch Page - Hanging

2012-01-10 Thread mailing list
The page seems to be loading now but I think I'm getting some weird behavior on my started instance. None of the services except SGE started up, and I see this under cluster status log on the main page: * 19:57:11 - Retrieved file 'persistent_data.yaml' from bucket

Re: [galaxy-user] CloudMan Launch Page - Hanging

2012-01-10 Thread Dannon Baker
It looks like you're trying to restart an existing cluster (same cluster name) that previously had galaxy included. Is this the case? If so, you'll need to start it in the same availability zone as the existing volumes. On Jan 10, 2012, at 3:03 PM, mailing list wrote: The page seems to be

Re: [galaxy-user] CloudMan Launch Page - Hanging

2012-01-10 Thread Dannon Baker
In your AWS management console delete the s3 bucket containing the cluster information. In the s3 viewer, the .clusterName file reflects the name of the cluster. You'll probably also want to delete the EBS data volume associated with that cluster, though electing to keep this won't prevent

Re: [galaxy-user] CloudMan Launch Page - Hanging

2012-01-10 Thread mailing list
Ok thanks. That makes sense. Maybe a separate issue but when I do the terminate option from within the CloudMan web interface it says it's terminating but nothing seems to happen. I still see the S3 bucket, the volumes, and the instance continues running. Thanks again for all the answers

Re: [galaxy-user] CloudMan Launch Page - Hanging

2012-01-10 Thread mailing list
Actually nevermind on that. I think I just wasn't waiting long enough. On Tue, Jan 10, 2012 at 3:37 PM, mailing list margeem...@gmail.com wrote: Ok thanks.  That makes sense. Maybe a separate issue but when I do the terminate option from within the CloudMan web interface it says it's