I just wanted to follow up on this thread. Changed the ClientAliveCountMax and ClientAliveInterval did resolve my issue.
Thanks, Brian On Sep 14, 7:17 pm, "Rafael G." <[email protected]> wrote: > I was wrong about my notes, it's about long tasks that block the other > connections. > > Anyway, have you tried to play with ClientAliveCountMax and > ClientAliveInterval parameters in sshd_config(in the server), I think > if you try with very high values it could work. > > Regards > > On Sep 12, 10:03 pm, Brian Carpio <[email protected]> wrote: > > > > > > > > > So currently I deploy an application using capinstrano via an ssh > > gateway or bastion host. If my cap jobs take over two hours I can see > > the ssh session close on the bastion host in /var/log/secure but on > > the deployment server I actually see the cap job still running, it > > seems to run indefinitely until I kill it. > > > I know two hours seems like a long time tokeepan ssh session open > > but I'm just wondering if anyone has seen similar behavior and if > > anyone has some suggestions on how to troubleshoot this problem or > > what to look for. These long running jobs seem to fail at different > > times, once the job failed at 2h 15m the next time it failed at 2h > > 50m. > > > I can't find anything in any of the config files which represents this > > timeout value. > > > Thanks for any help. > > Brian -- * 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
