BDM thread failed

[Jay.C.]

Hello, I'm not one to join forums or ask people for help, but here I am hat in hand.  I'll get right to it.

I've been using Armory for about 2 years now.  About 2 weeks ago I woke up, turned on my PC, fired up armory and within a couple minutes received an "armory needs to shut down" message underneath a message that says:

"BDM thread failed: The scanning process interrupted unexpectedly, Armory will now shutdown. If the error persists, you will have to rebuild and rescan your database. If rebuilding and rescaning did not fix the issue, contact support. Refer to your log file for more details on the error."

I've had DB issues before with core that I've been able to resolve, but this was new.  Note that I was running an outdated version of core and Armory 93.3 up until now.  Core is running fine, and there are no missing blocks that I can discern.  Core's error logs are clean.  However, here is the pertinent part of the armorycpplog:

-WARN  - 1504323063: (..\BlockWriteBatcher.cpp:1133) Finished applying blocks up to 477500
-WARN  - 1504323265: (..\BlockWriteBatcher.cpp:1133) Finished applying blocks up to 480000
-ERROR - 1504323416: (..\BlockWriteBatcher.cpp:980) No block in DB at height 481824
-INFO  - 1504323418: (..\BlockUtils.cpp:1518) Scanned Block range in 29035s
-INFO  - 1504323418: (..\BlockUtils.cpp:1521) Finished loading at file 985, offset 6002112
-INFO  - 1504323418: (..\BlockDataViewer.cpp:157) Enabling zero-conf tracking
-ERROR - 1504323421: (..\BDM_mainthread.cpp:429) BDM thread failed: The scanning process interrupted unexpectedly, Armory will now shutdown. If the error persists, you will have to rebuild and rescan your database. If rebuilding and rescaning did not fix the issue, contact support. Refer to your log file for more details on the error.

Clearly Armory does not like block 481824 for some reason.  Below I will go over what I've done thus far.  That block number has changed during some of these attempts to fix, however it's been that number the most, and it's currently that number again after a complete reset.

Here's what's transpired since:

1) I simply restarted Armory.  Same issue, not a fluke.
2) I click the 'rebuild and rescan DB on next start up'.  Waited for Armory to do it's thing.  Same issue.
3) I deleted the 'database' folder from the Armory directory.  Same issue.
3a) I used a backup of bitcoin core from July 19th to reload recent blocks as block 481824 was on Aug 24th.  Same issue. 
4) I -reindex'd bitcoin core.  (3 days later) Same issue.
5) I -rescan'd bitcoin core.  Same issue.
6) I deleted and reinstalled all my wallets multiple times.  No help.
7) I downloaded and installed Armory 96.1.  No change, except the error logs provide a LOT less information :/... Namely, it only provides the following:

Log file opened at 15:22:54.000: A:\Armory\Data\armorycpplog.txt
-ERROR - 15:59:41.203: (..\SocketObject.cpp:447) POLLERR error in readAndWrite
-ERROR - 15:59:41.469: (..\StringSockets.cpp:359) POLLERR error in readAndWrite

8. I deleted bitcoin core and downloaded the newest version.  (3 days later - today) Same issue.  Same block number - 481824.  This block number exists in core with no issue.

2017-09-01 10:10:42 UpdateTip: new best=000000000000000000cbeff0b533f8e1189cf09dfbebf57a8ebe349362811b80 height=481823 version=0x20000002 log2_work=86.98539 tx=249036369 date='2017-08-24 01:52:51' progress=0.990820 cache=199.4MiB(173876tx)
2017-09-01 10:10:43 UpdateTip: new best=0000000000000000001c8018d9cb3b742ef25114f27563e3fc4a1902167f9893 height=481824 version=0x20000002 log2_work=86.985426 tx=249038235 date='2017-08-24 01:57:37' progress=0.990823 cache=203.4MiB(177815tx)
2017-09-01 10:10:44 Pre-allocating up to position 0x1100000 in rev00975.dat
2017-09-01 10:10:44 UpdateTip: new best=000000000000000000daf7a26d903543377d5cdddb962077e58fd11212479eea height=481825 version=0x20000000 log2_work=86.985462 tx=249040201 date='2017-08-24 02:26:36' progress=0.990845 cache=204.3MiB(180318tx)
2017-09-01 10:10:46 Pre-allocating up to position 0x700000 in rev00976.dat

Nothing logically makes any sense.  The error will occur in 1 of 2 places: 1) at about 1 or 2% of importing one of my wallets (with 93.3, with 96.1 it goes all the way to 99% before erroring out), or 2) if the wallet is already in the system, it will get to the end of the 'scanning transactions' phase of boot up and then throw the exception. 

