uploading problem

Hi all,

i have this problem uploading with Filezilla.
For some reason it starts reuploading the files over and over again. It says "error while uploading" the next day i will find dozen of the same clips in my upladed bin..

Any idea's?

Thanks!!

I have the same problem with FTP Explorer. When a file is over 100 mBytes in many occasions it starts reloading the file. It's a big problem when you want to upload while you sleep. You can easily surpass your Internet provider bandwidth and get a big bill. I think the problem is in the P5 server side since it does not happen all the time.

I had this EXACT problem until I upgraded my router. The problem is that your FTP client is losing connection with the P5 server after 10 minutes or so (your router closes the control connection) and without the control connection, your FTP software doesn't know if the file completed upload or not. So it re-uploads the file.

Here is the problem (an excerpt from http://wiki.filezilla-project.org/Network_Configuration

Timeouts on large files

If you can transfer small files without any issues, but transfers of larger files end with a timeout, a broken router and/or firewall exists between the client and the server and is causing a problem.

As mentioned above, FTP uses two TCP connections: a control connection to submit commands and receive replies, and a data connection for actual file transfers. It is the nature of FTP that during a transfer the control connection stays completely idle.

The TCP specifications do not set a limit on the amount of time a connection can stay idle. Unless explicitly closed, a connection is assumed to remain alive indefinitely. However, many routers and firewalls automatically close idle connections after a certain period of time. Worse, they often don't notify the user, but just silently drop the connection. For FTP, this means that during a long transfer the control connection can get dropped because it is detected as idle, but neither client nor server are notified. So when all data has been transferred, the server assumes the control connection is alive and it sends the transfer confirmation reply. Likewise, the client thinks the control connection is alive and it waits for the reply from the server. But since the control connection got dropped without notification, the reply never arrives and eventually the connection will timeout.

In an attempt to solve this problem, the TCP specifications include a way to send keep-alive packets on otherwise idle TCP connections, to tell all involved parties that the connection is still alive and needed. However, the TCP specifications also make it very clear that these keep-alive packets should not be sent more often than once every two hours. Therefore, with added tolerance for network latency, connections can stay idle for up to 2 hours and 4 minutes.

However, many routers and firewalls drop connections that have been idle for less than 2 hours and 4 minutes. This violates the TCP specifications (RFC 5382 makes this especially clear). In other words, all routers and firewalls that are dropping idle connections too early cannot be used for long FTP transfers. Unfortunately manufacturers of consumer-grade router and firewall vendors do not care about specifications ... all they care about is getting your money (and only deliver barely working lowest quality junk).

To solve this problem, you need to uninstall affected firewalls and replace faulty routers with better-quality ones.


I had this problem with a cheapo router... and simply needed to upgrade to a better router.. I now have been using a Netopia 9000 commercial series router. (netopia no longer is netopia but motorola now)

I haven't uploaded here for a while, and I have the same issues as the other users. Yet I find your explanation a bit hard to stomach. I upload the exact files to other sites, same router (D-Link), yet no problem whatsoever. The problem has to be elsewhere.

I have the same problem, and I believe it has to do with the fact that the uploaded file was moved immediately elsewhere on the server side, so when my ftp program wants to check if the file has been uploaded successfully - it couldn't find the file so it tries to upload it again.

Waynstock, thats what i figured out. Afther sending a list ftp checks the server if the file is uploaded. If the file is removed on the server it starts uploading again.
Also Jacow's point seems to be holding up.
I'll guess it is a thing P5 should take of. also better for the bandwith i would think.

Look guys I've used FileZilla since 06 to upload files to P5 and never had a problem. If you are still having problems and the answers aren't forth coming why not use the CONTACT US at the bottom of this page. Also if you're keeping a log of your uploading you can send that along to the curator as well.

Problem is many here complain because videos are not processed fast enough. So when P5 moves files to their processing server quickly and an artist has stopped the ftp or there was a hiccup with something between the sender and P5 it can't find the original start and ya have to start again. Like Jason said above, I've also been using Filezilla for years and every time problem happens it when someone changed a setting in Filezilla. Leave it alone as you install it and if you have problems it's on your end and not P5.

I really like having P5 start to process quickly so I can get into the keywording. Maybe a 15-30 minute delay might be good to allow a restart.