Topic: Armory 0.96.3 released - page 8. (Read 15542 times)

I have completely deleted the blockchain, let 14.0.2 redownload all of it which took over a day, let ArmoryDB rebuild its database, and when I launch Qt I get the Same Old issue. Yes I am on 0.96.3 now, and nothing's changed. Really, bitcoind seems to be behaving fine, and ADB is also building up its database normally, I'd wager the issue is with Qt.

EDIT:

I went ahead and I moved the wallets away from ArmoryQt's folder, and deleted the settings file. Started fresh with a new wallet. The issue remains UNCHANGED.

When not using any wallet, the Qt shows Connected and correct number of blocks loaded, and keeps up to date. The problem always seems to appear when having to do anything with scanning transaction history, which never goes ahead. Qt will also close normally when there is no history to scan, as opposed to when there is, in which case it will seem to operate normally right up to being Quit, at which point it will freeze up and require forced termination.

Rechap:

Core 0.14.0.2 - fresh everything - 1.5 days old (I even deleted peers.dat, banlist.dat etc.)
ArmoryDB - fresh everything(including old files deleted and replaced before this update) - few hours old
Qt - same as DB, with fresh config as of - 30min ago



EDIT2:

I updated Core to 1.15.0.1. No dice. So what I have is, whenever Qt launches and connects to ArmoryDB, ADB's log gets this:


Nothing more follows. From what I see it's supposed to start showing "Scanned from height #" events as it processes the blockchain. It does not proceed. Yet the blockchain is loaded properly enough to actually exist in bitcoind, up to date, and with no errors reported by it. The blockchain is also loaded properly enough by DB to build its database out of it. Then when Qt wants to scan an address, suddenly it cannot load it?

bitcoind - all ok, downloaded blockchain up to date, maintaining it, no errors in log
armorydb - all ok, log shows loading all blk files up to date, no errors reported
amroryqt - requests history for wallet, armorydb chokes on the request, qt cannot find/load blockchain - SAME WITH FRESH CONFIG AND NEW EMPTY CLEAN WALLET

What gives?

Yes, it does fix that problem, hence that one line under "== Fixed =="

FYI, this version of Armory is the last one built to run on OS X 10.7. Starting with 0.96.4, you'll have to roll your own version if you insist on running Armory on 10.7. Long & technical story short, Armory uses code that can have issues on 10.7. Supporting 10.7 made it more difficult for people on more recent versions to compile the code. So, 10.7 is out the door.

Also, goatpig didn't explicitly mention this but I believe this will fix the issues people were seeing when they ran Core 0.15.0.1 (i.e., the ones where goatpig told them to go back to 0.15). If you're still having issues, post your logs!

Thanks.

Notes

This is a point release to fix a vulnerability with fragmented backups. If you are using fragmented backups on for your wallets, read the dedicated topic:

https://bitcointalksearch.org/topic/fragmented-backups-vulnerability-if-you-use-them-read-this-2199659

Binaries

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3

Changelog