Opened 13 years ago
Closed 13 years ago
Last modified 13 years ago
#5050 closed Other (invalid)
Filezilla abandones files with zero length after trying to upload
|Reported by:||Sergio Abreu||Owned by:|
|Keywords:||hang up length zero files||Cc:|
|Component version:||Operating system type:||Windows|
|Operating system version:|
I decided uninstall filezilla.
It seems to be irresponsible software.
While cute ftp insists untill the file is totally uploaded, Filezilla when encounters some difficulty in the connection, simply abandones files with ZERO length in the server side because it tryied to create new file but had problems in the connection.
I can not continue using a software that leaves zero length files in the server side when something happens to the connection. I use Cute ftp because it is more eficient.
Change History (5)
comment:1 by , 13 years ago
|Status:||new → moreinfo|
comment:2 by , 13 years ago
|Priority:||critical → low|
comment:3 by , 13 years ago
|Status:||moreinfo → new|
Unfortunatelly, I have already uninstalled and I believe these logs were in the app directory... If the logs are in other place, please tell me.
When the connection hangs during the upload process, some profissional FTP applications DO NOT give up, probably they have an internal loop that time after time checks if the connection became normal, and tries to finish de upload.
The second grave point is that EVEN having left one zero length file at the server side, Filezilla continue doing the same more times.
I got disturbed when I saw that in the server side I had about 3 or 4 ZERO length files that Filezilla could not complete download.
So I bring the meditation: Why not stop doing the queue if the first try had a critical error, that made Filezilla let the incomplete upload file with 0 byte ?
comment:4 by , 13 years ago
|Status:||new → closed|
Closed since ticket is lacking information.
comment:5 by , 13 years ago
|Type:||Bug report → Other|
As I said previously, I am new to Filezilla.
But I think that now, I discovered and solved the problem.
It was, in fact, very simple - no need of logs, etc.
By default, Filezilla comes configured with only 20 seconds expiration time for the connection. My server is very slow, so when the "20 seconds" time expired, the files were obviously left uncomplete.
I increased the time to 120 seconds and now it is working.
The funny thing is that nobody (experienced users there) at least mentioned this possible configuration problem ...
Now it is clear, and I hope this little tips can help new unexperient Filezilla users as me.
PS 1: The software is great, just need to be well configured to work.
PS 2: The default amount of time for connection expiration time is too low (20 s).
PS 3: I suggest changing this default time to 60s instead of 20s to avoid other users frustration.
Please attach some complete and unmodified logs of the failing transfers.