Opened 10 years ago

Closed 7 years ago

#9901 closed Bug report (wontfix)

FileZilla gives erroneous failed message

Reported by: Ken Owned by:
Priority: normal Component: FileZilla Client
Keywords: erroneous error uploading large file Cc:
Component version: Operating system type: Windows
Operating system version: Win7 64 bit

Description (last modified by Tim Kosse)

I have a very large file -- 320+MB -- and when I upload it to our FTP Side, after about 30-45 minutes, it ALWAYS ends on the Failed Transfers list with the reason "could not start transfer."

This error is (a) obviously erroneous as it just uploaded the file. I can verify this by first deleting the version on the site and then uploading a new version. When it's done uploading the new version is there; and (b) it didn't actually fail because if I download the file (which is a signed exe) it passes all integrity checks and its signature is still intact which it wouldn't be if it had failed.

If you'd like to grab the file to play with it's at:

Attachments (1)

filezilla.log (15.2 KB ) - added by Ken 10 years ago.
Log file of upload attempt

Download all attachments as: .zip

Change History (7)

comment:2 by Tim Kosse, 10 years ago

Status: newmoreinfo

Please post a complete log of a transfer.

by Ken, 10 years ago

Attachment: filezilla.log added

Log file of upload attempt

comment:3 by Ken, 10 years ago

Status: moreinfonew

I've posted the log file as requested.

comment:4 by Alexander Schuch, 9 years ago

Status: newmoreinfo

Just a short summary: The client uploads the file first. The upload does not finish, or at least the connection is not properly terminated.

2014-11-01 19:41:01 4644 3 Command: STOR FrameForgePreviz35_setupNU.exe
2014-11-01 19:41:01 4644 3 Response: 150 Data connection accepted from; transfer starting.
2014-11-01 20:24:29 4644 1 Response: 421 Disconnecting you since you were inactive for 2700 seconds.
2014-11-01 20:24:29 4644 1 Error: Connection closed by server
2014-11-01 20:38:36 4644 3 Error: Connection timed out
2014-11-01 20:38:36 4644 3 Error: File transfer failed after transferring 362,975,296 bytes in 3455 seconds

FileZilla believes this is a bad connection and tries to resume the upload. It backs off a bit and tries to continue uploading. For some reason, it backs off by 35 MiB.

2014-11-01 20:38:43 4644 3 Command: REST 326554612
2014-11-01 20:38:44 4644 3 Response: 350 Will attempt to restart at position 326554612.
2014-11-01 20:38:44 4644 3 Command: STOR FrameForgePreviz35_setupNU.exe
2014-11-01 20:38:44 4644 3 Response: 553 Sorry, you can only append to (RESTart at the end of) this file.
2014-11-01 20:38:44 4644 3 Error: Critical file transfer error

The server only supports appending, but it does not support backing off.

What is the original file size in bytes?

comment:5 by Ken, 9 years ago

Status: moreinfonew

I do not know the byte size of the file for which this log was generated BUT I know that it was in fact correctly uploaded because it is a signed, self-extracting ZIP file (SFX) and when I download it after it reports the error, it both passes all zip integrity checks but the digital signature also survives the round trip.

Unfortunately the file has changed since this last log so I can't just look.

Can you not duplicate this issue on your servers? I could give you an FTP account on our servers if that would help, or alternatively, I could upload a different file which I won't change and record its log, whichever will give you more information.

comment:6 by Tim Kosse, 7 years ago

Description: modified (diff)
Resolution: wontfix
Status: newclosed

This issue needs to be fixed server-side by implementing proper REST support.

Note: See TracTickets for help on using tickets.