Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automatically recover from Bad Block / Corrupt DB #1196

Closed
jorisbontje opened this issue Jun 7, 2015 · 2 comments
Closed

Automatically recover from Bad Block / Corrupt DB #1196

jorisbontje opened this issue Jun 7, 2015 · 2 comments

Comments

@jorisbontje
Copy link

Geth 067e66b is stuck in a bad block loop. Probably after killing geth at some point (with Ctrl-C) to perform a client update:

I0606 10:59:44.241961    1469 chain_manager.go:765] Bad block #508111 (8165d32f9f48e494231d84b3f59d0940f5657c1821090a12e8d538da313663e4)
I0606 10:59:44.242269    1469 chain_manager.go:766] Transaction w/ invalid nonce. tx=3667  state=0)

From which it can't recover. Besides manually resetting the blockchain and restarting syncing from scratch, I'd expect geth be able to automatically recover from this; discard the bad block and resume operations.
@jorisbontje
Copy link
Author

related #1190

@joeykrug joeykrug mentioned this issue Jun 21, 2015
Closed
@jorisbontje
Copy link
Author

Haven't seen this issue for ages.

@snyk-bot snyk-bot mentioned this issue Apr 26, 2021
Open
maoueh pushed a commit to streamingfast/go-ethereum that referenced this issue Apr 30, 2024
@anshalshukla
Merge pull request ethereum#1196 from maticnetwork/update-pebble
5461f9b 
Update pebble from upstream
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jorisbontje