I mentioned this before, but I dropped this for a few months.  The
summary of the issue is as follows: I am running Ruby on a Windows XP
machine, and using Capistrano to connect to several servers in
production.  I do not use public key authentication to log in to the
production servers, but I do use public key authentication to connect
to some local servers, and have Pageant running to keep my key.
However, when I run a "cap" command to talk to more than one
production server, cap will sometimes fail, apparently at random,
while talking to the agent.  It seems like the first couple of times I
try it on a given day, it works, but then I'll get a string of
failures.  I'm not sure if there's really a pattern there.  Retrying
the command repeatedly works (eventually), as does stopping Pageant
and retrying the command.  The error messages I get look like this:

connection failed for: waylon.reverbnation.com
(Net::SSH::Authentication::AgentError: could not get identity count),
miles.reverbnation.com (Net::SSH::Authentication::AgentError: could
not get identity count), bootsy.reverbnation.com
(Net::SSH::Authentication::AgentError: could not get identity count)

connection failed for: woody.reverbnation.com
(Net::SSH::Authentication::AgentError: unknown response from agent:
12, "\000\000\000\301\f\ [...omitted...] ssh-rsa\000\000\000\
[...omitted...] [EMAIL PROTECTED] rsa-
key-20070620"), willie.reverbnation.com
(Net::SSH::Authentication::AgentError: bad authentication reply: 2)

The difference from last time is that I've upgraded my Ruby to 1.8.6-
p111 (the one-click installer 1.8.6-26), and I'm using Capistrano
2.5.2 and net-ssh 2.0.4.  I read that there were some fixes to try to
address this issue in one or more those, but they're not doing the
trick.  Anything else I could try?
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to