Cloudman - The Connection Has Timed Out

Question: Cloudman - The Connection Has Timed Out

7.0 years ago by

mailing list • 840 wrote:

Hi Everyone, I'm trying to set up Cloud man. I believe I followed the instructions listed here to a T: http://wiki.g2.bx.psu.edu/Admin/Cloud After launching the instance I even waited 20 minutes before trying to access the public DNS ec2-xxx-xx-xx-xx.compute-1.amazonaws.com/cloud but my browser just says: The connection has timed out The server at ec2-xxx-xx-xx-xx.compute-1.amazonaws.com is taking too long to respond. Any ideas what I should check? I'm stuck. What information would be useful? Info: Zone is us-east-1a Type is m1.large root devide is ebs AMI Name: galaxy-cloudman-2011-03-22 Region is US East (Virginia) I used this format for user data: cluster_name: <desired cluster="" name=""> password: <desired galaxy="" cloudman="" web="" ui="" password=""> access_key: <your aws="" access="" key=""> secret_key: <your aws="" secret="" key=""> However this screenshot shows a pipe delimited deal? Maybe I should try that? http://userwww.service.emory.edu/~eafgan/content/galaxy_cloud/AWSconso le-4.jpg Thanks, Greg

galaxy • 1.1k views

ADD COMMENT • link •

modified 7.0 years ago by Enis Afgan • 680 • written 7.0 years ago by mailing list • 840

7.0 years ago by

Enis Afgan • 680

Enis Afgan • 680 wrote:

Hi Greg, Sorry to hear you're having trouble. Can you please confirm that you followed the step for creating a security group on the wiki and opened all the specified ports? Enis

ADD COMMENT • link written 7.0 years ago by Enis Afgan • 680

Hi guys, It looks like my security group rules didn't get saved. I'm going to try again and report back. I actually asked this question on Biostar too. I thought my email didn't make it to the user group. It probably makes sense to consolidate in one place so I'm continuing the updates over there: http://biostar.stackexchange.com/questions/15554/galaxy-cloudman-cant- get-an-instance-started-the-connection-has-timed-out -Greg

ADD REPLY • link written 7.0 years ago by mailing list • 840

Ok I got past that part. I hadn't applied my rules :-(. Now when I go to the public DNS it prompts me for a username and password but it's not accepting the password I entered in the user data. Any idea what went wrong? Thanks again, Greg

ADD REPLY • link written 6.9 years ago by mailing list • 840

Hi Greg, Glad to hear it's working now though. The username is not necessary, just the password. Did you download the ssh private key when you created it in the AWS console? You can use it to connect to the instance terminal and make confirm the password to use within the browser. If you connect to the instance (via ssh -i <key file=""> ubuntu@<instance public="" dns="">) you can execute following command and check you password: cat /mnt/cm/userData.yaml The value under the 'password' field is your password. Note that the password cannot contain any spaces and is case sensitive. Enis

ADD REPLY • link written 6.9 years ago by Enis Afgan • 680

Similar posts • Search »