Plus, I thought that's a know risk with ssh file transfers, which is why its advisable to use rsync to transfer many/big files. Also, do you have ssh keys setup? That might help.<br><br><div class="gmail_quote">On Tue, Sep 13, 2011 at 10:18 AM, <span dir="ltr"><<a href="mailto:alexgabriel-Nmj6Sl6vboSovDFt+AQlJdBPR1lH4CV8@public.gmane.org">alexgabriel-Nmj6Sl6vboSovDFt+AQlJdBPR1lH4CV8@public.gmane.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">My first question would be whether you've tested the network connection through another means when the SSH transfer hangs. I.e. Pull up a web browser on the machine and access an Internet location.<br>
<br>
If the network connection itself is down, obviously the culprit is the network card.<br>
<br>
Have you tried with a smaller number of files? Say 7000 instead of 8000?<br>
<br>
I'm not aware of any volume limits related to SSH specifically, but you could try seeing if it always fails at a particular file, or after a specific number of files transferred.<br>
<br>
This sounds more like an issue with the hardware itself as opposed to the software, really.<br>
<br>
I'm sure one of the other, vastly more experienced people on here will be of more help, but I figured I'd send off what came to mind as ways to troubleshoot the issue.<br>
Alex Gabriel<br>
<br>
Sent from my BlackBerry device on the Rogers Wireless Network<br>
<br>
-----Original Message-----<br>
From: Peter King <<a href="mailto:peter.king.1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org">peter.king.1@gmail.com</a>><br>
Sender: <a href="mailto:owner-tlug-lxSQFCZeNF4@public.gmane.org">owner-tlug-lxSQFCZeNF4@public.gmane.org</a><br>
Date: Mon, 12 Sep 2011 19:58:59<br>
To: <<a href="mailto:tlug-lxSQFCZeNF4@public.gmane.org">tlug-lxSQFCZeNF4@public.gmane.org</a>><br>
Reply-To: tlug-CXWQD4r8zi01MepVCCEwxg@public.gmane.org: [TLUG]: ssh/ethernet hanging...<br>
<div><div></div><div class="h5"><br>
After persistant hangs and errors in one of my computers, I took out all the<br>
added memory and the gigabyte ethernet cards, reverting to some old DDR memory<br>
and the on-board via-rhine LAN. The memory has worked well. But I'm still having<br>
an occasional problem with ssh transfers -- specifically, when I transfer lots of<br>
files (no one of which is all that large), at some indeterminate point in the<br>
process, it just hangs.<br>
<br>
Before I blamed it on the gigabyte ethernet cards. But the on-board LAN is just<br>
a 10/100 connection. And I get it even when the computer is doing sending, not<br>
just when it's receiving. So where's the problem? Is it ssh or is it the ethernet<br>
card? It seems improbable that three distinct kernel drivers (two for the gigabyte<br>
cards and one for the on-board LAN) are each buggy in the same way. But google as<br>
I might, I don't find anything about ssh failing after, ohh, 8000 files or so. It<br>
has had problems with extremely large files, but that doesn't seem to be what's<br>
going on here.<br>
<br>
I set ssh verbosity to VERBOSE in the logfiles, and I get nothing. It just stops.<br>
<br>
Buggy hardware on the motherboard? Seems like it could be some kind of cache memory<br>
that fills up... I really have no clue at this point. All suggestions welcome.<br>
<br>
--<br>
Peter King <a href="mailto:peter.king-H217xnMUJC0sA/PxXw9srA@public.gmane.org">peter.king-H217xnMUJC0sA/PxXw9srA@public.gmane.org</a><br>
Department of Philosophy<br>
170 St. George Street #521<br>
The University of Toronto <a href="tel:%28416%29-978-4951" value="+14169784951">(416)-978-4951</a> ofc<br>
Toronto, ON M5R 2M8<br>
CANADA<br>
<br>
<a href="http://individual.utoronto.ca/pking/" target="_blank">http://individual.utoronto.ca/pking/</a><br>
<br>
=========================================================================<br>
GPG keyID 0x7587EC42 (2B14 A355 46BC 2A16 D0BC 36F5 1FE6 D32A 7587 EC42)<br>
gpg --keyserver <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a> --recv-keys 7587EC42<br>
<br>
</div></div></blockquote></div><br>