Re: [Duplicity-talk] FTP Failure on DreamHost

[Steve Sloan]

Jay Summet wrote:
> One way to get around that (Dreamhost specific) is to create a second username
> (username_backup) for your scp/ftp backups, and only use it for backups. 

That is a good idea, but unfortunately I'm already using a dedicated 
username, mostly just for disk accounting.

No, this is definitely caused by something on the client side.  It fails 
instantly and consistently, and only on DH (as far as I can tell). 
Plus, from the backtrace, it looks like the initial directory listing 
succeeded (226), but python/ftplib/duplicity fails anyway.

> Steve Sloan wrote:
> > When trying to backup to DreamHost via FTP, I keep getting:
> >
> >   File "/usr/bin/duplicity", line 373, in ?
> >     if __name__ == "__main__": main()
> >   File "/usr/bin/duplicity", line 349, in main
> >     globals.archive_dir).set_values()
> >   File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line
> > 406, in set_values
> >     backend_filename_list = self.backend.list()
> >   File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line
> > 373, in list
> >     try: return self.error_wrap('nlst')
> >   File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line
> > 343, in error_wrap
> >     except ftplib.all_errors, e: raise BackendException(e)
> > duplicity.backends.BackendException: 226 Transfer complete.
> >
> > Why is a successful result code generating an exception?  Is this an
> > ftplib bug or a duplicity bug?  And why is it only DH?  Any ideas?
> >
> > Thanks ...

-- Steve