ArmoryDB is running by itself on its own headless host.
Restarting the ArmoryDB service runs just fine, the last dbLog.txt entries are:
-WARN - 16:13:54: (BDM_supportClasses.cpp:1944) running 35 zc parser threads
-INFO - 16:21:05: (BlockchainScanner.cpp:857) scanned block #518330
-INFO - 16:21:26: (BlockchainScanner.cpp:857) scanned block #518331
Starting ArmoryQt on a remote machine:
(again, dbLog.txt)
-INFO - 16:28:37: (BDM_Server.cpp:1121) registered bdv: a*****0
-INFO - 16:28:38: (BDM_supportClasses.cpp:401) Starting address registration process
-INFO - 16:28:43: (BlockchainScanner.cpp:852) scanned from block #0 to #142691
[..]
and then, finally:
-INFO - 17:11:48: (BlockchainScanner.cpp:852) scanned from block #514744 to #515526
As the last line, from then on ArmoryDB hangs.
ArmoryQt says:
(INFO) ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
-ERROR - : (BinaryData.h:563) odd hexit count
(scanning comes a few hundred times, then the hexit error several times a second)
Ente