Could a wallet file be corrupted?  I have four wallets on the system.  I tried to send funds from one wallet to the other wallet and added a small fee of .0005.  I didn't mind waiting a few days for it to go through.  However, when this error first started happening I could see behind the error pop-ups the list of my transactions.  The one at the top (the last one) was this transaction between the two wallets still with 0 confirmations, with no other transactions after it (and I KNOW there were transactions after it).  However, even when I try to import one of the other wallets that wasn't involved with this transaction to a fresh install of Armory I still get the same error.

I haven't tried 96.1 with the new version of core yet.  I'll download 96.2 and do that now, but I absolutely do not expect any different results.  I'm honestly not even sure what anyone can advise me to do at this point if a clean install of both programs doesn't resolve the issue. 

If it matters, these are watching-only wallets.  I use full cold storage implementation.  That said, when I go to my offline wallets to get the private keys, to put into Electrum as a last ditch effort to recover my funds, it doesn't have any.  How screwed am I?  Thanks for anyone's time who contributes, sorry for the long read.

[1714156262]

1714156262

[1714156262]

1714156262

[achow101]

Please post all of your log files. Also, upgrading from 0.93.3 to any newer version requires Armory to built a new database. You will need to delete the databases folder in the Armory datadir to allow it to do that.

[Jay.C.]

Hello, and thank you for taking the time to assist.  When I 'upgrade' I always delete the old installation of armory and just install a fresh copy, so the databases folder is always updated.  So I've made some progress and was really hoping to report that things were okay, however they're not.  Here's what's happened since my first post:

1) Clean install of bitcoin core
2) Clean install of Armory 96.2
3) When I started Armory this time I chose to create a new wallet, just to see exactly where the issue begins.  I don't know if it was doing this, or just 96.2 (which wasn't available at the initial time of my crisis) that fixed the issue, but Armory finally loaded and synced with bitcoin core.
4) I then imported 1 of 4 wallets. In doing so the wallet would 'scan' as indicated in the top section, however when it would complete it would go back to '0%' and not show any transactions.  However, upon rebooting Armory viola!, my transactions were there finally!
5) I imported 2 of 4 wallets, and then 3 of 4 wallets, all with the same results as above.
6) I then went to import 4 of 4 wallets last night before I went to bed.  I woke up this morning with the same nagging results that started this mess. Mind you, this is the wallet that I sent FROM to one of my other Armory wallets prior to the crash.  This is the one I suspected had the issue.  It's my oldest wallet, and it has a sh!t ton of transactions in it.  I'm not sure what was wrong with this last transaction that would cause such a commotion. 

This is to say that when I went to import 4/4 it went through the 'scanning transactions' process up until 99% and then the ArmoryDB service just quits.  I reboot Armory and it goes to 'scanning transactions 0%' and ArmoryDB quits within seconds.  I get no warning or notices of this.  Armory sits and spins, I only know because I have task manager open.

Below are the pertinent logs.  The bitcoin core logs seem normal so I won't include, but if you need them let me know.

 armorycpplog********************

Log file opened at 07:01:33.000: A:\Armory\Data\armorycpplog.txt
-ERROR - 07:02:39.953: (..\SocketObject.cpp:447) POLLERR error in readAndWrite
-ERROR - 07:02:39.953: (..\StringSockets.cpp:359) POLLERR error in readAndWrite

armorylog************************

