Re: [Duplicity-talk] "Bad fd number" with new FTP backend

[Kenneth Loafman]

address@hidden wrote:
> I'm trying to use the new FTP backend to perform a full backup from my
> Linux computer to my Windows box (running FileZilla).  I'm then
> uploading the results to Amazon S3 from Windows.
> 
> I used this command line (I know, I know, I'll change it to "-v 9" until
> we get a stable new Duplicity release).
> 
> duplicity -v 6 --archive-dir /var/backups/duplicity_archives
> --include-globbing-filelist list --full --short-filenames /
> ftp://address@hidden/
> 
> The full backup runs for several hours:

Probably need to split into a few smaller backups.  This would allow you
to recover faster and easier.

> and then fails with these error
> messages:
> 
> Comparing ('root', 'tmp') and None
> Generating delta - new file: root/tmp
> Comparing ('root', 'tmp', 'HyperSpec-7-0.tar.gz') and None
> Generating delta - new file: root/tmp/HyperSpec-7-0.tar.gz
> Running 'ncftpput -F -t 30 -u 'backup' -p '???' -V -c 'Deck'
> 'df.jlew61.u5.dt.g' < '/tmp/tmpII5RRL'' (attempt #1)
> Running 'ncftpput -F -t 30 -u 'backup' -p '???' -V -c 'Deck'
> 'df.jlew61.u6.dt.g' < '/tmp/tmpjfQamd'' (attempt #1)
> Running 'ncftpput -F -t 30 -u 'backup' -p '???' -V -c 'Deck'
> 'df.jlew61.m.g' < '/tmp/tmpD1PJH4'' (attempt #1)

Wrote the manifest.

> Running 'ncftpput -F -t 30 -u 'backup' -p '???' -V -c 'Deck'
> 'dfs.jlew61.st.g' < '/tmp/tmpAu4ZVi'' (attempt #1)

Wrote the signatures.

> Reading results of 'ncftpls -F -t 30 -u 'backup' -p '???'
> 'ftp://address@hidden/''

Getting a directory listing of the remote system.

> Running 'ncftpls -F -t 30 -u 'backup' -p '???' -X 'DELE
> /dfs.jlew61.st.g' 'ftp://address@hidden/' >& /dev/null' (attempt #1)

Now its trying to delete the signatures it just wrote.  I don't know
why, but will look into it.

> sh: Syntax error: Bad fd number

Bad fd number from the shell.  Which shell do you use?  If its not bash,
then its possible the problem may be in the '>&' redirection.

<snip>

> As an aside, does this mean that it's trying to delete files on the
> Windows box?  There was only an empty directory there when it started
> the full backup; why would it be deleting files?  Also, I told it to
> store the signatures locally using the --archive-dir switch, so if it's
> trying to delete signatures, it shouldn't be doing it via FTP.

Yes, it was trying to delete the sig files on the windows box.  Why is a
good question, but there have been reports of problems with
--archive-dir, so this may be one of them.  It looks like it stored the
sigs remotely, then tried to delete them.  The deletion command with its
redirection of '>&' may not be compatible with non-bash shells.  Another
problem may be that the system has run out of open file descriptors due
to a failure to close files and it just hits the shell when it tries to
run ncftpls.

Believe it or not, but you may have a complete backup sitting on the
Windows box.  The only way to tell is to do a --collection-status and
find out.

...Ken

signature.asc
Description: OpenPGP digital signature