search

muecoin / MUE

MUE2.0
https://MonetaryUnit.org
MIT License
10 stars 13 forks source link

2.1.1 Pre-Release on RPI fails to sync blockchain #7

Closed c44c closed 5 years ago

c44c commented 5 years ago

Describe the issue

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

  1. Install the 2.1.1 daemon and qt-client on a r-pi/raspbian system
  2. Run the MUE QT-wallet
  3. Chain gets stuck on block #140905. After closing the wallet, any attempt to use -reindex, -rescan or simply restart the wallet gives a seg fault.

Expected behavior

Tell us what should happen

  1. The 2.1.1 wallet gets stuck on block 140905, while the 2.0.2 wallet does not.

Actual behavior

Tell us what happens instead

Screenshots.

If the issue is related to the GUI, screenshots can be added to this issue via drag & drop. screenshot from 2018-12-13 13-06-51

What version of MonetaryUnit Core are you using?

https://github.com/muecoin/MUE/releases/download/v2.1.1/mon-2.1.1-arm-linux-gnueabihf.tar.gz

Machine specs:

Any extra information that might be useful in the debugging process.

After crashing / seg fault, removal of the blockchain and chainstate data allows the QT wallet to start again, and re-download the blockchain again, and then again get stuck on block #140905.

c44c commented 5 years ago

screenshot from 2018-12-14 23-09-44

Restarted the wallet again: The client is banning all other peers thus not progressing with the sync of the blockchain. Tested unbanning and cleaning the banned list, however all connected peers get added to the banlist again.

tohsnoom commented 5 years ago

Can you possibly give me the block hash of the latest block it has loaded?

Also, have you tried deleting the local blockchain folders (blocks, chainstate, sporks) and letting it sync again?

Also, would you be able to share the log file from around the time it loaded that block onward, so I can see any error messages or other information that may help diagnose the issue?

c44c commented 5 years ago

image updated 2.1.2 fixed the issues with an error with checkpoint lock-in at 140906 :+1: This issue can be closed now