I think this may be related to some sshd limit in my git server. I'm deploy to more than 20 servers. I'm overcoming this by setting :deploy_via copy. Is this the recommended way to go?
This is related to one of the machines not having keyed access to the Git server (so it's hanging up, because the key exchange failed) - the :copy strategy is viable… but deploys a tarball from your workstation to all hosts, bypassing SCM (so I don't advise it) If you deploy to more than 20 servers, and only two are failing, your situation should be easy to cure! -Lee On 21 May 2011 16:40, Manuel Vázquez Acosta <[email protected]> wrote: > Hi, > > I'm (rather randomly) get failures like this: > > ** [server1.local.net :: err] ssh_exchange_identification: Connection > closed by remote host > ** [server2.local.net :: err] ssh_exchange_identification: Connection > closed by remote host > ** [server1.local.net :: err] fatal: The remote end hung up unexpectedly > ** [server2.local.net :: err] fatal: The remote end hung up unexpectedly > > I think this may be related to some sshd limit in my git server. I'm deploy > to more than 20 servers. I'm overcoming this by setting :deploy_via copy. Is > this the recommended way to go? > > Best regards, > Manuel. > > -- > * 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.com/group/capistrano?hl=en -- * 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.com/group/capistrano?hl=en
