Is your instance in a security group that allow your IP and the port your trying to connect to?
If it timeout, it's probably blocked by Amazon firewalls. On Thu, Jun 10, 2010 at 15:07, Matt Calder <mvcal...@gmail.com> wrote: > Hi, > > I am having problems using fabric with EC2 instances. I am not > entirely sure fabric is even the source of the problem, but I am > hoping someone on this list can suggest a solution or a path to > investigate. Here is the problem. I start an EC2 instance using boto. > I wait for the instance to report its state as "running". I wait an > addition 60 seconds after that. Then I try to "run" things on the > instance through fabric. At that point I get: > > [ubu...@ec2-174-129-96-241.compute-1.amazonaws.com] run: ls > > Fatal error: Timed out trying to connect to > ec2-174-129-96-241.compute-1.amazonaws.com > > Aborting. > > Now, the interesting thing is this. During that additional 60 second > wait I can log into the instance from a separate terminal, moreover, > when I do that separate login, the fabric login succeeds. > > Obviously, there is not a lot to go on here, but I am not entirely > sure what additional information would be helpful. If anyone has a > suggestion of what I might try to do, I would greatly appreciate it. > Thanks, > > Matt > > _______________________________________________ > Fab-user mailing list > Fab-user@nongnu.org > http://lists.nongnu.org/mailman/listinfo/fab-user >
_______________________________________________ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
