My ssh config is this, followed by a bunch of hostname aliases:
Host *
ServerAliveInterval 180
Host solr* jenkins folio*
IdentityFile ~/.ssh/aws_id_rsa
The ServerAliveInterval is something I added when I was trying to debug the
issue last summer. It didn't work, and I never took it out.
The servers that I'm communicating with are a combination of Amazon Web
Services hosted and on-campus server farm machines. Both sets are virtual
machines, if that makes any difference. I did ask last summer, and all I got
from our operations people was an assurance that they definitely didn't set up
the servers to limit ssh sessions to 20 minutes. If there are specific
misconfigurations that someone can suggest I check or ask them about, I'd be
happy to pursue that further. Out-of-date server software is worth looking into
if there are known incompatibilities.
-----Original Message-----
From: matthew patton <patto...@yahoo.com>
Sent: Friday, June 5, 2020 11:12 AM
To: Frances B. Webb <frances.w...@cornell.edu>
Subject: Re: trouble maintaining an open ssh connection past 20 minutes
post your ssh config. specifically if you're doing heartbeat packets and loss
threshold. And also have you talked to your firewall admins?
eg.
ServerAliveInterval 90
ServerAliveCountMax 3
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