2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1270 - Loading Armory Engine:
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1271 -    Armory Version        : 0.96.2
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1272 -    Armory Build:         : 95dc55907f
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1273 -    PyBtcWallet  Version  : 1.35
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1274 - Detected Operating system: Windows
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1275 -    OS Variant            : 8-6.2.9200--Multiprocessor Free
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1276 -    User home-directory   : C:\Users\Claibourne\AppData\Roaming
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1277 -    Satoshi BTC directory : C:\Users\Claibourne\AppData\Roaming\Bitcoin
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1278 -    Armory home dir       : A:\Armory\Data
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1279 - Detected System Specs    :
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1280 -    Total Available RAM   : 7.86 GB
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1281 -    CPU ID string         : Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1282 -    Number of CPU cores   : 4 cores
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1283 -    System is 64-bit      : True
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1284 -    Preferred Encoding    : cp1252
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1285 -    Machine Arch          : amd64
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1286 -    Available HDD (ARM)   : 74 GB
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1287 -    Available HDD (BTC)   : 157 GB
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1288 -
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1289 - Network Name: Main Network
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1290 - Satoshi Port: 8333
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1291 - Do wlt check: True
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1292 - Named options/arguments to armoryengine.py:
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     thread_count    : -1
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     rescan          : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     ignoreAllZC     : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     rescanBalance   : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     disableModules  : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     port            : None
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     interport       : 8223
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     coverageOutputDir: None
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     forceWalletCheck: False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     regtest         : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     rebuild         : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     nettimeout      : 2
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     datadir         : A:\Armory\Data
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     clearMempool    : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     offline         : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     armoryDBDir     : DEFAULT
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     armorydb_port   : 9001
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     satoshiPort     : DEFAULT
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     useTorSettings  : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     netlog          : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     keypool         : 100
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     coverageInclude : None
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     forceOnline     : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     redownload      : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     rpcBindAddr     : 127.0.0.1
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     armorydb_ip     : 127.0.0.1
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     multisigFile    : DEFAULT
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     ram_usage       : -1
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     mtdebug         : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     logDisable      : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     settingsPath    : A:\Armory\Data\ArmorySettings.txt
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     language        : en
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     db_type         : DB_FULL
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     doDebug         : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     enableDetSign   : True
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     disableConfPermis: False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     testnet         : False
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     rpcport         : DEFAULT
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     satoshiHome     : DEFAULT
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     satoshiRpcport  : DEFAULT
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     logFile         : A:\Armory\Data\ArmoryQt.exe.log.txt
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1294 -     verbosity       : None
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1295 - Other arguments:
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1298 - ************************************************************
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:1701 - C++ block utilities loaded successfully
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: A:\Armory\Data\ArmorySettings.txt
2017-09-03 07:01:33 (ERROR) -- ArmoryUtils.pyc:3719 - Unsupported language  specified. Defaulting to English (en)
2017-09-03 07:01:33 (INFO) -- ArmoryUtils.pyc:3722 - Using Language: en
2017-09-03 07:01:33 (INFO) -- BDM.pyc:355 - Using the asynchronous/multi-threaded BlockDataManager.
2017-09-03 07:01:33 (INFO) -- BDM.pyc:356 - Blockchain operations will happen in the background. 
2017-09-03 07:01:33 (INFO) -- BDM.pyc:357 - Devs: check TheBDM.getState() before asking for data.
2017-09-03 07:01:33 (INFO) -- BDM.pyc:358 - Registering addresses during rescans will queue them for
2017-09-03 07:01:33 (INFO) -- BDM.pyc:359 - inclusion after the current scan is completed.
2017-09-03 07:01:34 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: A:\Armory\Data\ArmorySettings.txt
2017-09-03 07:01:35 (INFO) -- ArmoryQt.py:2061 - loadWalletsAndSettings
2017-09-03 07:01:35 (INFO) -- ArmoryQt.py:2121 - Loading wallets...
2017-09-03 07:01:37 (INFO) -- ArmoryQt.py:2186 - Number of wallets read in: 5
2017-09-03 07:01:37 (INFO) -- ArmoryQt.py:2191 -    Wallet (26L6brpKh):   "Offline Wallet 1 (Watch) (Watch)"   (No Encryption)
2017-09-03 07:01:37 (INFO) -- ArmoryQt.py:2191 -    Wallet (32uPYJ3J7):   "Offline Wallet 2 (Watch)        "   (No Encryption)
2017-09-03 07:01:37 (INFO) -- ArmoryQt.py:2191 -    Wallet (2fZP4hef1):   "Primary Wallet                  "   (Encrypted)
2017-09-03 07:01:37 (INFO) -- ArmoryQt.py:2191 -    Wallet (e5pFx8fH):    "Odd (Watch)                     "   (No Encryption)
2017-09-03 07:01:37 (INFO) -- ArmoryQt.py:2191 -    Wallet (2Q3YuJbXd):   "Even (Watch)                    "   (No Encryption)
2017-09-03 07:01:37 (INFO) -- ArmoryQt.py:2196 - Loading Multisig Lockboxes
2017-09-03 07:01:38 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2017-09-03 07:01:39 (INFO) -- ArmoryQt.py:1892 - Setting satoshi datadir = F:\Bitcoin
2017-09-03 07:01:39 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-09-03 07:01:39 (INFO) -- SDM.pyc:171 -    F:\Bitcoin\daemon\bitcoind.exe
2017-09-03 07:01:39 (INFO) -- SDM.pyc:173 - Using: F:\Bitcoin\daemon\bitcoind.exe
2017-09-03 07:01:39 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-09-03 07:01:39 (WARNING) -- SDM.pyc:439 - Spawning bitcoind with command: F:\Bitcoin\daemon\bitcoind.exe -datadir=F:\Bitcoin
2017-09-03 07:01:39 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: [u'F:\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=F:\\Bitcoin']
2017-09-03 07:01:39 (INFO) -- SDM.pyc:445 - PID of bitcoind: 11208
2017-09-03 07:01:39 (INFO) -- SDM.pyc:446 - PID of armory:   9664
2017-09-03 07:01:39 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: ['.\\guardian.exe', '9664', '11208']
2017-09-03 07:01:42 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2017-09-03 07:01:42 (INFO) -- ArmoryQt.py:1892 - Setting satoshi datadir = F:\Bitcoin
2017-09-03 07:01:42 (WARNING) -- SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="F:\Bitcoin\blocks" --datadir="A:\Armory\Data" --dbdir="A:\Armory\Data\databases"
2017-09-03 07:01:42 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="F:\\Bitcoin\\blocks"', '--datadir="A:\\Armory\\Data"', u'--dbdir="A:\\Armory\\Data\\databases"']
2017-09-03 07:01:44 (INFO) -- ArmoryQt.py:1824 - Connecting on port 50068
2017-09-03 07:01:44 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-09-03 07:01:44 (INFO) -- ArmoryQt.py:1906 - loadBlockchainIfNecessary
2017-09-03 07:01:44 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-09-03 07:01:44 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:01:44 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:21 (WARNING) -- ArmoryQt.py:4108 - Called updateSyncProgress while not sync'ing
2017-09-03 07:02:21 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:22 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:22 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:23 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:23 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:24 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:25 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:25 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:26 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:26 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:26 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:30 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:32 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:32 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-03 07:02:33 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode

