Hello minerja,
I'm stuck syncing at block 2332117.
I have tried every wallet, with / without bootstrap.
Even tried Clean install win 7 and 10, and everytime i get stuck at block 2332117.
Any ideas please? Never had this issue with Datacoin before...
Which release(s) are you using specifically, or did you compile Datacoin-Qt on your own?
If you compiled Datacoin-Qt on your own which version of boost did you use?
Earlier when fedde reported his issue, I went to check a node I operate.
A corruption happend on the active chain and i have to rebuild it.
This particular node had indeed crashed and so I started it again with a -reindex and it caught up and has been running since then.
Though I wasn't smart enough to have shrinkdebugfile enabled in my datacoin.conf and so I lost the snippet of the log file which included the error.
This box does run the binary released on GitHub.
There is another box where I run a Datacoin daemon and although it was not running at the time of the reported corruption, it did sync and catchup to the chain without error.
Tonight, I started up a Datacoin-Qt instance on macOS from the GitHub release which hasn't been on for a few weeks.
It also caught up to the tip of the chain without error.
I don't know why you're stuck at block 2332117 which is why I'd like to know which peers you're connected with (getpeerinfo from the Debug window) and if you're using one of our releases or if you compiled it on your own.
My first thought about the reported corruption in the large block was that perhaps there were too many signature operations inside a transaction.
Turns out that wasn't the case since it looked like a plain 90,199 byte tx with a simple script.
re: txid d1d059d5ac333d72ccf8b1e222264cd0c5ca7fb5c8c09db01fa0ec05a935abd3
Similarly, the last tx in that run, txid 1a9d1a244dc0125c11a43d2bbeb86174e7685781d4a2f3a8a9c84a1a1d75dde8 is 90,347 bytes and also includes simple script.
I'll need to have a debug.log capture the datacoind crash next time it happens or have someone willing to reproduce it on testnet so that we can work through the reported corruption.
Looking for to learning more information about your configuration on the above inquiries so we can help you.
Best Regards,
-Chicago