Re: [Duplicity-talk] GPGError - empty GnuPG log

[Oliver Cole]

Thanks Edgar,

On 27/04/2018 02:25, edgar.soldin--- via Duplicity-talk wrote:
> nope, not without an error stack stack to see where the error was thrown. you can try 
> running in debug verbosity '-v9' (really lot's of output) and "hope" it happens 
> again. maybe this will help pinpointing the issue.

Oh, I had this, but I didn't think it would be useful:

Apr 26 07:58:07 GPG error detail: Traceback (innermost last):
Apr 26 07:58:07   File "/usr/bin/duplicity", line 1555, in <module>
Apr 26 07:58:07     with_tempdir(main)
Apr 26 07:58:07   File "/usr/bin/duplicity", line 1541, in with_tempdir
Apr 26 07:58:07     fn()
Apr 26 07:58:07   File "/usr/bin/duplicity", line 1393, in main
Apr 26 07:58:07     do_backup(action)
Apr 26 07:58:07   File "/usr/bin/duplicity", line 1511, in do_backup
Apr 26 07:58:07     full_backup(col_stats)
Apr 26 07:58:07   File "/usr/bin/duplicity", line 572, in full_backup
Apr 26 07:58:07     globals.backend)
Apr 26 07:58:07   File "/usr/bin/duplicity", line 430, in write_multivol
Apr 26 07:58:07     globals.volsize)
Apr 26 07:58:07   File 
"/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 401, in 
GPGWriteFile
Apr 26 07:58:07     file.close()
Apr 26 07:58:07   File 
"/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 286, in close
Apr 26 07:58:07     self.gpg_failed()
Apr 26 07:58:07   File 
"/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 271, in gpg_failed
Apr 26 07:58:07     raise GPGError(msg)
Apr 26 07:58:07  GPGError: GPG Failed, see log below:
Apr 26 07:58:07 ===== Begin GnuPG log =====
Apr 26 07:58:07 ===== End GnuPG log =====


> another "hack" could be writing a shell wrapper for gpg, piping all output via 
> tee to the outs _and_ into a log file.

If it happens again I will give that a go.

> also check your syslog/dmesg for oom killing or such during that time.

Nothing in syslog.