Opened at 2009-06-22T17:01:31Z
Closed at 2010-02-11T01:37:14Z
#746 closed defect (duplicate)
Tahoe operations fail with "no attribute _writekey" exception
Reported by: | [4-tea-2] | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | undecided |
Component: | code-mutable | Version: | 1.4.1 |
Keywords: | repair | Cc: | |
Launchpad Bug: |
Description
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 --- <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").
Attachments (1)
Change History (5)
Changed at 2009-06-22T17:08:52Z by [4-tea-2]
comment:1 Changed at 2009-06-24T21:27:48Z by warner
This is probably another instance of #625, unfortunately.
comment:2 Changed at 2009-07-01T18:53:03Z by warner
- Component changed from unknown to code-mutable
- Owner nobody deleted
comment:3 Changed at 2009-12-05T23:59:10Z by davidsarah
- Keywords repair added
comment:4 Changed at 2010-02-11T01:37:14Z by davidsarah
- Resolution set to duplicate
- Status changed from new to closed
It's clear from the traceback that this is a duplicate of #625.
HTML output of exception after deepcheck-and-repair