Re: [Duplicity-talk] Duplicity not displaying some GPG errors

[Simon Ruderich]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Apr 04, 2009 at 02:32:51PM -0500, Kenneth Loafman wrote:
> Simon Ruderich wrote:
>>
>> No Gnupg log was displayed. Raising the verbosity didn't help. So
>> I added "raise" statements in the python code to see the error,
>> it was "IOError: [Errno 32] Broken pipe". Most search results
>> indicated this is a trust problem, but my trust settings were
>> fine. So I ran strace and found out, that my /tmp was full. I
>> added --tempdir and everything works fine now.

Well, except for one thing I just noticed. I now use --tempdir
$HOME/tmp which fixed the problem, but duplicity doesn't ignore
it's own temporary files so it ended up backing up its own
temporary files as well. Would it be possible to automatically
ignore the temporary directory or better duplicity's temporary
directory in --tempdir?

> The logging should only happen on a gpg error, so I may have something
> wrong there.  The reason I push logging the gpg errors so hard is that
> quite often the broken pipe error is really a gpg trust or password
> error that has nothing to do with broken pipe.

Thanks for your quick reply.

This is a gpg error so I think it should be displayed. My problem
was that no message was shown at all and I didn't know what
happened.

> In your case the broken pipe is being raised, but that's not really the
> problem.  The upstream problem was a full filesystem that caused the
> broken pipe.  I need to find a way to get to that error, or we're going
> to keep seeing broken pipe being blamed on everything.  That and FTP are
> the two major support issues with duplicity, and regrettably, both are
> well outside my control.

I don't know the gpg interface (looked only a second at the
code), but wouldn't it be possible to get gpg's "raw" error and
display it as is when a high verbosity is set (9 or so)? So that
the user can get the real source of the problem if necessary but
isn't bothered normally.

> ...Ken

Thanks,
Simon
- -- 
+ privacy is necessary
+ using http://gnupg.org
+ public key id: 0x6115F804EFB33229
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknX7CYACgkQYRX4BO+zMimiAgCeKh+boYSC7q38a5R9BV3c+bpV
ZDMAoNEWxV6WPPKAzyF8ZFfAJiNLu1QS
=JBnD
-----END PGP SIGNATURE-----