mainSavannah Administration - Support: sr #103027, premature ssh timeouts on slow...

 
 

sr #103027: premature ssh timeouts on slow connections

Submitter:  Karl Berry <karl>
Submitted:  Fri 23 Apr 2004 09:59:21 PM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  2 - Minor Status:  Done
Privacy:  Public Assigned to:  Beuc
Operating System:  None Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 25 Apr 2004 01:42:53 PM UTC, comment #4: 

thanks very much! it seems to have helped, at least i was able to do a couple of cvs updates this morning without getting timed out.


Karl Berry <karl>
Site Administrator
Sun 25 Apr 2004 08:41:51 AM UTC, comment #3: 

I set it to 20.
I am not sure that allowing a non-responsive client for 10 minutes will solve the problem, but it does not cost anything to try.
I will also see with the system administrators whether there is any cons in this change.

Sylvain Beucler <Beuc>
Sat 24 Apr 2004 11:07:59 PM UTC, comment #2: 

Hi Sylvain,

The 15 was just a random example, ignore that.

Would you be willing to try increasing ClientAliveCountMax to something much larger, say, 10 or 20?  I don't think this would do any harm, as it will only affect clients that aren't successfully connecting anyway.  I don't know if it will help my case, but it's the only thing I can think of.

As for the "inactivity", it would take substantial debugging to figure out exactly why it is happening.  Since the timeouts usually occur only in hierarchies with relative large numbers of files, I surmise that the client has to send lots of data in quick succession, and the satellite connection simply won't pass it that quickly. With latencies around 800-900ms, anything that requires a round-trip handshake is not going to be completed quickly.

Thanks.

Karl Berry <karl>
Site Administrator
Sat 24 Apr 2004 08:04:54 PM UTC, comment #1: 

Hello,

The current settings are ClientAliveInterval 30 and ClientAliveCountMax to default (3), hence the 90 seconds I guess :)

I do not understand your suggestion to set it to 15, as an unreachable client would be killed in 45 seconds.
I am also puzzled to see that your connection can be 'inactive' for more than one minute.
Is there something I missed?

Thanks.

Sylvain Beucler <Beuc>
Fri 23 Apr 2004 09:59:21 PM UTC, original submission:  

I unfortunately had to move to a satellite-based Internet connection, since nothing else was available in my area.  It has very slow upload speeds with a large latency. 

Since moving, I've found that cvs updates in larger hierarchies, namely /webcvs/texinfo, usually die after approximately 90 seconds with the message:
Received disconnect from 199.232.41.3: 2: Timeout, your session not responding.

It will occasionally run to completion, occasionally time out sooner, etc.  I've tried everything I can think of on the client side to affect this: ServerAliveInterval, ServerAliveCountMax, TCPKeepAlive, and more, but nothing has made any difference.

On the server side, setting ClientAliveInterval 15 (or some such) in sshd_config seems like the most likely thing to help, although I obviously don't know for sure.

Are you willing and able to try to help with this?  I don't know if anyone else is on a satellite connection; I doubt anyone on real broadband or even dialup would have the problem.

Thanks.


Karl Berry <karl>
Site Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2004-04-29 Beuc StatusNone Done
    Open/ClosedOpen Closed
2004-04-24 Beuc Assigned toNone Beuc

Back to the top

Powered by Savane 3.13-02a9.
Corresponding source code