increase timeout value of ssh timeout

1,160 views
Skip to first unread message

kumar

unread,
Jan 3, 2013, 10:29:24 PM1/3/13
to scmma...@googlegroups.com
Hi

I have install the SSH plugin for SCM Manager

I am doing an initial push of a 9GB to the remote repository using ssh. 
I get the following error

Received disconnect from 10.1.1.127: 2: User idle has timed out after 600000ms.

Is there a way to increase the time out value

Thanks

Sebastian Sdorra

unread,
Jan 6, 2013, 8:58:00 AM1/6/13
to scmma...@googlegroups.com
Hi,
Sorry until yesterday i did not even know that a ssh plugin for SCM Manager exists. I think you should ask the author of the plugin. I does not know if the author read this mailing list, perhaps you have to write him directly. But if you find a solution, please post the answer to this thread.

P.s.: The ssh plugin clears all caches automatically.

Sebastian


2013/1/4 kumar <t12...@gmail.com>

kumar

unread,
Jan 22, 2013, 8:03:02 AM1/22/13
to scmma...@googlegroups.com
Hi
This is the reply i got from the author


--------------------------------------------------------------------------------------REPLY----------------------------------------------------------------------------
just checked the EGit source code (SCM and thus the SSH plugin are using EGit internally). The "receive-pack" command does not have a timeout parameter, unlike the "upload-pack" command.

I think that the problem might be in the SSH session handling, however I could not find a default timeout of 600 seconds in the session configuration classes.

If you are using the command-line Git client, you can try setting two parameters for your SSH session that might help: In your ~/.ssh/config file you can add:

ServerAliveCountMax 10
ServerAliveInterval 30

This should stop idle SSH session from timing out.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have tried this but i get the same error. Not sure where this 600000ms is set. this time out is happening when compression time is taking too much time due to huge repository.

thanks
Reply all
Reply to author
Forward
0 new messages