Craig Hockenberry recently emailed me with the solution to a problem that has bitten several people on this list. The problem is this: during a deploy, Capistrano would suddenly go off into la-la land and just hang, and on the server would be a defunct process. An SSH trace on the client side would show that Capistrano was just pinging away, waiting for a response from the server.
Craig discovered that changing his sshd on his server to start with the -4 switch (to use IPv4 instead of IPv6) fixed this. So, there's something wierd, apparently, with how IPv6 is being handled, either at the Ruby sockets level, or in Net::SSH somewhere (though Net::SSH isn't doing anything explicitly IPv4, that I'm aware of). Hopefully this helps someone else out there. (And if anyone wants a challenge: I'd love to know why IPv6 causes problems here...) - Jamis --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
