Hi,

I just tried to upload some files via FTP to my server and ran into a problem. When transferring the file, it gets 99.7% complete, then just hangs there. If I let it time out, the error is "451 name_of_file.html: Append/Restart not permitted, try again". I'm using the FTP Voyager program, version 10 on my PC.

I think I'm running ProFTP on my server. Its a Redhat 7.3 based system with Plesk 6.0x on it. I've never seen this before. I checked the hard drive stats to make sure I wasn't running low on space. My load using the 'top' command is not showing anything strange either, although it was a bit high, its settled down again, but still no FTP success.

What should I be checking here or trying?

Your server or client may not be capable of resuming. Try removing the file from the server and uploading again. See if that helps. :)

I should have mentioned, I tried that already, and it didn't work. I tried it both with an existing file, and a new file.

Also, I know it supports resuming because it worked before. I've been using it on this server for almost 2 years, first under Plesk 5 and for about 3 months with Plesk 6. I'm sure that doesn't affect the FTP server, but thought I'd mention it.

In any case, I just noticed this problem tonight, I haven't had it before.

The FTP server may be logging errors somewhere -- check that log. If it's not, enable error logging, try to upload your file, then check the log when (and if) it fails. It may help.

Another option is to start the FTP server without making it fork to the background and turning on various levels of verbosity. You can then see exactly what the FTP server is doing while you try to upload. I know ProFTPd can do this, I'm not sure if others can.

To see if you have ProFTPd running, just check your process list (ps auxww |grep ftp). If it is proftpd, run a man proftpd to find out the "do not fork" switch and the verbose switches. Kill your proftpd process, run it with those switches, and see what it does. When you solve your problem, restart proftpd as normal (probably listed in /etc/rc.d/init.d for linux and /usr/local/etc/rc.d for freebsd).

Was there an xfer.log on Plesk 6 like there is on Plesk 7? If so, check there for more info.

Yes, there is an xferlog. Here's all that is in there, I've replaced IP info and domain info with bogus details. Basically, I don't know what I'm looking for. If this tells anyone anything, I'd appreciate your input.

Sat Apr 17 22:40:29 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/fs/selfadhesive.html a _ i r l$
Sat Apr 17 22:41:26 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/fs/selfadhesive.html a _ i r l$
Sat Apr 17 22:42:57 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/fs/selfadhesive.html a _ i r l$
Sat Apr 17 22:44:20 2004 3600 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/dish.html a _ i r clientsite$
Sat Apr 17 22:44:34 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/dish.html a _ i r clientsite$
Sat Apr 17 22:47:14 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/dish.html a _ i r clientsite$
Sat Apr 17 22:52:54 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/dish.html a _ i r clientsite$
Sat Apr 17 22:53:14 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/dish.html a _ i r clientsite$
Sat Apr 17 22:54:57 2004 3599 207-170-255-999.asisna.com 0 /home/httpd/vhosts/clientsite.com/httpdocs/dish.html a _ i r clientsite$
Sat Apr 17 22:55:59 2004 3599 207-170-255-999.asisna.com 0 /home/david/selfadhesive.html a _ i r david ftp 1 * i

Well, I tried rebooting the server, but that didn't help.

I can confirm now that this is a local issue on my network somewhere. Just not sure what, so I'm going to start be rebooting everything.

Why is it the solution is always the LAST THING you try????

Well, here it is... Since I knew the problem was local, the last thing I tried was checking for any updates to my FTP program. Sure enough, there was one, and wouldn't you know it, that solved the problem.