Warning message for every volume using --asynchronous-upload

Bug #946993 reported by Daniel Andersson
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Debbugs
Fix Released
Unknown
Duplicity
Fix Released
Undecided
Unassigned

Bug Description

Using the --asynchronous-upload switch, the error message

Exception AttributeError: AttributeError("'_DummyThread' object has no
attribute '_Thread__block'",) in <module 'threading' from
'/usr/lib/python2.7/threading.pyc'> ignored

is thrown to STDERR every time a volume is created.

(I also used the -v5 switch)

Also reported as Debian bug #659004, but it has gotten no attention for a month.

Duplicity 0.6.17
Python 2.7.2+
Debian Sid
Linux

Tags: precise
Revision history for this message
Peter Petrakis (peter-petrakis) wrote :

There looks like there's a fix for this upstream, it just hasn't made it to the distribution yet.

http://bugs.python.org/issue14308

"""
msg155818 - (view) Author: Dustin Kirkland (Dustin.Kirkland) Date: 2012-03-14 23:48
My Apache2 logs are filled with the following error kicked out by my python wsgi script:

[Wed Mar 14 18:16:38 2012] [error] Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored

I was able to silence these with a simple conditional in /usr/lib/python2.7/threading.pyc:

- del self._Thread__block
+ if hasattr(self, '_Thread__block'):
+ del self._Thread__block

Full patch attached."""

I'm experiencing this as well, though it is not fatal in this case. I can readily observe the difftar being uploaded.

Changed in duplicity:
status: New → Confirmed
tags: added: precise
Revision history for this message
Rodrigo Alvarez (rodrigo-alvarez-i) wrote :

I'm seeing this exact same error in duplicity 0.6.18 running on Ubuntu 12.04 after starting a fresh install and a fresh backup set.

I also see a couple of other error messages such as:
Cleanup of temporary file /home/Backups/.duplicity_cache/f8b8ad7f550c05bc2f127fe057fa58a5/duplicity-QysQAI-tempdir/mktemp-1PdBc8-1 failed
Cleanup of temporary file /home/Backups/.duplicity_cache/f8b8ad7f550c05bc2f127fe057fa58a5/duplicity-ekKsvE-tempdir/mktemp-BY_STs-1 failed

Please help, the backups claim to finish successfully, but it is hard to trust a new backup set/system if the first log is all dirty with errors.

Changed in debbugs:
status: Unknown → Confirmed
Changed in debbugs:
status: Confirmed → Fix Released
Changed in duplicity:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.