On Sat, Mar 26, 2005 at 11:32:59AM -0500, James Wald wrote: > I have been having this issue for a while now and after speaking with a few > other users with this client and drftpd server I appear to be the only one > with the problem. I have the same configuration as when I found the > "Waiting for copy peer..." issue, but this has been happening ever since I > started using lftp. I am trying to mirror a directory which may contain > offline files, the server replies 530 No transfer-slave(s) available to the > PRET RETR message but lftp appears to be ignoring the 5xx message and ends > up in an endless loop of the following commands: > > ---> PRET RETR .message > <--- 530 No transfer-slave(s) available > ---> PASV > <--- 500 You need to use a client supporting PRET (PRE Transfer) to use PASV > ---> RETR .message > <--- 450 net.sf.drftpd.NoAvailableSlaveException: /test/.message has 0 > slaves online > ---> PRET RETR .message > <--- 530 No transfer-slave(s) available > ---> PASV > <--- 500 You need to use a client supporting PRET (PRE Transfer) to use PASV > ---> RETR .message > <--- 450 net.sf.drftpd.NoAvailableSlaveException: /test/.message has 0 > slaves online
Reply for PRET command is ignored by lftp, because it is an optional command which can be unimplemented. Besides, PRET documantation (http://drftpd.mog.se/wiki.phtml?title=Distributed_PASV) states: If any reply other than these are received it is the reply of the upcoming transfer command. The client is not required or encouraged to act on this reply and can continue sending PASV and transfer command to receive the same error from the upcoming transfer command. But then RETR command returns 450 code, which is a retriable error. Probably lftp should act on 500 error to PASV command. I'll check that. -- Alexander. | never mind that noise you heard
