Topic: Armory stuck on "Preparing Databases" (Read 531 times)

Hello again,

Because of the node offline and because bitcoin core was stuck on 3 days and didnt make any progress, I reinstalled bitcoin core. Because I didnt have enough space on my C: SSD I put it this time on my E: SSD. I directed the install location to Armory for it to start it in the background and put my Bitcoin Home Dir on: BitcoinQt -datadir="E:\blocks"   I tried it with only E:\blocks and so on but the site you send me said I had to use it with -datadir for custom path. Now nothing seems to work again, I dont know why which is why I hope to find some advice here.

Here is some Armory log I found, maybe it helps

-INFO  - 21:27:34.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 8 threads
-INFO  - 21:27:34.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 21:27:34.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: C:\Users\Asus\AppData\Roaming\Bitcoin\blocks\blocks
-INFO  - 21:27:34.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\Asus\AppData\Roaming\Armory\databases
-INFO  - 21:27:34.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 21:27:34.032: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 52178
-INFO  - 21:27:34.032: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 21:27:34.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 21:27:34.047: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 21:27:34.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 21:27:34.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #0
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 0s
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 21:27:34.063: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO  - 21:27:36.110: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: c2a1796c6d45fe084ffc
-INFO  - 21:27:36.157: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
-INFO  - 21:27:36.157: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:857) scanned block #0
-INFO  - 21:27:36.172: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:857) scanned block #0
-INFO  - 21:35:53.891: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1150) unregistered bdv: c2a1796c6d45fe084ffc
-INFO  - 21:35:53.891: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1061) proceeding to shutdown
-ERROR - 21:35:59.579: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:267) poll() error in readFromSocketThread: 10038
-ERROR - 21:35:59.579: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in readFromSocketThread: 10038
-INFO  - 21:36:05.094: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:969) Disconnected from Bitcoin node
-ERROR - 21:36:11.204: (e:\users\goat\code\armory3\cppforswig\bdm_mainthread.cpp:294) caught exception in main thread: terminate

The "3 days behind" message doesn't mean that it'll take 3 days to sync, it's just 3 days worth of blocks which usually sync within an hour in my machine.
I suspect that there's something wrong with your node.

Close everything, restart the PC (to make sure everything isn't running in the background) and then start Bitcoin Core to see if it'll continue from where it left.
Take note that Bitcoin Core's GUI might freeze while it's syncing but it's still active in the background,
closing it forcefully might corrupt your "txindex", "chain_index" or "blockchain".
If it's not frozen, you can close it safely.

After it fully sync, the close it and open Armory, let it manage Bitcoin Core (it'll launch bitcoind in the background).
If there's an issue, check you debug.log file for errors in Bitcoin Core's data directory to see why it's not progressing.

I did it like it was stated on that website you linked and now armory is online, but somehow bitcoin core is now loading nonstop and it says 3 days behind. I let it be for 5 but its not loading its calculating the progress und the time remaining is unknown. So now I can see armory that its online but in the right corner it says Node offline (0 blocks) probably because it cant connect if bitcoin core isnt synced and because it wont sync it will never connect.
and thanks for your help I wouldve probably given up if it werent for you thx.

Have you installed Bitcoin Core in a different directory as well as its data directory?

Because it seems like a pathing issue and bitcoind can't be launched either.
Refer to this guide to setup the correct path to your Bitcoin data/install directory: https://btcarmory.com/docs/pathing

Alternatively, you can set it all in the GUI in "File->Settings":
"Bitcoin Install Dir" should point to the directory where Bitcoin Core is installed.
"Bitcoin Home Dir" should point to your bitcoin data directory.

Hello,
I have the same Problem with it being Stuck on preparing Databases, which is why I looked it up and tried different things like putting the bitcoin home dir right and so on. I have bitcoin core and Armory both on the newest version and fully synced. In the log I saw that my path somehow doesnt gets recognized which is why I wanted to reach out for help.




some part of the log:

Well, I guess that's good news... would have been nice to try and figure out why it was not passing the correct datadir through to ArmoryDB... possibly just a weird settings glitch and once ArmoryDB ran once with the proper commandline, it fixed it?

Hopefully you don't have any more issues!

dblog.txt is empty. Armory seems to be straightened out now and is back online.

Thanks!

no obvious errors output then? Can you please post the output from "dbLog.txt"... as always, put it on pastebin.com and then post the unique pastebin URL here.

Here is what I entered and the response:
C:\Program Files (x86)\Armory>ArmoryDB.exe --cookie --satoshi-datadir="J:\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\Marty\AppData\Roaming\Armory" --dbdir="C:\Users\Marty\AppData\Roaming\Armory\databases"

logging in C:\Users\Marty\AppData\Roaming\Armory/dbLog.txt

and just sits there like that. What did I do, LOL?

That is outside the scope of this forum/thread. You'll need to go take that up with the Bitcoin Core team on their github issues register: https://github.com/bitcoin/bitcoin/issues

I've not seen/heard of Bitcoin Core automatically switching to pruned mode before... it usually requires that pruning be enabled at startup via .conf or shortcut/commandline or via the GUI setting.

Anyway, should be a relatively easy fix if you have a non-pruned copy of the blockchain, you'll just need to copy that over to your pruned node (making sure it's not still set to prune), then make sure it's all synced and Armory should work just fine again.

OK, well that explains it but why suddenly it switched to prune mode.
Ive never done that.
There is nothing in the .conf or that line in the core settings.
The startup link is the default
"C:\Program Files\Bitcoin\bitcoin-qt.exe"
Ive used this program at least 5 years and know tricks to keep it working
but this has NEVER happend before.

I was just running it fine, rebooted, came back and I saw it just prune the fkng
thing all magically on its own.

luckily i have a copy of the blockchain on another computer but this is a huge pain
in the fkng ass

I didnt do it, but Ive seen the bitcoin core program itself do SOMETHING lately.
SO, what is going on?
When I open bitcoin core, it says it is fully synched and I can watch it download
new blocks.
So, WTF is wrong, what do we do to fix our problem
MANY people are having THAT same problem.....

I have another PC that has this, that for whatever reason has not yet pruned the
blockchain, and it works fine, I see bitcoind running.
That is the main problem, bitcoind is not starting.
I put the logs right there....
SO what do we do?
You can see right here, bitcoin core runs PERFECTLY
But when Armory starts, everything crashes.
bitcoindD crashes or wont run so no connection and Armory wont run
What changed?  What is different.  Why is bitcoin core running like this now?
Why is it different but Armory WONT RUN??

I have screenshots but this site sucks so bad I cant even attach them directly.

So, you changed Bitcoin Core to PRUNE mode?

In Bitcoin Core, under "Settings -> Options -> Main"... is the "Prune" option checked?



If so, the problem isn't Armory, it's the way your node is configured. Armory doesn't work with a pruned node... it never has. You'll need to undo the Prune configuration (you might need to check your "bitcoin.conf" and/or the shortcut you use to start Bitcoin Core to make sure they're not overriding this setting window... look for this warning message in that dialog:



If it says that and shows something like "-prune=550" then it's in the .conf or the commandline/shortcut that is being used to start Bitcoin Core. That change needs to be undone and then you'll need to resync the entire blockchain again.

You cannot design a blockchain service that fully indexes your wallet's history against a node that prunes that very history.

2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1164 - C++ block utilities loaded successfully
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1281 -
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1282 -
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1283 -
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine:
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1288 -    Armory Version        : 0.96.5
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1289 -    Armory Build:         : 8730390989
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1290 -    PyBtcWallet  Version  : 1.35
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1292 -    OS Variant            : 10-10.0.18362--Multiprocessor Free
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\ADMIN\AppData\Roaming
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : C:\Users\ADMIN\AppData\Roaming\Bitcoin
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\ADMIN\AppData\Roaming\Armory\
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    :
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1297 -    Total Available RAM   : 7.85 GB
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1298 -    CPU ID string         : Intel64 Family 6 Model 142 Stepping 12, GenuineIntel
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1299 -    Number of CPU cores   : 8 cores
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1300 -    System is 64-bit      : True
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1301 -    Preferred Encoding    : cp1252
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1302 -    Machine Arch          : amd64
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1303 -    Available HDD (ARM)   : 335 GB
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1304 -    Available HDD (BTC)   : 335 GB
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1305 -
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py:
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     force_segwit    : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     nettimeout      : 2
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     rescan          : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     force_fcgi      : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreAllZC     : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     rescanBalance   : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     disableModules  : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     port            : None
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     interport       : 8223
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     coverageOutputDir: None
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     forceWalletCheck: False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     regtest         : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     rebuild         : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     thread_count    : -1
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     datadir         : DEFAULT
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     clearMempool    : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     offline         : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     armoryDBDir     : DEFAULT
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_port   : 9001
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiPort     : DEFAULT
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     disableConfPermis: False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     useTorSettings  : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     netlog          : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     keypool         : 100
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     coverageInclude : None
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     forceOnline     : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     disableWalletCheck: False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     redownload      : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     rpcBindAddr     : 127.0.0.1
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_ip     : 127.0.0.1
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     multisigFile    : DEFAULT
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     ram_usage       : -1
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreZC        : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     logDisable      : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     settingsPath    : C:\Users\ADMIN\AppData\Roaming\Armory\ArmorySettings.txt
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     language        : en
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     db_type         : DB_FULL
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     doDebug         : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     enableDetSign   : True
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     mtdebug         : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     testnet         : False
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     rpcport         : DEFAULT
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiHome     : DEFAULT
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiRpcport  : DEFAULT
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     logFile         : C:\Users\ADMIN\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1311 -     verbosity       : None
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments:
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\ADMIN\AppData\Roaming\Armory\ArmorySettings.txt
2019-12-09 23:27:07 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
2019-12-09 23:27:07 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2019-12-09 23:27:07 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2019-12-09 23:27:07 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background. 
2019-12-09 23:27:07 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2019-12-09 23:27:07 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2019-12-09 23:27:07 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2019-12-09 23:27:09 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\ADMIN\AppData\Roaming\Armory\ArmorySettings.txt
2019-12-09 23:27:09 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2019-12-09 23:27:09 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2019-12-09 23:27:09 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 6
2019-12-09 23:27:09 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2019-12-09 23:27:09 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user.  Done!
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2019-12-09 23:27:11 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2019-12-09 23:27:11 (INFO) -- SDM.pyc:254 - Found Bitcoin Core link on desktop: C:\Program Files\Bitcoin
2019-12-09 23:27:11 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2019-12-09 23:27:11 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2019-12-09 23:27:11 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2019-12-09 23:27:11 (INFO) -- SDM.pyc:175 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2019-12-09 23:27:11 (INFO) -- SDM.pyc:340 - Called startBitcoind
2019-12-09 23:27:11 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=C:\Users\ADMIN\AppData\Roaming\Bitcoin -dbcache=1000
2019-12-09 23:27:11 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\ADMIN\\AppData\\Roaming\\Bitcoin', '-dbcache=1000']
2019-12-09 23:27:11 (INFO) -- SDM.pyc:451 - PID of bitcoind: 72852
2019-12-09 23:27:11 (INFO) -- SDM.pyc:452 - PID of armory:   51008
2019-12-09 23:27:11 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\guardian.exe', '51008', '72852']
2019-12-09 23:27:17 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2019-12-09 23:27:17 (WARNING) -- SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\ADMIN\AppData\Roaming\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\ADMIN\AppData\Roaming\Armory\" --dbdir="C:\Users\ADMIN\AppData\Roaming\Armory\databases"
2019-12-09 23:27:17 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\ADMIN\\AppData\\Roaming\\Bitcoin\\blocks"', '--satoshi-port=8333', '--datadir="C:\\Users\\ADMIN\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\ADMIN\\AppData\\Roaming\\Armory\\databases"']
2019-12-09 23:27:22 (INFO) -- ArmoryQt.py:1824 - Connecting on port 54680
2019-12-09 23:27:22 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2019-12-09 23:27:22 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary

2019-12-09 23:27:22 (ERROR) -- ArmoryQt.py:1198 - 4 attempts to load blockchain failed.  Remove mempool.bin.
2019-12-09 23:27:22 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.

2019-12-09 23:27:22 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2019-12-09 23:27:22 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:22 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:24 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:24 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:24 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:24 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:25 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:25 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:25 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:25 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:26 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:27 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:27 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:27 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:30 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:30 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:30 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:30 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:31 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:27:31 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-12-09 23:28:24 (INFO) -- ArmoryQt.py:5475 - BDM state is scanning -- force shutdown BDM
2019-12-09 23:28:24 (INFO) -- SDM.pyc:465 - Called stopBitcoind
2019-12-09 23:28:24 (WARNING) -- SDM.pyc:515 - bitcoind exited, bitcoind STDOUT:
2019-12-09 23:28:24 (WARNING) -- SDM.pyc:517 -
2019-12-09 23:28:24 (WARNING) -- SDM.pyc:518 - bitcoind exited, bitcoind STDERR:
2019-12-09 23:28:24 (WARNING) -- SDM.pyc:520 -
2019-12-09 23:28:24 (INFO) -- SDM.pyc:471 - ...but bitcoind is not running, to be able to stop
2019-12-09 23:28:26 (INFO) -- ArmoryQt.py:5490 - Attempting to close the main window!

looks pretty obvious the problem:

2019-12-09 23:27:22 (ERROR) -- ArmoryQt.py:1198 - 4 attempts to load blockchain failed.  Remove mempool.bin.
2019-12-09 23:27:22 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.

Kind of an ominous blaring kick in the nuts that when I see it prune the blockchain down, SOMETHING CHANGED.
But no Armory update to address recent changes......
SO here we sit....

(ERROR) ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=C:\Users\ADMIN\AppData\Roaming\Bitcoin
(WARNING) SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\ADMIN\AppData\Roaming\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\ADMIN\AppData\Roaming\Armory\" --dbdir="C:\Users\ADMIN\AppData\Roaming\Armory\databases"
(WARNING) ArmoryQt.py:4110 - Called updateSyncProgress while not sync'ing
(ERROR) ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
(WARNING) SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=C:\Users\seide\AppData\Roaming\Bitcoin -dbcache=1000
(WARNING) SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\seide\AppData\Roaming\Bitcoin\blocks" --satoshi-port=8333 --datadir="C:\Users\seide\AppData\Roaming\Armory\" --dbdir="C:\Users\seide\AppData\Roaming\Armory\databases"
(WARNING) SDM.pyc:515 - bitcoind exited, bitcoind STDOUT:
(WARNING) SDM.pyc:517 -
(WARNING) SDM.pyc:518 - bitcoind exited, bitcoind STDERR:
(WARNING) SDM.pyc:520 -


This was literally JUST working 6 hours ago.
I restarted, ran bitcoin core.
Exited
Ran Armory
Hangs, again.  This is the second time Ive seen this, BOTH TIMES after I noticed an update of some sort
and the  bitcoin core  blochain saved is MUCH smaller.

No update to this program in like a year, like seriously here..... 

Is there any support for this anymore?
As soon as I opened bitcoin core to synch the latest blocks, I saw it say something like parsing blocks.
Then my blocks folder under bitcoin core went down in size like 1/3 the size or less.
Hey, great.  Its not using 400 gig anymore.  But now Armory is stuck

I also see under the task manager, when you expand Armory, bitcoind no longer is running.
There is no connection to the bitcion deamon so it hangs.

So, something is wrong

Seriously, does anyone support or update this damn program?
After whatever update recently came out in the latest blockchain release, its fuked Armory.

So again, any foooooking support or just flush this dumpsterfire and move over to a hardware
wallet with actual support?

Are you able to run ArmoryDB.exe manually from the commandline and see what it does if you start it with the following:

NOTE: that in this instance, the satoshi-datadir should have the "blocks" folder appended to it

I get the same result and same error in my log file.

What happens if you modify the Armory shortcut and remove the "--satoshi-datadir" stuff... and just leave it with: "C:\Program Files (x86)\Armory\ArmoryQt.exe", then put J:\bitcoin in the Armory Settings in the "Bitcoin Home Dir" box and leave the Armory Database dir blank?

This is essentially what I have (with my custom Bitcoin Core directory)... no .conf files, no shortcut target... and just the custom Bitcoin DataDir listed in "Settings" in "Bitcoin Home Dir":


NOTE: I have "Let Armory run Bitcoin Core/bitcoind in the background" selected... but I leave the "Bitcoin Install Dir" box blank (and I actually have Bitcoin Core GUI already running whenever I start Armory)