FTP upload occasionally stops and starts over again from 0%

[msiivola]

What was different in the final file? Maybe the server doesn't correctly support the REST command (restart download) and started from the beginning?

I am unable to repeat it, because I cannot reach those computers anymore (new computers now, with different version of Serv-U), but anyway, the download continued tens of megabytes over the correct length of the files to be downloaded 'til I stopped them, but, alas, I did not look inside the files to see what was different. The downloads was not stopped/restarted in these experiments.

The errors were definite, anyway, repeatedly seen, and CuteFTP worked then each time.

Of course if I can catch the error again, I'll report it more accurately.

[MatKus]

Thread is quite old, but since i'm using latest TC and i have exactly same problem, i decided to write here.
I know it says "witch will not be changed" but i'll spam a little anyway

I'm trying right now to upload 450 KB file. Nothing big, you say, but when your upload is below 1kb/s and it stops every 30-60 KB, it is problem

So, everytime it stops, i'm simply trying to resume it by "finish file" (or how it is in english, i don't know, i'm, using polish translation of TC). It works, but but sometimes in middle of file TC simply stops upload, i see PASV, and if server will respond (connection is not realy lost), upload starts from begin, so uploading "so huge file" is close to impossible.

I belive problem is with slow/unstable connections. TC thinks, that connection is lost, but checks if it's true. server responds to PASV, so TC starts to upload file from beginning.

[ghisler(Author)]

Could you post a connection log here, please? It's only in "will not be changed" because I cannot reproduce and therefore not fix it...

[MatKus]

sure, here we go. I've tried few times to reproduce it, so, here's log of all tries. I'll cut few first lines, no need to publicate server and login

SYST
215 UNIX Type: L8
FEAT
500 'FEAT': command not understood.
Connect ok!
PWD
257 "/" is current directory.
Pobierz katalog
TYPE A
200 Type set to A.
PASV
227 Entering Passive Mode (<server IP censored >)
LIST
150 Opening ASCII mode data connection for '/bin/ls'.
Ściąganie: 4 334 bajtów
Czekam na serwer...
226 Transfer complete.
CWD temp
250 CWD command successful.
PWD
257 "/temp" is current directory.
Pobierz katalog
PASV
227 Entering Passive Mode (<server IP censored >)
LIST
150 Opening ASCII mode data connection for '/bin/ls'.
Ściąganie
Czekam na serwer...
226 Transfer complete.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (<server IP censored >)
STOR palurin.zip
150 Opening BINARY mode data connection for 'palurin.zip'. <--File have like 420KB
Wysyłanie: 17 407 bajtów, 111 bajtów/s, 45 min
PASV <--- this appeared after about minute or two of inavtivity
Wciśnięto anuluj! <--- this means "pressed cancel" I did this after about another two minutes of inavtivity. Provably connection is lost, just TC does not know about it.
PASV
Wciśnięto anuluj!
Pobierz katalog
TYPE A
Wciśnięto anuluj!
PASV
Wciśnięto anuluj!

OK, so, here goes try 2nd. (bingo! )

<CUT>
CWD temp
250 CWD command successful.
PWD
257 "/temp" is current directory.
Pobierz katalog
PASV
227 Entering Passive Mode (<server IP censored >)
LIST
150 Opening ASCII mode data connection for '/bin/ls'.
Ściąganie
Czekam na serwer...
226 Transfer complete.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (<server IP censored >)
STOR palurin.zip
150 Opening BINARY mode data connection for 'palurin.zip'.
Wysyłanie: 94 207 bajtów, 246 bajtów/s, 8 min
PASV <-- here for unknown reason goes PASV, before file was completely uploaded
227 Entering Passive Mode (<server IP censored >)
STOR palurin.zip
150 Opening BINARY mode data connection for 'palurin.zip'.
Wysyłanie: 8 704 bajtów
Wciśnięto anuluj!<-- I got what i needed in log, so i've canceled.
Wysyłanie: 8 703 bajtów
Wciśnięto anuluj!
Pobierz katalog
TYPE A
Wciśnięto anuluj!
PASV
Wciśnięto anuluj!

I have terrible connection. Uplad is 256KB/s, but it's shared for like 20 people, and most of them are running torrents or emule 24/7, so it works like it works, and that may be main reason.

I don't know. Maybe don't try to re-upload same file, if it TC is not 100% sure it was completed (program knows how much it was uploaded and how big was file)? Or ask user about it?

[ghisler(Author)]

Thanks for the log, that's indeed very unusual - I will check in my code how it could get first to reporting a complete transfer without having received a "transfer complete" message, and then again to PASV...