Quote from: Carlton Banks on May 16, 2023, 10:33:29 PM

I tried getting Armory 96.5 working on my Qubes 4.1 machine (4.0 is really not supported any more), and all was well until this last part

compiling was really the same as 94-96.x, using debian 10/buster toolchain, no issues

dbLog.txt:

Code:

-INFO - 18:09:08: (BlockUtils.cpp:915) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 18:09:08: (BlockUtils.cpp:916) lmdb dir: /home/user/.armory/databases
-INFO - 18:09:08: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 18:09:08: (BDM_Server.h:263) Listening on port 63221
-INFO - 18:09:08: (nodeRPC.cpp:57) RPC connection established
-INFO - 18:09:08: (BlockDataManagerConfig.cpp:919) waiting on node sync: 99.9997%
-INFO - 18:09:08: (nodeRPC.cpp:425) Node is ready
-INFO - 18:09:08: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO - 18:09:08: (BDM_Server.cpp:1121) registered bdv: 4a80c146a3552190f2b4
-INFO - 18:09:08: (DatabaseBuilder.cpp:199) Reading headers from db
-INFO - 18:09:25: (DatabaseBuilder.cpp:238) Found 723305 headers in db
-INFO - 18:09:33: (DatabaseBuilder.cpp:64) Rewinding 100 blocks
-INFO - 18:09:33: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO - 18:09:33: (DatabaseBuilder.cpp:493) Found next block after skipping 1660080bytes
...
-INFO - 18:09:35: (DatabaseBuilder.cpp:281) parsed block file #3599
-INFO - 17:53:09: (DatabaseBuilder.cpp:281) parsed block file #3600
-INFO - 17:53:11: (Blockchain.cpp:248) Organizing chain
-INFO - 17:53:18: (Blockchain.cpp:370) Organized chain in 6s
-INFO - 17:53:24: (DatabaseBuilder.cpp:76) updated HEADERS db in 908s
-INFO - 17:53:25: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 17:53:25: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO - 17:54:06: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO - 17:54:07: (DatabaseBuilder.cpp:134) scanning new blocks from #723305 to #790065
...
-INFO - 18:06:46: (BlockchainScanner.cpp:852) scanned from block #789756 to #790065
-INFO - 18:06:46: (BlockchainScanner.cpp:214) scanned transaction history in 759s
-INFO - 18:06:47: (BlockchainScanner.cpp:1789) resolving txhashes
-INFO - 18:06:47: (BlockchainScanner.cpp:1848) 0 blocks hit by tx filters
-INFO - 18:06:47: (BlockchainScanner.cpp:1937) found 0 missing hashes
-INFO - 18:06:47: (BlockchainScanner.cpp:1982) Resolved missing hashes in 0s
-INFO - 18:06:47: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 18:06:47: (DatabaseBuilder.cpp:186) scanned new blocks in 760s
-INFO - 18:06:47: (DatabaseBuilder.cpp:190) init db in 1726s
-INFO - 18:06:47: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking
-INFO - 18:06:53: (BlockchainScanner.cpp:857) scanned block #790066
-ERROR - 18:10:17: (lmdb_wrapper.cpp:2086) BLKDATA DB does not have the requested ZC tx
-ERROR - 18:10:17: (lmdb_wrapper.cpp:2087) (scrubbed_but_valid_hexdata)
-WARN - 18:10:17: (LedgerEntry.cpp:334) failed to get tx for ledger parsing

subsequently, ArmoryDB only seems to perform "Wallet Properties" callbacks, most everything else produces errors in the qt log

the ERROR line from lmdb_wrapper.cpp repeats dozens of times. And the gui reports "node offline"

It seems that you are encountering an issue with Armory 0.96.5 where the BLKDATA DB does not have the requested ZC (Zero-Confirmation) transaction. This error message suggests that there might be a problem with the blockchain data stored in the database.

Verify blockchain data: Double-check if your blockchain data is complete and up-to-date.
Rebuild databases: You can try rebuilding the Armory databases to ensure they are in a consistent state. This process will involve reindexing the blockchain data. In Armory, go to "File" > "Rebuild Databases" and follow the prompts.
Check disk space and permissions: Ensure that you have enough disk space available for Armory to operate properly. Additionally, verify that the user running Armory has the necessary read and write permissions to access the Armory and Bitcoin data directories.
Update Armory: Consider updating to the latest version of Armory, as newer releases often include bug fixes and improvements.

Let me know how it goes.