dbLog*****************************************

Log file opened at 07:01:43.000: A:\Armory\Data/dbLog.txt
-INFO  - 07:01:43.000: (..\main.cpp:32) Running on 4 threads
-INFO  - 07:01:43.000: (..\main.cpp:33) Ram usage level: 4
-INFO  - 07:01:43.000: (..\BlockUtils.cpp:915) blkfile dir: F:\Bitcoin\blocks
-INFO  - 07:01:43.000: (..\BlockUtils.cpp:916) lmdb dir: A:\Armory\Data\databases
-INFO  - 07:01:43.000: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 07:01:43.016: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 50068
-INFO  - 07:01:44.157: (..\BDM_Server.cpp:1114) registered bdv: 01656d6fe6f26ba17758
-INFO  - 07:02:18.063: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 07:02:19.110: (..\nodeRPC.cpp:57) RPC connection established
-INFO  - 07:02:21.313: (..\nodeRPC.cpp:346) Node is ready
-INFO  - 07:02:21.313: (..\BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 07:02:21.360: (..\DatabaseBuilder.cpp:199) Reading headers from db
-INFO  - 07:02:26.672: (..\DatabaseBuilder.cpp:238) Found 483281 headers in db
-INFO  - 07:02:30.047: (..\DatabaseBuilder.cpp:64) Rewinding 100 blocks
-INFO  - 07:02:30.047: (..\DatabaseBuilder.cpp:71) updating HEADERS db
-INFO  - 07:02:30.078: (..\DatabaseBuilder.cpp:493) Found next block after skipping 1001540bytes
-INFO  - 07:02:32.735: (..\DatabaseBuilder.cpp:281) parsed block file #986
-INFO  - 07:02:32.735: (..\Blockchain.cpp:248) Organizing chain
-INFO  - 07:02:32.782: (..\Blockchain.cpp:370) Organized chain in 0s
-INFO  - 07:02:32.782: (..\DatabaseBuilder.cpp:76) updated HEADERS db in 1s
-INFO  - 07:02:32.969: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 07:02:32.969: (..\DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO  - 07:02:32.422: (..\DatabaseBuilder.cpp:1314) done checking txfilters
-INFO  - 07:02:33.032: (..\DatabaseBuilder.cpp:134) scanning new blocks from #482803 to #483281

This is where each log ends once the ArmoryDB service quits. 

[Jay.C.]

Note that even after removing the 'bad' wallet ArmoryDB service still quits within seconds of starting the transaction scan on subsequent reboots.  I'm back to square one.

[Jay.C.]

I'm only replying to this in the event someone else has this issue and wants to know the resolution.  As you can see the forum had no assistance in the matter. 

So what ended up happening is the following:

I installed a second version of Armory and created a new wallet.  I then imported my 4th wallet by itself and it worked.  I then rebuilt the DB for the other 3 wallets and they now seem operable for the time being.  I simply switch the folder names back and forth and only open one instance of Armory at a time to access all 4 wallets. 

So, I'm not sure if it's the creating of a new wallet on a clean install or something in the 96.2 code that "fixed" it.  I don't know what caused the issue so can't avoid it happening again in the future, I don't know what fixed the issue so if it does happen again it could take me just as long to fix (2 weeks), and currently my situation remains unstable and inconvenient at best.  With a lack of support and a platform that is seemingly on it's way out, I'll be spending the week moving all my stuff over to Trezor and Electrum.  It was a good run Armory, sorry to see you go downhill so fast :/...