Opened 14 years ago

Closed 11 years ago

#5696 closed Bug report (outdated)

Could not write to transfer socket: ECONNRESET - Connection reset by peer + transfer not logged as failed

Reported by: Grant Owned by:
Priority: normal Component: FileZilla Client
Keywords: ECONNRESET Failed Transfers Cc: grant@…
Component version: Operating system type: Windows
Operating system version: Win7Ultimate 64bit NT v6.1 build 7600

Description

Started FileZilla and was auto-upgraded to v3.3.5. Invoked about 300+ file transfer in passive mode from FZ on Win7 Ultimate 64bit.
Several transfers failed, some smaller files <100K and larger files about 16MB with the subject error message.

This left partially uploaded file in DESTINATION folder.
HOWEVER, the filesize was incorrect due to incomplete
file transfer.... AND....
the file transfer was NOT SHOWN as an ERROR in the FZ GUI...
I would have expected this.

I searched known bugs and understand ECONNRESET due to external network issues, however FZ should not show failed FTP as SUCCESSFUL.

I tried recreating in DEBUG 3 mode... however I was unable to reproduce the problem. I suspect the DEBUG setting slows down the condition that creates the problem... or no network issues (which seems strange to resolve in same timeframe since it was occurring for over 5-10 minutes). I did receive "Connection closed by server" with unexpected reply from server... suspect network issues... but again, NO FAILED TRANSFERS shown... ???

Attachments (1)

filezilla_ECONNRESET_20101117.7z (47.8 KB ) - added by Grant 14 years ago.
ECONNRESET in normal and debug/verbose3 mode

Download all attachments as: .zip

Change History (4)

by Grant, 14 years ago

ECONNRESET in normal and debug/verbose3 mode

comment:1 by Alexander Schuch, 11 years ago

Status: newmoreinfo

Do you still have that problem in a current version of FileZilla?

comment:2 by Alexander Schuch, 11 years ago

Summary: Could not write to transfer socket: ECONNRESET - Connection reset by peerCould not write to transfer socket: ECONNRESET - Connection reset by peer + transfer not logged as failed

comment:3 by Alexander Schuch, 11 years ago

Resolution: outdated
Status: moreinfoclosed

No reply for more than 28 days.

Note: See TracTickets for help on using tickets.