We have tried changing the SSH client settings to give feedback to the server. But to no avail. In general the SSH sessions we have on our network do not timeout anyway.
I'm wondering how others have dealt with this issue - there must be a whole community of people who have real deploys which will have long running migrations. Mike On Oct 22, 2009, at 1:07 AM, Rafael G. wrote: > > Mike wrote: >> We have a long running migration. After the migration finishes on one >> box, when Cap starts the next task, the other ssh connections to the >> other servers timeout and the deploy fails. >> >> I have read a number of items on the net and from this group >> regarding >> this issue. However, there seems to be nothing that resolves the >> situation or at least nothing specific about what versions of cap >> and/ >> or ruby solve the issue. >> >> I'm sure that many others must be encountering this problem and I >> would like to know if there is a highly recommended way to deal with >> this issue, any help is appreciated. >> >> Mike >> > Perhaps change(increment) this values at your /etc/ssh/sshd_config in > your servers works: > > ClientAliveInterval 300 > ClientAliveCountMax 3 > > More info at http://unixhelp.ed.ac.uk/CGI/man-cgi?sshd_config+5 > > Regards > > -- > Rafa > > > > --~--~---------~--~----~------------~-------~--~----~ * 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 -~----------~----~----~----~------~----~------~--~---
