Opened 17 years ago

Last modified 6 years ago

#146 closed Bug report

Too many retries

Reported by: anonymous Owned by:
Priority: normal Component: Other
Keywords: Cc: pbru, abacker, chainkeiya, emsco, sapience, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

When connecting, and uploading a lot of times the same
file (while it is changed all the time) itsays after some
time: Timeout detected. Upload Failed.
In the queue it says: Too many retries...

shouldn't I be able to upload the file as many times as I
want?

Change History (11)

comment:1 Changed 17 years ago by pbru

I encounter this problem when I upload large files, even if
for the first time (each time I had the problem the file was
more than 200MB large).

server NT4, client: FilleZilla 1.9.9

comment:2 Changed 17 years ago by anonymous

Logged In: NO

I just got it on a bunch of files. The one I just tried to reset
the status on a resend, keeps doing it. It is only 8k!!!!!!!!!!!!!!
This is not an inconvenience, it's a show stopper. I'm looking
for another ftp agent if I can't get this little file across the wire.

comment:3 Changed 17 years ago by abacker

I see this all the time when I am uploading 'too many' files.
At least it usually happens when I am doing 100+ files.

At some point fileZilla will start 'retrying' like crazy on quite a
few files, usually small ones. Everything keeps going ok, and
at the end I can 'reset' the status of the files and they will
upload fine.

Might this have something to do with the multiple connections
options? We are uing ftp over ssl, and having the multiple
connections option does not work with our server software.

comment:4 Changed 16 years ago by chainkeiya

Hi, I get this too with my webpage, and it occurs on many
servers. Its really annoying...

comment:5 Changed 16 years ago by anonymous

Logged In: NO

I have the same Problem!
Server run with SUNOS (2 CPU's)

220 ProFTPD 1.2.7 Server (Hosting Server 01, e.bootis ag)
[SUNPROD]

comment:6 Changed 16 years ago by anonymous

Logged In: NO

I have encountered to this problem too. I'm sending about 50
Java class-files to server about once in a five minutes. And
usually 2-4 of them always fails to this error discussed. The
files are 2-15Kb in size.

comment:7 Changed 16 years ago by anonymous

Logged In: NO

If you continue to get the retries, find the file in your ftp
server and delete it then try again. It seems to have a
problem with partial uploads. It's possibly a bug with
attempting to resume the upload, or attempting to decide to
replace the file by newer date since the date is the same. It
happens to me all the time...in fact, right now, i'm uploading
2,300+ files (all very small) and have quite a few timeouts.
It's a huge inconvenience. I know it's not a replace problem
since you can replace files just fine (mostly what I'm doing
now).

I noticed it being a problem with partial uploads when I
uploaded 132 image files ranging from 300k to 700k, and the
ones that failed were partially uploaded.

comment:8 Changed 16 years ago by emsco

I am having the same problem uploading to server ProFTPD 1.2.5.
This happens with all file sizes (500K-3MB) and it happens
with first upload and with resume.
The same files get tuploaded in no time with EFTP and Core FTP.
I stoped using FileZill for uploads

comment:9 Changed 16 years ago by emsco

I am having the same problem uploading to server ProFTPD 1.2.5.
This happens with all file sizes (500K-3MB) and it happens
with first upload and with resume.
The same files get tuploaded in no time with EFTP and Core FTP.
I stoped using FileZill for uploads

comment:10 Changed 15 years ago by sapience

any news on this being resolved? it's still happening on
2.2.7a. when a file is in the upload queue and in the process
of being uploaded, when i drag and drop another file into the
queue, it seems the first file goes into the crazy retry loop
even though the file seems to have completed uploading.

comment:11 Changed 14 years ago by Tim Kosse

This bug report has been closed due to inactivity and has possibly
already been solved.

You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).

Note: See TracTickets for help on using tickets.