Raspiblitz: error code: -28 error message: Loading block index...

Created on 19 Aug 2020  路  10Comments  路  Source: rootzoll/raspiblitz

I get this on every reboot and and I've seen a number of other people get this on 1.6. Seems like it is giving up to early or something, doesn't give enough time to let the block index load.

*****************************************
* The bitcoind service is not running.
*****************************************
If you just started some config/setup, this might be OK.

More Error Detail:
error code: -28 error message: Loading block index...

POSSIBLE OPTIONS:
-> Use command 'repair' and then choose 'DELETE-INDEX' to try rebuilding transaction index.
-> Use command 'repair' and then choose 'RESET-CHAIN' to try downloading new blockchain.
-> Use command 'debug' for more log output you can use for getting support.
-> Use command 'menu' to open main menu.
-> Have you tried to turn it off and on again? Use command 'restart'

bitcoin error: error code: -28
error message:
Loading block index...

Most helpful comment

I figured out a workaround if you type menu in the Commandline then select Info from the menu options it will ask you to type in your LND password and then the load index window will appear letting you know what percentage your Blockchain Index and LND index is at.

All 10 comments

hey i get this too after power off and on. last reboot it worked. Everytime if that happens, i have to update public ip manually with the dynupdate url

Just got this error with a completely fresh SD.

run, sudo tail -n 20 /mnt/hdd/bitcoin/debug.log

See if it is slowly verifying the blocks or downloading blocks. Once the chain is sync'd then you can run , raspiblitz to launch the menu and go back through the normal loading without a reboot.

I also find running the lnd wallet unlock to help with the command, lncli unlock

I had some teething problems with 1.6, and decided to blow away the chain data. Which was probably an over-reaction, as once I had finally copied it over I still got the above errors, and it was caused by the the slow verification of blocks or need to download the last few remaining blocks while the node had been offline. You can check all this in the /bitcoin/debug.log

so its just a race condition between the bitcoind and lnd. Wait for start lnd while bitcoind is syncing. Not that easy for a script to get that state i think, if it depends a lot on sync time... can be seconds, days or weeks. At setup from scratch that all worked well.

Further in my cases there was no need to interact... the LND waits in a suspend state or something as i observed. So only wait for the bitcoind sync progress. that could be visualized a bit more

This seems to be a timing issue .. marked for v1.6.1 to change timing on this.

I figured out a workaround if you type menu in the Commandline then select Info from the menu options it will ask you to type in your LND password and then the load index window will appear letting you know what percentage your Blockchain Index and LND index is at.

merged the fix by @CandleHater - putting it on final testing

original fix by @CandleHater tested good .. rolling with that.

Tested for some weeks now ... looks good. Will be part of v1.6.1. Closing this issue.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ChuckNorrison picture ChuckNorrison  路  4Comments

pkclyoni picture pkclyoni  路  3Comments

2000jago picture 2000jago  路  5Comments

philbertw4 picture philbertw4  路  5Comments

shawnyeager picture shawnyeager  路  3Comments