Stuck on "Initializing bitcoin engine" forever

[TheNerd]

I'm with Armory 0.95.1-beta and bitcoin-0.11.1 on Ubuntu 16.10
When I start Armory, it starts bitcoind as well but it closes shortly after. So it's stuck at "Initializing bitcoin engine" forever

Sometimes after couple of runs it goes beyond that and hangs all day on syncrhonizing with network, but it's just few days behind so couldn't be taking whole day for sure.

So basically I can't access my money again.

[1714102763]

1714102763

[1714102763]

1714102763

[achow101]

In Armory, uncheck the "Let Armory run Bitcoin Core in the background" Checkbox. Stop Armory. Start Bitcoin Core. Let Bitcoin Core sync. Then start Armory again.

[TheNerd]

When starting bitcoin-qt it said corrupted database block detected and started reindexing blocks from the beginning which last time took couple of days.
This is like the 3rd time this happens (second in a month)

Is there particular reason this happens so often?



p.s.
thank you for the help!

[goatpig]

If you don't shut down Core gracefully, the leveldb database may get corrupted. Your best bet is to manually control BitcoinQt to make sure it is shut down properly (that the shut down period is respected).

[TheNerd]

I see. More often than not Armory freezes when quitting on Ubuntu and I have to kill it.

[TheNerd]

I just spent 3+ days rebuilding the whole database with bitcoin-qt and when finally started armory the dblog ends with

-INFO  - 1492548099: (DatabaseBuilder.cpp:56) updated HEADERS db in 68.9895s
-INFO  - 1492548099: (DatabaseBuilder.cpp:106) scanning new blocks from #457820 to #459045
-ERROR - 1492548100: (BlockchainScanner.cpp:271) raw data does not match expected block hash

how many block files I have to delete?
Can't afford to wait another 3+ days to rebuild.

[goatpig]

You should just rebuild & rescan here. Don't delete blocks files just yet.

[TheNerd]

That didn't help, so i went the starting bitcoin-qt route so it rebuilds everything.
After it did that for 3+ days armory still hangs on scanning transaction history and bad block hash

[goatpig]

Delete your databases folder. Start ArmoryDB from the command line with the following:

Code:

ArmoryDB --db-type=DB_BARE

Once, it's done building, you can shutdown the DB and start the client as usual.

[TheNerd]

Thank you! I did it, it's now stuck at:

-INFO  - 1492718365: (DatabaseBuilder.cpp:268) parsed block file #837
-INFO  - 1492718368: (DatabaseBuilder.cpp:268) parsed block file #841
-DEBUG - 1492718393: (Blockchain.cpp:242) Organizing chain
-INFO  - 1492718401: (DatabaseBuilder.cpp:56) updated HEADERS db in 2358.24s
-INFO  - 1492718403: (BlockUtils.cpp:1636) Enabling zero-conf tracking

[goatpig]

That's not stuck, that's how far the DB can get without wallets registered. Now start ArmoryQt to get to the next step.

[TheNerd]

aha thanks!
Now stuck at initializing bitcoin engine. bitcoind is running and at 40% cpu usage.
uh

[goatpig]

Don't run auto bitcoind if your setup isn't stable. Run BitcoinQt and make sure it's sync'd before running anything else. The fact that it's eating 40% CPU implies it's not done syncing.

[bitminerinthecloud]

In Armory, uncheck the "Let Armory run Bitcoin Core in the background" Checkbox. Stop Armory. Start Bitcoin Core. Let Bitcoin Core sync. Then start Armory again.

Let me get this straight: "Let Bitcoin Core sync." - Start syncing or finish syncing?

[achow101]

In Armory, uncheck the "Let Armory run Bitcoin Core in the background" Checkbox. Stop Armory. Start Bitcoin Core. Let Bitcoin Core sync. Then start Armory again.

Let me get this straight: "Let Bitcoin Core sync." - Start syncing or finish syncing?

Finish syncing.