Network froze on 1874879 May 22, 2023 4:02:30 AM UTC / daemon can't start too #5383
Comments
gades
changed the title
|
There was a problem during v19 activation of Dash Core. The chain is stalled and currently not producing blocks. We have everyone investigating the issue. |
|
|
|
After update to |
the same issue with v19 and you can fix by downloading blocks from network and it will work until daemon will up |
is there any way to fix this without resync? |
Untill it becomes clear what exactly the issue is and how they plan to address the issue (hotfix ?) we should just wait. |
|
They did patch ea18452 and new version is accepting blocks from miner who is using last one ... |
|
Upgrading to 19.1.0 doesn't help, the node is stuck at |
Yeah, i ended up giving my masternodes a reindex command after updating to v19.1 |
|
current VALID height and hash I see is / are |
|
I am seeing a lot (and i mean a lot) of 'CActiveMasternodeManager::Init -- ERROR: Local address does not match the address from ProTx' messages in my debug.log after i updated to v19.1 and issued a reindex. I checked a few masternodes of mine and those i checked all had that error message in their debug.log Update : decided to just remove the blockchain and most of the .dat files and download and sync from scratch. |
It suddenly started to sync and it seems to be working fine now. |
|
With 19.1. Still froze for us. Tried to invalidate and reconsider (even using earlier blocks) and didn't help. Getblockcount, getpeerinfo and getblockchaininfo after the break. Would appreciate all help |
|
@maayank pls try disconnecting a couple of nodes so that the first node in |
|
If you are stuck on block 1874880, you can try to perform the following grab this text here: https://gist.github.com/PastaPastaPasta/ace08090e6034b3cd1b7f1379776be7f and run submitblock |
|
Anyone have other solution to share? I'm still stucking at Please help, thank you. |
how long have you waited until it work normally ? I have upgrade to v19.1.0 for 2 hours but it's still stucking at 1874879. have you take any other action to recover it？ |
I did following steps:
other steps like invalidateblock / reconsiderblock / submitblock / disconnectnode were unsuccessful |
|
dash v19.1.0 crashed with following error. |
can you try to remove all files in ~/.dashcore/ except dash.conf / wallet.dat and start again? |
did you mean that you clear the chaindata and resync the chain? |
yes, it's only one way which solve this issue for me |
|
Just wanted to say that by now our node resumed syncing |
Several hours. We also tried to delete |
Resyncing node from scratch was approx 2-3 hours and our nodes are up. But strange , before we start do it the count blocks were higher than in the main net @PastaPastaPasta will there new update because I didn't saw any fixes for v19 and only one change is reschedule start voting to 15 June ? |
|
You should only have to launch with -reindex, not do a full resync. |
|
Yes, there will be an 19.2 once we have proper fixes for the issues we saw. |
|
It's been at least 5 days, still not fixed❓ Is the dash chain dead❓ No one uses this chain anymore❓ 😴 |
|
$ dash-cli --version $ dash-cli getblockchaininfo|head remove all files in ~/.dashcore/ except dash.conf / wallet.dat resync, three times, same result. |
|
Make sure you reindex (-reindex or reindex=1 in your config file), then it should resume fine. You make have to do a reconsiderblock on the correct block too. |
|
before "remove all files ... and resync", already tried reindex, invalidateblock/reconsiderblock, but it doesn't work. |
|
In two days a new Dash bootstrap file will be created (June 1 00:00:01 UTC 2023) See : https://github.com/UdjinM6/dash-bootstrap It does mean waiting for two more days. With me the removal of all files in ~/.dashcore/ (except dash.conf / .lock / settings.json / sentinel folder) did the trick for my masternodes. |
|
I tried run
What does it mean? Is there cause of concern? Dash Core 19.1.0 |
That's an artefact of postponing hard fork v19 (bit 8). |
Just in case, I've updated Dash Core to 19.2 and i still see this warning. |
|
Can you guys help BTCPAYSERVER bump their version to latest? I'm stuck with this bug. According to btcpayserver/btcpayserver-docker#803 you should help them somehow. |
There is an open PR there to do this. See btcpayserver/btcpayserver-docker#800 |
|
Block sync stopped at 1899071. reconsiderblock 0000000000000015e32e73052d663626327004c81c5c22cb8b42c361015c0eae both, not helped! $ dash-cli --version $ dash-cli getblockchaininfo|head $ dash-cli getblockhash 1899071 1899071 hash： https://insight.dash.org/insight/block/0000000000000022cd5c8d422c2e9b3a876dee260402e8850d95ca3bf64cb9b6 1899072 hash： https://insight.dash.org/insight/block/0000000000000015e32e73052d663626327004c81c5c22cb8b42c361015c0eae $ grep "is marked invalid" debug.log |
the same problem here . |
|
You need to update to v19.2 if you haven't already and then reindex your chain:
|
It works,thank you very much |
Daemon can't start in case restart - invalid blocks and after resync it stops on 1874879
The text was updated successfully, but these errors were encountered: