| 1 |
On Tuesday 21 October 2008, Paul Hartman wrote: |
| 2 |
> On Tue, Oct 21, 2008 at 12:15 AM, Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
> > Hi All, |
| 4 |
> > |
| 5 |
> > Any idea why this happens: |
| 6 |
> > ======================================== |
| 7 |
> > 150 Ok to send data. |
| 8 |
> > 100% |***********************************| 224 MiB 46.74 KiB/s |
| 9 |
> > 00:00 ETA |
| 10 |
> > 226 File receive OK. |
| 11 |
> > 235279855 bytes sent in 1:21:59 (46.70 KiB/s) |
| 12 |
> > local: xab remote: xab |
| 13 |
> > 227 Entering Passive Mode (205,178,145,65,166,71) |
| 14 |
> > 150 Ok to send data. |
| 15 |
> > 34% |*********** | 115 MiB 46.80 KiB/s |
| 16 |
> > 1:19:27 ETAtnftp: Writing to network: Connection reset by peer |
| 17 |
> > 0% | | -1 0.00 KiB/s |
| 18 |
> > --:-- ETA |
| 19 |
> > 500 OOPS: child died |
| 20 |
> > ======================================== |
| 21 |
> > |
| 22 |
> > It is rare that I am able to complete more than a single file transfer |
| 23 |
> > before the "connection is reset by peer". As these are relatively large |
| 24 |
> > files and the upload is unattended this is rather annoying. |
| 25 |
> > -- |
| 26 |
> > Regards, |
| 27 |
> > Mick |
| 28 |
> |
| 29 |
> That used to happen to me when I was using a piece-of-junk D-Link |
| 30 |
> router. It was one of those $29.99 consumer-grade deals. It would |
| 31 |
> reboot itself constantly when it was under any kind of load. I |
| 32 |
> replaced it with a $50 router with DD-WRT and things have been fine |
| 33 |
> ever since. Might not have anything to do with your problem, but I |
| 34 |
> figured I'd mention it. Check your router logs to see if it's having |
| 35 |
> any problems. |
| 36 |
|
| 37 |
Thanks Paul, |
| 38 |
|
| 39 |
On the client side I am running a $500 professional grade router and I assume |
| 40 |
that the server ISP is also running something upmarket in their data center. |
| 41 |
|
| 42 |
On this topic the client-server arrangement straddles the Atlantic ocean, so |
| 43 |
who knows how many routers and switches it jumps across. That said the |
| 44 |
failure pattern is consistent: first file always transfers cleanly, then |
| 45 |
second transfer fails after a while. Could it be some configured |
| 46 |
disk/account quote, dropping transfers above a certain size on the (Unix) |
| 47 |
server? |
| 48 |
-- |
| 49 |
Regards, |
| 50 |
Mick |
Archives