I have recently purchased a linux based PDA called the Yopy (http://www.yopypda.co.uk/) and jolly clever it is too. However I have had some bother transferring files with Filezilla.
The ftp server in the Yopy does not support resumption. If a file transfer fails I cannot try it again, as Filezilla uses REST instead of STOR and all I get is a complaint in the log window (cool- it's in red) on Filezilla.
I've tried using the 'reset status' command in the queue window, or deleting the queue all over again, and it seems as though Filezilla is determined to use the REST command come what may.
I'd like to suggest a tick box in the site manager, so I can tell Filezilla that the site does not support resumption of transfers, so this behaviour does not occur.
enhancement request: Suppressing the REST command?
Moderator: Project members
OK, here is one. Note, the command is APPE, not REST as I seem to recall from last time....botg wrote:Please post some full logs.
The first failure was me cancelling the transfer because the Yopy PDA froze, the second was me unplugging it to force a failure. In both these cases I had to delete the partial file on the Yopy before a good transfer could be done. Even though the default action is 'overwrite'.Status: Connecting to yopy ...
Status: Connected with yopy. Waiting for welcome message...
Response: 220 BCB1COOL Server (Proftpd FTP Server) [yopy]
Command: USER root
Response: 331 Password required for root.
Command: PASS
Response: 230 User root logged in.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/home/root" is current directory.
Command: PORT 192,168,1,254,4,48
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD mmc
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/mnt/mmc" is current directory.
Command: PORT 192,168,1,254,4,49
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD music
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/mnt/mmc/music" is current directory.
Command: PORT 192,168,1,254,4,50
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD Handel
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/mnt/mmc/music/Handel" is current directory.
Command: PORT 192,168,1,254,4,51
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD fire
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/mnt/mmc/music/Handel/fire" is current directory.
Command: PORT 192,168,1,254,4,52
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\01-Overture.mp3
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,53
Response: 200 PORT command successful.
Command: STOR 01-Overture.mp3
Response: 150 Opening BINARY mode data connection for 01-Overture.mp3.
Command: ABOR
Error: Upload aborted
Error: Interrupted by user!
Status: Retrieving directory listing...
Command: PORT 192,168,1,254,4,58
Response: 460 Requested action not taken. Other command in progress.
Error: Could not retrieve directory listing
Error: Disconnected from server
Status: Waiting to retry... (5 retries left)
Status: Connecting to yopy ...
Error: Unable to connect!
Status: Waiting to retry... (4 retries left)
Status: Connecting to yopy ...
Error: Unable to connect!
Status: Waiting to retry... (3 retries left)
Status: Connecting to yopy ...
Status: Connected with yopy. Waiting for welcome message...
Response: 220 BCB1COOL Server (Proftpd FTP Server) [yopy]
Command: USER root
Response: 331 Password required for root.
Command: PASS
Response: 230 User root logged in.
Status: Connected
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\01-Overture.mp3
Command: CWD /mnt/mmc/music/Handel/fire/
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/mnt/mmc/music/Handel/fire" is current directory.
Command: PORT 192,168,1,254,4,62
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,63
Response: 200 PORT command successful.
Command: APPE 01-Overture.mp3
Response: 451 01-Overture.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\01-Overture.mp3
Command: PORT 192,168,1,254,4,64
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,65
Response: 200 PORT command successful.
Command: APPE 01-Overture.mp3
Response: 451 01-Overture.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\01-Overture.mp3
Command: PORT 192,168,1,254,4,66
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,67
Response: 200 PORT command successful.
Command: APPE 01-Overture.mp3
Response: 451 01-Overture.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\01-Overture.mp3
Command: PORT 192,168,1,254,4,68
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,69
Response: 200 PORT command successful.
Command: APPE 01-Overture.mp3
Response: 451 01-Overture.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\01-Overture.mp3
Command: PORT 192,168,1,254,4,70
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,71
Response: 200 PORT command successful.
Command: APPE 01-Overture.mp3
Response: 451 01-Overture.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Retrieving directory listing...
Command: PORT 192,168,1,254,4,72
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Command: DELE /mnt/mmc/music/Handel/fire/01-Overture.mp3
Response: 250 DELE command successful.
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\01-Overture.mp3
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,73
Response: 200 PORT command successful.
Command: STOR 01-Overture.mp3
Response: 150 Opening BINARY mode data connection for 01-Overture.mp3.
Response: 226 Transfer complete.
Status: Upload successful
Status: Retrieving directory listing...
Command: PORT 192,168,1,254,4,122
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Command: TYPE A
Response: 200 Type set to A.
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\05-Menuet.mp3
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,123
Response: 200 PORT command successful.
Command: STOR 05-Menuet.mp3
Error: Disconnected from server
Error: Upload failed
Status: Connecting to yopy ...
Error: Timeout detected!
Status: Connecting to yopy ...
Status: Connected with yopy. Waiting for welcome message...
Response: 220 BCB1COOL Server (Proftpd FTP Server) [yopy]
Command: USER root
Response: 331 Password required for root.
Command: PASS
Response: 230 User root logged in.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/home/root" is current directory.
Status: Directory listing successful
Error: Unable to connect!
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\05-Menuet.mp3
Command: CWD /mnt/mmc/music/Handel/fire/
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/mnt/mmc/music/Handel/fire" is current directory.
Command: PORT 192,168,1,254,4,127
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,128
Response: 200 PORT command successful.
Command: APPE 05-Menuet.mp3
Response: 451 05-Menuet.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\05-Menuet.mp3
Command: PORT 192,168,1,254,4,129
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,130
Response: 200 PORT command successful.
Command: APPE 05-Menuet.mp3
Response: 451 05-Menuet.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\05-Menuet.mp3
Command: PORT 192,168,1,254,4,131
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,132
Response: 200 PORT command successful.
Command: APPE 05-Menuet.mp3
Response: 451 05-Menuet.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Starting upload of C:\Documents and Settings\Bob\My Documents\My Music\card image\Handel\fire\05-Menuet.mp3
Command: PORT 192,168,1,254,4,133
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,1,254,4,134
Response: 200 PORT command successful.
Command: APPE 05-Menuet.mp3
Response: 451 05-Menuet.mp3: Append/Restart not permitted, try again.
Error: Upload failed
Status: Retrieving directory listing...
Command: PORT 192,168,1,254,4,135
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226 Transfer complete.
Status: Directory listing successful
Command: PWD
Response: 257 "/mnt/mmc/music/Handel/fire" is current directory.
Ich have a similar problem with one ftp server.
Sometimes when i upload a file it fails:
Status: Starting upload of F:\....\stylesheet.css
Command: PORT 192,168,100,59,13,118
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226-Transfer complete.
Response: 226 Quotas off
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,100,59,13,119
Response: 200 PORT command successful.
Command: APPE stylesheet.css
Response: 451 stylesheet.css: Append/Restart not permitted, try again.
Error: Upload failed
When i try again or delete the file first it works:
Status: Starting upload of F:\...\stylesheet.css
Command: CWD /
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/" is current directory.
Command: PORT 192,168,100,59,13,132
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226-Transfer complete.
Response: 226 Quotas off
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,100,59,13,133
Response: 200 PORT command successful.
Command: STOR stylesheet.css
Response: 150 Opening BINARY mode data connection for stylesheet.css.
Response: 226 Transfer complete.
Status: Upload successful
Default Setting is overwritte
Sometimes when i upload a file it fails:
Status: Starting upload of F:\....\stylesheet.css
Command: PORT 192,168,100,59,13,118
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226-Transfer complete.
Response: 226 Quotas off
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,100,59,13,119
Response: 200 PORT command successful.
Command: APPE stylesheet.css
Response: 451 stylesheet.css: Append/Restart not permitted, try again.
Error: Upload failed
When i try again or delete the file first it works:
Status: Starting upload of F:\...\stylesheet.css
Command: CWD /
Response: 250 CWD command successful.
Command: PWD
Response: 257 "/" is current directory.
Command: PORT 192,168,100,59,13,132
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for file list.
Response: 226-Transfer complete.
Response: 226 Quotas off
Command: TYPE I
Response: 200 Type set to I.
Command: PORT 192,168,100,59,13,133
Response: 200 PORT command successful.
Command: STOR stylesheet.css
Response: 150 Opening BINARY mode data connection for stylesheet.css.
Response: 226 Transfer complete.
Status: Upload successful
Default Setting is overwritte
-
rembert
- 504 Command not implemented
- Posts: 7
- Joined: 2004-08-13 21:47
- Location: Laren NH, Netherlands
Same problem here
Running Filezilla 2.2.9
Default setting: Overwrite
Log:
ommand: PORT 192,168,100,100,11,233
Response: 200 PORT command successful
Command: TYPE A
Response: 200 Type set to A.
Command: APPE leftmidframe.htm
Response: 451 leftmidframe.htm: Append/Restart not permitted, try again.
Error: Upload failed
I have no clue why it's trying to append. The destination file does exist and has a filestamp of several months ago. The file I try to upload has a filestamp of only seconds ago.
The problem is making me nervous: I cannot risk the software will ever try to append something to some file unless explicitly specified. Gladly the software appearantly discovers something isn't right and refuses the append.
To solve the problem I have found three ways:
1. Remove the destination file manually, then upload it again. This always succeeds but takes quite some effort with partial directory updates
2. Restart Filezilla sometimes seems to fix the problem
3. Wait a couple of minutes, reset the status on the error and reprocess the queue.
It seems to me two different bugs are involved:
A. The software appearantly ignores the upload settings and just uses 'append' as the standard setting in any situation
B. Somehow the filestamp of the sourcefile seems to confuse Filezilla
Looking forward to a fix for this issue.
Default setting: Overwrite
Log:
ommand: PORT 192,168,100,100,11,233
Response: 200 PORT command successful
Command: TYPE A
Response: 200 Type set to A.
Command: APPE leftmidframe.htm
Response: 451 leftmidframe.htm: Append/Restart not permitted, try again.
Error: Upload failed
I have no clue why it's trying to append. The destination file does exist and has a filestamp of several months ago. The file I try to upload has a filestamp of only seconds ago.
The problem is making me nervous: I cannot risk the software will ever try to append something to some file unless explicitly specified. Gladly the software appearantly discovers something isn't right and refuses the append.
To solve the problem I have found three ways:
1. Remove the destination file manually, then upload it again. This always succeeds but takes quite some effort with partial directory updates
2. Restart Filezilla sometimes seems to fix the problem
3. Wait a couple of minutes, reset the status on the error and reprocess the queue.
It seems to me two different bugs are involved:
A. The software appearantly ignores the upload settings and just uses 'append' as the standard setting in any situation
B. Somehow the filestamp of the sourcefile seems to confuse Filezilla
Looking forward to a fix for this issue.
FileZilla will try to resume automatically if a transfer fails so that it can continue. Unfortunately, your server is not configures properly:
A code 4 reply code tells the client it should retry, that's exactly what FileZilla does. I'll try to hack a workaround for this together, I think I can have it ready by the end of the week.451 leftmidframe.htm: Append/Restart not permitted, try again.
-
rembert
- 504 Command not implemented
- Posts: 7
- Joined: 2004-08-13 21:47
- Location: Laren NH, Netherlands
I had noticed that 451 before but forgot to mention it and didn't realize the consequences of this error. I get this error with quite some FTP servers, unfortunately these are all FTP servers maintained by several different ISPs. I guess they don't like to reconfigure their FTP servers.
On the other hand. I configured Filezilla it should never try to append. I didn't have a file transfer failure (at least not that I'm aware of). And even I had one, then IMO it should just redo the filetransfer as if it's a new filetransfer, overwriting the existing file.
It would be great to see a workaround!
On the other hand. I configured Filezilla it should never try to append. I didn't have a file transfer failure (at least not that I'm aware of). And even I had one, then IMO it should just redo the filetransfer as if it's a new filetransfer, overwriting the existing file.
It would be great to see a workaround!
Ah. Dodgy choice of message numbers in the RFC then?botg wrote:A code 4 reply code tells the client it should retry, that's exactly what FileZilla does
Yes, that's the bit that confused me.rembert wrote:On the other hand. I configured Filezilla it should never try to append.
I don't mind it going into a loop trying to do something that the server doesn't support. That's easy to understand. But when I set the transfer to overwrite rather than append, I expected that would be what would happen!
I go back to my suggestion of a per-site setting in the site manager that would allow you to say "this site does not support restarts", but if you can do it automagically from the returned message, well that's probably cleverer.
Filezilla still uses sometime APPE (overwrite is default)
Needed three trys to upload a modified file:
Command: APPE orders.php
Command: APPE orders.php
Command: STOR orders.php
Tue Feb 1 16:06:06 2005 1 62.138.223.211 656 /pub/orders.php
Tue Feb 1 16:06:48 2005 1 62.138.223.211 0 /pub/orders.php
Tue Feb 1 16:07:55 2005 1 62.138.223.211 35764 /pub/orders.php
The funny thing is i don't see any logic when filezilla users APPE or STOR.
Seems random, mostly STOR but sometime APPE (and APPE gives me parse errors)
Needed three trys to upload a modified file:
Command: APPE orders.php
Command: APPE orders.php
Command: STOR orders.php
Tue Feb 1 16:06:06 2005 1 62.138.223.211 656 /pub/orders.php
Tue Feb 1 16:06:48 2005 1 62.138.223.211 0 /pub/orders.php
Tue Feb 1 16:07:55 2005 1 62.138.223.211 35764 /pub/orders.php
The funny thing is i don't see any logic when filezilla users APPE or STOR.
Seems random, mostly STOR but sometime APPE (and APPE gives me parse errors)
The problem is that this was the initial upload of the modified file (i double clicked the file, filezilla didn't ask me anything, as i have set overwrite as default setting).
When executing the script i get an parse error. After the upload with store it worked.
I don't know if this failed APPE upload is a bug in filezilla or my FTP Server (vsftp) or the internet connection. But i would like the feature that Filezilla always uses STOR. APPE seems to make problems here
Henri
When executing the script i get an parse error. After the upload with store it worked.
I don't know if this failed APPE upload is a bug in filezilla or my FTP Server (vsftp) or the internet connection. But i would like the feature that Filezilla always uses STOR. APPE seems to make problems here
Henri
-
rembert
- 504 Command not implemented
- Posts: 7
- Joined: 2004-08-13 21:47
- Location: Laren NH, Netherlands
I just discovered the 2.2.10 actually tries this. But the server just doesn't accept the APPE command so we're not getting anywhere. It failed but Filezilla never asked for an action.botg wrote:I'll explain the APPE logic:
If a transfer fails or get's stopped and resumed by the user, FileZilla always uses APPE. Only if that fails, FileZilla asks the user for an action.
Before FZ 2.2.10, FileZilla could not properly handle a failing APPE.
Command: APPE view_d.php
Response: 451 view_d.php: Append/Restart not permitted, try again.
Error: Upload failed
I retried it two times and at then suddenly it just stored the file instead of appending it. Beats me why Filezilla changed its mind.
Response: 200 PORT command successful
Command: STOR view_d.php
I just feel uncomfortable with software which function I cannot predict. I had a very terrible day yesterday when I was uploading several perl scripts to a server. Somewhere something went wrong, so I re-uploaded the bunch. To my horror one file got appended at a point where it should be overwritten. Gladly this file didn't contain any plain-text passwords. I don't know if this was caused by Filezilla but due to the unpredictable APPE/STOR functionality I tend to blame Filezilla (I'm sorry to say so).
I'd prefer if I could turn-off the APPEND function entirely. I don't like Mozilla to use this function except when I explicitly ask for it with for instance a resume command - maybe a 'restart' can be added to the options? Besides a setup option like 'resume function always restarts entire transfer' per ftp connection sounds very good to me as some ftp servers do seem to support the append command correctly, others don't.