Galaxy Cloudman relaunch and new launch failures?

Question: Galaxy Cloudman relaunch and new launch failures?

13 months ago by

alishamassa • 20 wrote:

Hello,

For the past week I have been trying to restart a previous instance of Galaxy CloudMan from the url in my appliances in CloudLaunch. Everytime I receive the same error that the webserver times out and cannot connect.

Now just today on the list of my appliances in CloudLaunch I cannot see which instances were successful or not, and the url no longer appears.

I had amazon AWS add a higher limit on my concurrent instances and attempted to launch a new instance as well. On the second page of the form to fill out to launch a new CloudMan appliance where I choose name, what type of virtual hardware, etc, it says "server error" beneath the "advanced CloudMan options" button and absolutely nothing happens when I click the green LAUNCH button at bottom of page.

Anyone else having issues in the last week? What can I try to get CloudMan launched?

Thank you for any help!

cloudman • 609 views

ADD COMMENT • link •

modified 13 months ago by Enis Afgan • 690 • written 13 months ago by alishamassa • 20

As you might have noticed, CloudLaunch was updated late last week with some new features (announcement is still forthcoming) and you discovered a bug that crept up. I'm sitting in a conference workshop now so it'll take me a few hours before I can look at it and work on a fix. I'll post here once I figure it out. Also, how were you restarting your instance, as that feature is not yet exposed?

ADD REPLY • link modified 13 months ago • written 13 months ago by Enis Afgan • 690

I shut it down Saturday 10/14 for the first time, to save a little money. I assumed I could restart the same instance with all my data from the url on the CloudLaunch page but never was able to get the page to load. I assumed I would be able to reopen the page with the "access Galaxy" button that also allows size change and addition of worker nodes, etc. Thanks for all you do, Enis!

ADD REPLY • link written 13 months ago by alishamassa • 20

13 months ago by

Enis Afgan • 690

United States

Enis Afgan • 690 wrote:

I've fixed the issue for launching new instances and updated the server so things should work fine again.

For relaunching the old one, I just realized that got broken with a change of the URL structure we implemented a little while ago (stemming from here https://github.com/gvlproject/cloudbridge/issues/69) and I didn't get around to fixing that yet. However, for the time being, you can use the old launcher available at https://launch.usegalaxy.org/ and relaunch that instance.

ADD COMMENT • link written 13 months ago by Enis Afgan • 690

Hi,

I have been trying to access an old shutdown Galaxy Cloudman instance, the previous URL doesn't work obviously. I launched a new instance from the old version of Cloud launch appliance, using the same instance name - I can see from my AWS account that it has restarted the same old instance.

However when I click on the new URL from My applicances active appliances list - it takes me to a pop up asking for my user name and password as always. However the user name and password don't work - instead of taking me to galaxy it takes me to a blank error page: 401 Authorization Required nginx/1.4.6 (Ubuntu)

Is it broken for good? How do I download my genomic data off this old instance so I can delete it permanently? Thank you

ADD REPLY • link written 8 months ago by alishamassa • 20

I'm not sure I follow your question(s) exactly but if if you’re trying to access the CloudMan management page, the username there will be ubuntu and the password will be whatever you supplied when you relaunched the cluster most recently. This is not the Galaxy username and password. Not sure if that's the case but just wanted to clarify it.

Now, if I'm misunderstanding and that's not the issue yet all you're trying to do is delete your cluster, it may be easier to just delete it directly from the AWS console. If you log into the AWS console and go to the Volumes page under the EC2 service, you can just delete the volume that's been tagged with the name of the cluster you're trying to delete. Before deleting it, take a note of the cluster bucket name, which is available as on of the volume tags. It will be something like cm-<long string of letters and numbers>. After you've deleted the volume, switch to the S3 service page in the AWS console, look for the bucket with the given name and delete it. That will have cleaned up all the pieces of your cluster.

ADD REPLY • link written 8 months ago by Enis Afgan • 690

Similar posts • Search »