Re: [Duplicity-talk] Unusual broken pipe error

[Richard Scott]

> Do someone have a clue of what can take to this error?
> I got this error yesterday, and today the backup has run to the end
> without errors.
>
> Generating delta - changed file: share/soapy/firebird/tecelagem.fdb
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 401, in ?
> if __name__ == "__main__": main() File "/usr/bin/duplicity", line 395, in main
> else: incremental_backup(sig_chain)
> File "/usr/bin/duplicity", line 174, in incremental_backup
> bytes_written = write_multivol("inc", tarblock_iter, globals.backend) File 
> "/usr/bin/duplicity",
> line 82, in write_multivol globals.gpg_profile,globals.volsize) File
> "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 202,
> in GPGWriteFile file.write(data) File 
> "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line
117,
> in write def write(self, buf): return self.gpg_input.write(buf) IOError: 
> [Errno 32] Broken pipe
> gpg: Error writing to `-': Broken pipe
> gpg: handle plaintext failed: file write error
> gpg: Error writing to `-': Broken pipe
> gpg: handle plaintext failed: file write error
> gpg: Error writing to `-': Broken pipe
> gpg: handle plaintext failed: file write error
> gpg: Error writing to `-': Broken pipe
> gpg: handle plaintext failed: file write error
> gpg: Error writing to `-': Broken pipe
> gpg: handle plaintext failed: file write error
> gpg: Error writing to `-': Broken pipe
> gpg: handle plaintext failed: file write error

IMHO it looks like it ran out of disk space creating a temporary file during 
the backup.

When backing up a file Duplicity splits it up into chunks into temporary files 
and this will take
up disk space for a short time on the server doing the backup.

Perhaps check your disk space for /tmp

Rich.