Indeed, this seems to have been the issue, or at least closely related - the dev guy in question built/installed REE 05/20/09, and the problem went away. Sounds like a regression in 1.8.7, indeed. (Everybody else is either using 1.8.6pl111-pl287, or REE of some version...) --elijah
On Wed, Jun 3, 2009 at 11:19 AM, Lee Hambley <[email protected]> wrote: > Elijah, > This may be part of it? .. have a read of this, and see if it fits > https://capistrano.lighthouseapp.com/projects/8716/tickets/79-capistrano-hangs-on-shell-command-for-many-computers-on-ruby-186-p368#ticket-79-24 > > - Lee > > 2009/6/3 Elijah Wright <[email protected]> > > Hi guys, >> I've got a user (inconveniently, in Poland, so major time zone difference) >> who's having trouble doing deploys to one of our multi-host rails >> environments. >> >> Basically, when he runs cap qa deploy, ssh connections connect then >> eventually go into CLOSE_WAIT state. Hang, boom. Not fun. >> >> I've managed to eliminate most of the possibles - multiple ssh keys, crap >> system ssh on his end, on the deployment end, etc - and think there might be >> a bug of some sort lurking here. >> >> He can ssh to the hosts he's trying to deploy to while he's trying to >> deploy (as they're failing / falling to the icky CLOSE_WAIT state..), and I >> can deploy to them perfectly adequately, so I think I've ruled out server >> issues and *mostly* ruled out key issues on his local host. >> >> How would folks-in-the-know like us to proceed with data collection, and >> what can you think of that might cause this kind of a failure? >> >> thanks, >> >> --elijah >> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
