Messages about "corrupted or incomplete CURRENT file"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I started receiving this message when trying to do basically anything with keybase (pgp verify, list-trackers, etc):
- WARNING Failed to load [[[LoadUser uid redacted]]] from storage: leveldb/storage: corrupted or incomplete CURRENT file
- ERROR leveldb/storage: corrupted or incomplete CURRENT file
I decided to try updating my client, and installed version 1.0.16-20160701140709+9c6469c.
The problem persisted. Additionally, when I entered my chose "Login" on the GUI and entered a userid, I received this message:
There was an error provisioning
Unknown error: Error: leveldb/storage: corrupted or incomplete CURRENT file
My keybase.service.log has similar log entries:
2016-07-02T16:21:23.463991 - [WARN keybase loaduser.go:227] 016 Failed to load [[[LoadUser uid redacted]]] from storage: leveldb/storage: corrupted or incomplete CURRENT file
Some searching online indicates that this may be caused by a system crash, which is plausible.
I decided to rename the file
C:\Users\[username]\AppData\Roaming\Keybase\keybase.leveldb\CURRENT
to a new name
C:\Users\[username]\AppData\Roaming\Keybase\keybase.leveldb\CURRENT.corrupt
and try again.
This seems to have resolved my problem; I was able to login and use the client successfully.
If this is an acceptable solution, the client (or at least the GUI) should ideally be able to recover from this issue automatically.
I'm running Windows 7 x64.
my log id: 70dd9a02d479ed7c6c00d11c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Windows 7 failure using the reported leveldb/storage error and the keybase.leveldb\CURRENT path. Trace how the client handles a corrupted CURRENT file, then verify that login and operations such as PGP verification and tracker listing recover without manual renaming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100