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.

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

MAINNET: node.sh panics #2808

Closed
mindstyle85 opened this issue Apr 11, 2020 · 5 comments
Closed

MAINNET: node.sh panics #2808

mindstyle85 opened this issue Apr 11, 2020 · 5 comments
Assignees
Labels

Comments

@mindstyle85
Copy link

Describe the bug

OS: ubuntu 18.04 64bit
node.sh: version: v1 20200327.0

photo_2020-04-11_02-12-59

@gupadhyaya
Copy link
Contributor

if currentBlock == nil {
		// Corrupt or empty database, init from scratch
		utils.Logger().Warn().Str("hash", head.Hex()).Msg("Head block missing, resetting chain")
		return bc.Reset()

exploding in return bc.Reset(), which can be fixed, @mindstyle85 did you try cleaning db?

@mindstyle85
Copy link
Author

hmm thats odd, it happened on a FN runner that just downloaded db via rclone, so only possibility is the snapshots were corrupted? I will check with him though and ask him to re-download the snapshots @gupadhyaya

@mindstyle85
Copy link
Author

confirmed it was a db problem, looks like the rclone copy yesterday was bad

im guessing it should still not explode right, but rather give out an error message and shut down?

@gupadhyaya
Copy link
Contributor

@mindstyle85 yes, this is also observed in go-ethereum: ethereum/go-ethereum#19286. Will port their fix that initializes the currentBlock and currentFastBlock atomic to nil block of right type.

@mindstyle85
Copy link
Author

sure @gupadhyaya once the fix is ported in you can close this one, will be hard to check unless we corrupt db on purpose hehe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants