There is an update. I think either some corruption of the database or a bug in the build.
I gave another try. This time I did not start bitcoind, and I also closed all other applications running. So I run ArmoryDB (with no options) and on the terminal I see this:
gaglia@myhost:~$ ArmoryDB
/home/gaglia
/home/gaglia
logging in /home/gaglia/.armory/dbLog.txt
-INFO - 13:52:35: (main.cpp:32) Running on 4 threads
-INFO - 13:52:35: (main.cpp:33) Ram usage level: 4
-INFO - 13:52:35: (BlockUtils.cpp:908) blkfile dir: /home/gaglia/.bitcoin/blocks
-INFO - 13:52:35: (BlockUtils.cpp:909) lmdb dir: /home/gaglia/.armory/databases
-INFO - 13:52:35: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 13:52:36: (BDM_Server.h:249) Listening on port 9001
-INFO - 13:52:36: (BlockUtils.cpp:1092) Executing: doInitialSyncOnLoad
-INFO - 13:52:36: (DatabaseBuilder.cpp:190) Reading headers from db
-INFO - 13:53:07: (DatabaseBuilder.cpp:229) Found 474952 headers in db
-INFO - 13:53:09: (DatabaseBuilder.cpp:63) Rewinding 100 blocks
-INFO - 13:53:09: (DatabaseBuilder.cpp:70) updating HEADERS db
-INFO - 13:53:14: (DatabaseBuilder.cpp:482) Found next block after skipping 998187bytes
-INFO - 13:53:17: (DatabaseBuilder.cpp:272) parsed block file #888
-INFO - 13:53:17: (Blockchain.cpp:246) Organizing chain
-INFO - 13:53:18: (Blockchain.cpp:360) Organized chain in 0.033253s
-INFO - 13:53:18: (DatabaseBuilder.cpp:75) updated HEADERS db in 1.04113s
-INFO - 13:53:18: (DatabaseBuilder.cpp:1121) verifying txfilters integrity
-INFO - 13:54:06: (DatabaseBuilder.cpp:1205) done checking txfilters
-INFO - 13:54:06: (BDM_supportClasses.cpp:1873) Enabling zero-conf tracking
At that point I start armory (again, with no bitcoind), and after some time I see that it connects to ArmoryDB, which starts scanning blocks until after a few minutes it crashes with an error:
-INFO - 13:56:06: (BDM_Server.cpp:1074) registered bdv: de33372f76586bce256e
-INFO - 13:56:07: (BDM_supportClasses.cpp:378) Starting address registration process
-INFO - 14:03:23: (BlockchainScanner.cpp:665) scanned from height #0 to #223709
-INFO - 14:03:33: (BlockchainScanner.cpp:665) scanned from height #223710 to #227221
-INFO - 14:03:41: (BlockchainScanner.cpp:665) scanned from height #227222 to #230415
-INFO - 14:03:48: (BlockchainScanner.cpp:665) scanned from height #230416 to #233652
...
...
...
-INFO - 14:33:29: (BlockchainScanner.cpp:665) scanned from height #473510 to #474154
-INFO - 14:33:38: (BlockchainScanner.cpp:665) scanned from height #474155 to #474726
-ERROR - 14:33:38: (BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 14:33:38: (BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 14:33:38: (BlockchainScanner.cpp:271) raw data does not match expected block hash
terminate called recursively
Aborted
gaglia@myhost:~$
When this happens, the Armory window is at 99% of "Scanning Transaction History". At the same time, the armory terminal window shows this:
gaglia@myhost:~$ armory
Gtk-Message: Failed to load module "canberra-gtk-module"
/home/gaglia
(ERROR) ArmoryUtils.py:3747 - Unsupported language specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(ERROR) ArmoryQt.py:1194 - 3 attempts to load blockchain failed. Remove mempool.bin.
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
-ERROR - 14:33:38: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
What I tried to do at this point is, instead of closing armory, I left the wondow open and tried to run again ArmoryDB, but then armory crashes:
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
-ERROR - 14:33:38: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
terminate called after throwing an instance of 'DbErrorMsg'
Aborted
gaglia@myhost:~$
Any idea? I'd rather prefer to not build my own armory if not strictly necessary.
But is it just me? I can't believe I'm having this weird errors, I don't have any strange configuration, I'm just trying to run "normally" armory on Debian... is it such an unpopular thing?
