Tahoe operations fail with "no attribute _writekey" exception #746

Closed
opened 2009-06-22 17:01:31 +00:00 by [4-tea-2] · 3 comments
[4-tea-2] commented 2009-06-22 17:01:31 +00:00
Owner

My weekly cronjobs ("deep-check --repair" and "backup") started failing two days ago. Upgrading to the latest Debian package (allmydata-tahoe_1.4.1-r3916_all.deb) did not help, the problem persists.

Example output from the cli (this is from allmydata-tahoe_1.4.1_all.deb, ie. pre-update):

$ tahoe deep-check --repair media:
ERROR: AttributeError(MutableFileNode instance has no attribute '_writekey')
[Failure instance: Traceback: <type 'exceptions.AttributeError'>: MutableFileNode instance has no attribute '_writekey'
/usr/lib/python2.5/site-packages/twisted/internet/base.py:705:runUntilCurrent
/usr/lib/python2.5/site-packages/foolscap/eventual.py:26:_turn
/usr/lib/python2.5/site-packages/twisted/internet/defer.py:243:callback
/usr/lib/python2.5/site-packages/twisted/internet/defer.py:312:_startRunCallbacks
--- ---
/usr/lib/python2.5/site-packages/twisted/internet/defer.py:328:_runCallbacks
/usr/lib/python2.5/site-packages/allmydata/mutable/checker.py:301:_maybe_repair
/usr/lib/python2.5/site-packages/allmydata/mutable/filenode.py:263:repair
/usr/lib/python2.5/site-packages/allmydata/mutable/repairer.py:89:start
/usr/lib/python2.5/site-packages/allmydata/mutable/filenode.py:172:get_writekey

Output from allmydata-tahoe_1.4.1-r3916_all.deb is identical, up to the line numbers.

Running "deepcheck-and-repair" from the WUI results in the same exception, yet no incident report is created. I'll attach the HTML output of the result page (after clicking "reload").

My weekly cronjobs ("deep-check --repair" and "backup") started failing two days ago. Upgrading to the latest Debian package (allmydata-tahoe_1.4.1-r3916_all.deb) did not help, the problem persists. Example output from the cli (this is from allmydata-tahoe_1.4.1_all.deb, ie. pre-update): $ tahoe deep-check --repair media: ERROR: [AttributeError](wiki/AttributeError)(MutableFileNode instance has no attribute '_writekey') [Failure instance: Traceback: <type 'exceptions.AttributeError'>: [MutableFileNode](wiki/MutableFileNode) instance has no attribute '_writekey' /usr/lib/python2.5/site-packages/twisted/internet/base.py:705:runUntilCurrent /usr/lib/python2.5/site-packages/foolscap/eventual.py:26:_turn /usr/lib/python2.5/site-packages/twisted/internet/defer.py:243:callback /usr/lib/python2.5/site-packages/twisted/internet/defer.py:312:_startRunCallbacks --- <exception caught here> --- /usr/lib/python2.5/site-packages/twisted/internet/defer.py:328:_runCallbacks /usr/lib/python2.5/site-packages/allmydata/mutable/checker.py:301:_maybe_repair /usr/lib/python2.5/site-packages/allmydata/mutable/filenode.py:263:repair /usr/lib/python2.5/site-packages/allmydata/mutable/repairer.py:89:start /usr/lib/python2.5/site-packages/allmydata/mutable/filenode.py:172:get_writekey Output from allmydata-tahoe_1.4.1-r3916_all.deb is identical, up to the line numbers. Running "deepcheck-and-repair" from the WUI results in the same exception, yet no incident report is created. I'll attach the HTML output of the result page (after clicking "reload").
tahoe-lafs added the
unknown
critical
defect
1.4.1
labels 2009-06-22 17:01:31 +00:00
tahoe-lafs added this to the undecided milestone 2009-06-22 17:01:31 +00:00
[4-tea-2] commented 2009-06-22 17:08:52 +00:00
Author
Owner

Attachment tahoe-exception.html (8287 bytes) added

HTML output of exception after deepcheck-and-repair

**Attachment** tahoe-exception.html (8287 bytes) added HTML output of exception after deepcheck-and-repair

This is probably another instance of #625, unfortunately.

This is probably another instance of #625, unfortunately.
warner added
code-mutable
and removed
unknown
labels 2009-07-01 18:53:03 +00:00
davidsarah commented 2010-02-11 01:37:14 +00:00
Author
Owner

It's clear from the traceback that this is a duplicate of #625.

It's clear from the traceback that this is a duplicate of #625.
tahoe-lafs added the
duplicate
label 2010-02-11 01:37:14 +00:00
davidsarah closed this issue 2010-02-11 01:37:14 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#746
No description provided.