Tahoe operations fail with "no attribute _writekey" exception #746
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#746
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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").
Attachment tahoe-exception.html (8287 bytes) added
HTML output of exception after deepcheck-and-repair
This is probably another instance of #625, unfortunately.
It's clear from the traceback that this is a duplicate of #625.