-
Notifications
You must be signed in to change notification settings - Fork 3k
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
0.21.3 doesn't like block 1228431 0.21.2.2 is OK #961
Comments
In 0.21.3 can you try console command |
unfortunately i'm not fast enough to get to the console before we bomb and exit. i tried doing it with 0.21.2.2, i.e. and then re-running 0.21.3 but we bomb and exit for the same block - but thanks for the idea |
I'm having the same issue is there any workaround on how to upgrade to |
I would try resyncing from scratch. Delete the blocks directory. |
gituser are you have the problem with the same block (1228431) or a different block? if it is a different block could you let us know which one? thanks! |
@kl1059
|
same error, same block, macOS. no fix? |
unfortunately for me workarounds listed in this thread didn't help, I had to take synced blockchain from other server |
I can see there is a new release https://github.com/litecoin-project/litecoin/releases/tag/v0.21.4 but I was not able to see if this issue is fixed already or not? |
@arshad-deriv sorry I'm not able to reproduce this issue. Have you tried resyncing from scratch? |
I don't know if it was the same block, but some days ago my litecoin node crashed with a similar error i think, i tried to resync the block headers but when it was trying to resync the block headers i was getting a segfault error so i tried to resync completely which took 1 day but after that it worked. About the segfault error i was using litecoind 0.21.3 aarch64 but i now upgraded to 0.21.4 |
@losh11 I did not need to resync from scratch so far but I have not upgraded the node just to avoid any unforeseen issue like mentioned above that it gives an error on some specific block and needs to resync from scratch afterward which is time-consuming. May I know if upgrading to 0.21.4 fixes the issue? |
0.21.3 debug.log:
2024-04-22T17:18:47Z ERROR: UndoReadFromDisk: Checksum mismatch
2024-04-22T17:18:47Z *** ThreadSync: Failed to write block 75d457c945c6666d92871fdd12f5380b9e01b25268f7d81870c1b0c6edb33241 to index database
2024-04-22T17:18:47Z Error: A fatal internal error occurred, see debug.log for details
shortly after syncing with 0.21.3 litecoin will stop with the above error. 0.21.2.2 continues to run after syncing.
could be a problem on my side but i wanted to post this for FYI
The text was updated successfully, but these errors were encountered: