-
Notifications
You must be signed in to change notification settings - Fork 992
Interrupting grin during chain validation results in corrupted data #2770
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
Comments
This is a log on a release node just before the interrupt:
|
I also saw several times of this problem, our current shutdown (on kill normally) operation is definitely not safe, this should be a major issue for a production environment since will check the shutdown process. |
I see it again on one of my seed servers:
|
Look like now it's a very high probability to get this problem, I'm upgrading all my 4 seed servers but 3 of them have this |
I'm still seeing this in v2.0.0 - now by following a slightly different way: I'm trying to sync from scratch but it's always get stuck a couple of blocks before the hard fork, and when I restart grin via systemd it crashes with the same error as this issue:
|
Closing. Feel free to reopen if this is still the case in grin v3.0.0. |
I have been able to reproduce #1620 deterministically in v1.1.0.beta-1 (running on Fedora 28).
Steps to reproduce:
My latest try:
The text was updated successfully, but these errors were encountered: