App: Invalid block 597925

[Anlien75]

Hello,

have today made the update to the latest version 2.1.12.

Unfortunately, the synchronization always breaks at 99.91%. But the blocks themselves are synchronized (598463 at 20:05).
Have deleted the DeFi app and reloaded again.

What else can I do to access my wallet?

Greetings Andy

[cRuuZaR]

Same issue here with Mac

[domo88]

same here with windows 10 and app version 2.1.12. stops at block 597924:

[Jacobsieler8888]

I have the same problem with windows 10. Except mine will not sync after block 597952. Can anyone help?

[madeinusmate]

same, stuck at block 597924. tried multiple releases they get all stuck at the same block.
The behavior appeared first after 9:30 PM SG Time on Jan 25th.

[DanielZirkel]

Same issue on my side.
It seems that the synchronization is stucked at the block of the triggered blockchain update.

I also tried to use the CLI and here it shows me an invalid block 597925

Here is the Hash of the block from CLI output:
0ff2aa3749300e3d0b5bc8d48f9d699bc42e222fe718dc011b33913127087c6d

Here is also my Log-File from the App
AppLog20210126.log

Update 1:
I started the Node several time via CLI. For me it looks like, that I am connected with other nodes, which have blocks smaller or equal block 597924 (except the first peer). This lead to no error in the node window, but if I cannot get information behind the block 597924 (like getblock).

Block 0ff2aa3749300e3d0b5bc8d48f9d699bc42e222fe718dc011b33913127087c6d is working in CLI

The next block (597926) 73d2a49f2c874c63fc01426ef1bbb65d838a3ba310c7b6f938fd4bf7b0707be8 not

Update 2
Another launch of the Node via CLI. First only 1 Node was found with blocks higher 597924.
Directly after connection with the 2nd peer having more blocks, an error marking block 597925 as invalid was given.
So, for me it looks like that my node is maybe loading two chains after block 597924 (hardfork) and don't know, which is the correct one.

[uzyn]

Can you post the output of defi-cli getblockchaininfo please?

[DanielZirkel]

Can you post the output of defi-cli getblockchaininfo please?

Here are the wanted results


The node was running the whole time. If the second command should be executed without running it, please let me know.

[Jacobsieler8888]

DOES ANYONE KNOW OF A FIX FOR THIS PROBLEM YET??

[monstrobishi]

Hi @DanielZirkel I'm adding a checkpoint for this block to the next build it may help with this issue

[madeinusmate]

@uzyn

defi-app_v2.1.6
defi-cli getblockchaininfo
{
"chain": "main",
"blocks": 597924,
"headers": 597924,
"bestblockhash": "e229dfaec32944b3f476da1f1981a3ccc650619e4ff7f38823d5ed68477564d2",
"difficulty": 216379423.5508064,
"mediantime": 1611581057,
"verificationprogress": 1,
"initialblockdownload": false,
"chainwork": "00000000000000000000000000000000000000000000ab3aab5e823f18120bcd",
"size_on_disk": 574744815,
"pruned": false,
"softforks": {
"bip34": {
"type": "buried",
"active": true,
"height": 0
},
"bip66": {
"type": "buried",
"active": true,
"height": 0
},
"bip65": {
"type": "buried",
"active": true,
"height": 0
},
"csv": {
"type": "buried",
"active": true,
"height": 1
},
"segwit": {
"type": "buried",
"active": true,
"height": 0
},
"amk": {
"type": "buried",
"active": true,
"height": 356500
},
"bayfront": {
"type": "buried",
"active": true,
"height": 405000
}
},
"warnings": ""
}

[Jacobsieler8888]

WHAT DOES THAT MEAN?

[monstrobishi]

@madeinusmate you must be on app version minimum 2.1.9 to sync with blockchain, that's unrelated to this issue thanks

[Jacobsieler8888]

Does anyone know how to fix this problem yet?

[madeinusmate]

@madeinusmate you must be on app version minimum 2.1.9 to sync with blockchain, that's unrelated to this issue thanks

tested on multiple releases.
2.1.6 was the most recent release that allowed to provide liquidity without "() recipient address..." error.

here you go with 2.1.12

defi-app_v2.1.12
defi-cli getblockchaininfo
{
"chain": "main",
"blocks": 597924,
"headers": 597924,
"bestblockhash": "e229dfaec32944b3f476da1f1981a3ccc650619e4ff7f38823d5ed68477564d2",
"difficulty": 216379423.5508064,
"mediantime": 1611581057,
"verificationprogress": 0.9901780275247484,
"initialblockdownload": false,
"chainwork": "00000000000000000000000000000000000000000000ab3aab5e823f18120bcd",
"size_on_disk": 574744815,
"pruned": false,
"softforks": {
"bip34": {
"type": "buried",
"active": true,
"height": 0
},
"bip66": {
"type": "buried",
"active": true,
"height": 0
},
"bip65": {
"type": "buried",
"active": true,
"height": 0
},
"csv": {
"type": "buried",
"active": true,
"height": 1
},
"segwit": {
"type": "buried",
"active": true,
"height": 0
},
"amk": {
"type": "buried",
"active": true,
"height": 356500
},
"bayfront": {
"type": "buried",
"active": true,
"height": 405000
},
"clarkequay": {
"type": "buried",
"active": true,
"height": 595738
}
},
"warnings": ""
}

[Jacobsieler8888]

@madeinusmate what do you mean when you said "here you go with 2.1.12"? Is that a fix to the issue?

[monstrobishi]

@Jacobsieler8888 he's saying he's also stuck on 2.1.12, he is a user like you, we will be releasing 2.1.13 today which should hopefully fix this issue.

[Jacobsieler8888]

okay. Do you know what time today 2.1.13 will be released?

[monstrobishi]

Within the next 3-4 hours

[Jacobsieler8888]

Okay. Thank you very much for your help.

[domo88]

worked for me after: Settings -> Reindex-Option. Now fully synced with 2.1.12 on W10.

[monstrobishi]

For those facing the issue, are you able to try with this pre-release build? we would like to confirm before making the release official: Download v2.1.13 here

Note that our testers and developers are not facing the issue hence we cannot 100% test if it is resolved ourselves., so would like users that are facing the issue to try it.

[izzycsy]

Hi @Anlien75 @cRuuZaR @domo88 @Jacobsieler8888 @DanielZirkel @madeinusmate do give a thumbs up to this comment if your issue has been resolved, otherwise, provide new information (include screenshots) and app logs. Thank you.

[cRuuZaR]

I have downloaded and install this version and it works fine... but before
I have done a resync under Settings with the 2.1.12 version ;-)

Am Di., 26. Jan. 2021 um 14:29 Uhr schrieb Bella [e-mail]:

Hi @Anlien75 https://github.com/Anlien75 @cRuuZaR
https://github.com/cRuuZaR @domo88 https://github.com/domo88
@Jacobsieler8888 https://github.com/Jacobsieler8888 @DanielZirkel
https://github.com/DanielZirkel @madeinusmate
https://github.com/madeinusmate do give a thumbs up to this comment if
your issue has been resolved, otherwise, provide new information (include
screenshots) and app logs. Thank you.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DeFiCh/app/issues/381#issuecomment-767541121, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASPLZWMZI2R6J42PO3N5F3LS327TVANCNFSM4WSG4HEQ
.

[DanielZirkel]

Version 2.1.13 was working in my case, but I need a complete new reindex.
Just installing could not solve the issue

[Jacobsieler8888]

How do you reindex DanielZirkel?

[Jacobsieler8888]

https://github.com/DanielZirkel, how do you reindex?

[monstrobishi]

@Jacobsieler8888 you can go to Settings -> Reindex after saving -> Save

[Jacobsieler8888]

Thank you!

[Anlien75]

My system is dead. Nothing works anymore.

Reindex is not possible. Uninstalling and reinstalling from .12 to .13 does nothing.

[Jacobsieler8888]

I installed version 2.1.13 and it stopped syncing at block 597952 again so I reindexed after saving and it froze as well. It says "restarting node. this may take a few minutes". but it's been about 30 minutes and it's still trying to restart node. Please help!

[monstrobishi]

Yes this can happen you can restart your computer to clear any stuck process and then try reindex again

[Jacobsieler8888]

Okay, but now I tried to close the app to restart my computer and it says "Quitting

Defi chain app. do not turn off computer while this window is open". What should I do????

[monstrobishi]

Under normal circumstances you should not but because it seems stuck for a long time go ahead and restart. Don't worry this warning is just to save you the trouble of having to reindex but in this case you want to reindex anyway so you can ignore it and restart.

[Jacobsieler8888]

okay. will do. thank you

[Jacobsieler8888]

Now I got this message when trying to open defi app after restarting my computer.

[Jacobsieler8888]

and it still will not reindex. It says it is restarting node again and it will not restart, just like the last picture

[cherryactiveo2]

Got also the same problem @monstrobishi
Edit: work now! thx

[Jacobsieler8888]

IT'S WORKING NOW! THANK YOU EVERYONE!

[Christian-vfx]

I had exactly the same issues.
After the same steps as Jacobsieler8888, it worked for me as well.
Now I can sleep again. Thanks for your support!

[madeinusmate]

Hi @Anlien75 @cRuuZaR @domo88 @Jacobsieler8888 @DanielZirkel @madeinusmate do give a thumbs up to this comment if your issue has been resolved, otherwise, provide new information (include screenshots) and app logs. Thank you.

Different error for me "node disconnected" + notification saying: "Pending Balance Failure - network error"
Tried both updating the existing installation and with a fresh one.

[madeinusmate]

problem solved with a restart and fresh install.
the issue "node is disconnected" was due to no more free space on my hard drive to store the blocks.

EDIT: is it normal the blocks are taking 9GBs of space?

[izzycsy]

Hi @madeinusmate , for hard disk space yes.

Thanks all for your reply, should the the same error occur, you may reopen this issue with new information (include screenshots) and app logs. Thank you.

[Christian-vfx]

After closing and restarting the app I had again damaged blocks.
Now the app is syncronizing again.

[uzyn]

Block corruption is an unrelated issue.

That happens locally when your memory is filled up and it doesn't have the buffer to dump to disk before OS kills the process. Try to increase the memory/swap allocation.

[Christian-vfx]

I have 32GB RAM. When syncing DeFi app goes up to 10GB.
After sync, right now only 177MB.
I used the workaround to “stop” via console and then kill the process via Task Manger. Then I can start the app without error message and full sync.