All,
After much debugging I finally found a workaround. I'd like to explain
what I did in the hopes that someone might see what the underlying
problem is.
I don't think I made this point explicit in my previous emails, but, I
am using fabric as a library. For simplicity, say I have two
Matt,
Try eliminating the use of DNS, ie.
ec2-174-129-96-241.compute-1.amazonaws.com, and instead connect
directly to the IP address, ie. 174.129.96.241, to see if that has
something to do with it.
Pat
On 06/14/2010 11:16 AM, Matt Calder wrote:
All,
After much debugging I finally found
Patrick,
I thought you were on to something there, but alas no. I get the same
using both DNS and IP. Both the errors without the fixes described,
and correct connections with the fixes.
Matt
On Mon, Jun 14, 2010 at 5:25 PM, Patrick J McNerthney
pmcnerth...@clearpointmetrics.com wrote:
Matt,
Hi Matt,
Paramiko doesn't have a connection cache that I'm aware of, but Fabric
itself does. However, from your description it sounds like you are
creating a new instance and then connecting to it, so I'm not sure why
a cache would present a problem.
If you're rebooting a remote system or doing
Jeff,
On Thu, Jun 10, 2010 at 6:54 PM, Jeff Forcier j...@bitprophet.org wrote:
Hi Matt,
Paramiko doesn't have a connection cache that I'm aware of, but Fabric
itself does. However, from your description it sounds like you are
creating a new instance and then connecting to it, so I'm not sure
Bruno,
No it is in a good group. I can log in using fabric if I restart it
and the instance is already running. I can see that fabric is inside
network.py trying to make the connection. I get one of two errors:
either timeout or low level socket error. In debugging, I added
retries to
Try using the --disable-known-hosts command line option to see if it has
something to do with a prior use of the same ip address.
On 06/10/2010 01:19 PM, Matt Calder wrote:
Jeff,
On Thu, Jun 10, 2010 at 6:54 PM, Jeff Forcierj...@bitprophet.org wrote:
Hi Matt,
Paramiko doesn't have a
