-
Notifications
You must be signed in to change notification settings - Fork 60
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
v8.22.0-rc3 crashes before finishing synchronisation #191
Comments
Thanks for sharing this. So just to be clear you:
Is that correct? Did it happen just the once? Or have you been able to recreate it? I don't suppose you have a backup of the old chain to try again? |
Correct.
It happened a few times until I realised I could try fixing it with the stable version.
I do have a backup of the chain from 2018. Unfortunately reaching the point of failure would take another few weeks (my internet is so slow 😢) It's about 1.1 GB. Probably better to upload somewhere than to attempt to synchronise again |
And there is nothing unusual in debug.log? Do you know what version the old chain was originally synced with? Was it 7.17.3? |
Nope, just the blocks being downloaded before the crash.
Apparently it was 6.14.2 (from the installer name I have in a backup disk) |
Since version 6 chain and 7 is incompatible with each other due to breaking changes I don't think this should be an issue. The only way to get it working, even if it weren't to crash, is to clear all block data and sync from scratch. |
Ah ok, I wasn't aware. I'll have to sync from scratch then 😭 I have a default wallet and an additional wallet which apparently was created in a subdirectory. I'd like to keep both but version 7.17.3 doesn't seem to support multiple wallets. Is it ok if I keep using the 8.22 RC3? |
As far as we know for sure, you should be able to keep using 8.22 RC3, but that being said, it is a somewhat experimental version meant for testing to find issues, and there may still be many that we do not yet fully comprehend. The issue you have experienced with the client crashing might just be that, a bug in that version, so please be aware that you may encounter further issues and that we are all extremely grateful if you keep reporting issues found here in GitHub. |
Ok, I will try 8.22.0-RC3 once more, this time from scratch. Are wallets from version 6 compatible? Is keeping only wallet.dat and the second wallet subdirectory ok? Or should I keep something else? |
Is this still a valid issue? |
I’m still synchronizing from scratch to test whether the old 6.x db starting point was causing the issue or not. I’ve already downloaded all the headers, it's now getting the blocks. I guess it will take a few more days. |
Synchronising from scratch, it's still crashing 😞 These are the last few log lines in
I suspect this is caused by a transaction from 2018 that is in my wallet (it shows in the recent transactions section since the beginning of the synchronisation), namely the following 10760ee84d1e04bde910b6456d2fa106699e58df0da650273de6e77153dfe88d But I'm not sure because there are logs of three blocks after it. A second run went two blocks further before crashing:
I guess, this is consistently crashing now, a third time crashed at height=6026795, again. Should I try removing the wallet before restarting synchronisation? Just to check whether it's the culprit or not. |
Have you tried a completely fresh sync from the beginning with v8.22 rc3? It seems like you have a corrupted local DB. I have had this happen in the past when upgrading versions. But a fresh sync with latest wallet or a full reindex=1 always fixed the issue. Cheers |
I've done a fresh sync, I think. I started with an empty node directory. Only my old wallet.dat was there. |
Hmm, I deleted Any idea of how to recover/upgrade the wallet? |
I hope you have a backup of your You say empty node folder, can you please elaborate what you mean by this? |
I hope you have a backup of your wallet.dat?
Yes, I have a backup.
So, after deleting the wallet the synchronization continued without issues. A few blocks later, I stopped the client, restored the `wallet.dat` and then started the client again.
Synchronization continued without problems then. And I was able to move the funds to a newer wallet which hopefully doesn’t have this issues.
You say empty node folder, can you please elaborate what you mean by this?
I mean an empty data directory, where digibyte wallet downloads its files. There was only the `wallet.dat` file in there.
As I said above, I’m in the process of moving the funds to another wallet which was created by the newer digibyte-core program.
So, with the wallet emptied, I could share the dat file to debug this further, in case anyone is interested :D
… —
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Well, as my old wallet seems hexed 😄 , I finally moved all the funds to a new one. Maybe it is related to it being created with an old version of DigiByte-Core although it's weird it only crashed on the old transaction and not on the newer ones made this year. I'm not sure how many people are in the same situation as me, probably not many. So, it may make sense to close this issue now. |
Expected behaviour
The node is able to synchronise fully and continue operation normally.
Actual behaviour
Somewhere before fully synchronisation the application crashes.
The following is the event on the Windows 11 Event Console.
dgb-evtx.zip
To reproduce
Synchronise the blockchain DB, I guess. I started with an old database from 2018 and synchronised up to the very few days of march 2024.
I then downloaded 7.17.3 and completed the synchronisation. And now the v8.22.0-rc3 seems to work ok. So, I'm not sure what's happening.
System information
There's no unusual log entries in debug.log file before the crash. Only the Windows event attached above.
The text was updated successfully, but these errors were encountered: