10 minutes is definitely way, way longer than it should take to become
responsive. It's a little hard to guess what might have gone wrong with your
setup -- my first guess for this type of issue would be the security group
configuration, but you did say you were able to SSH in.
One easy thing to test, however, would be to launch the instance using Galaxy's
Cloud Launch at usegalaxy.org/cloudlaunch, which configures security groups and
keys for you.
On Oct 26, 2012, at 11:08 AM, Scooter Willis <hwil...@scripps.edu> wrote:
> Following the instructions at
> Setup an instance using the latest AMI and did configure it to use a password
> AMI: galaxy-cloudman-2012-05-10 (ami-78a00411)
> Waited 10+ minutes after instance is running and going to
> Gets a Unable to Connect message.
> I am able to ssh into the instance but don't have any clue where to look for
> error messages or what is expected to be running.
> From the ssh client if I do a wget localhost I get a connection refused
> ubuntu@ip-10-80-199-13:~$ wget localhost
> --2012-10-26 18:05:07-- http://localhost/
> Resolving localhost (localhost)... 127.0.0.1
> Connecting to localhost (localhost)|127.0.0.1|:80... failed: Connection
> I have been using Amazon EC2 for years so familiar with everything. I know
> just enough linux to cause more problems then I can solve!!!
> Any suggestions?
> 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:
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: