-
Notifications
You must be signed in to change notification settings - Fork 291
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
Comments
exploding in |
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 |
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? |
@mindstyle85 yes, this is also observed in go-ethereum: ethereum/go-ethereum#19286. Will port their fix that initializes the |
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 |
Describe the bug
OS: ubuntu 18.04 64bit
node.sh: version: v1 20200327.0
The text was updated successfully, but these errors were encountered: