Topic: Not Preparing Databases (Read 175 times)

The file extension was the issue. Everything works correctly now.
Thanks for your assistance.

Maybe you've created the file as "armoryqt.conf.txt" instead of "armoryqt.conf" that's why it's not recognized by Armory.

Windows hides the file extension by default, check if it's ticked in File Explorer's setting:
Go to the directory where 'armoryqt.conf' is, click "view" and tick "file name extensions",
after that, extensions like ".txt" will show up; if your config file has that extension, rename it so it will be ".conf".

Same result unfortunately. I restarted everything, double checked my settings and tried different combinations of e:\bitcoin and e:\bitcoin\blocks.

Per the pathing guide, the config file should be named armoryqt.conf with content: satoshi-datadir="e:\bitcoin\"
This is placed in the armory directly (same as the log files).
The armory db hasn't been moved so I haven't changed that in the GUI or in the armoryqt.conf file.

What's beyond my knowledge is why I change the bitcoin blockchain dir to my external drive at e:\ but the log file still shows the original. It's like the GUI changes are registering. 

Any other suggestions?

Pathing guide says it's "e:\bitcoin\blocks" but "e:\bitcoin" works fine at my end.

Regarding the logs:
If you've set satoshi directory through the UI, "Satoshi BTC directory" will register in the logs as the default but it will launch armorydb with the set path anyways.
You can see it in the line - "ArmoryQt.py:1891 - Setting satoshi datadir = E:\bitcoin" and below it showing that it's included as a start parameter of armorydb.
If you set it using the config file, the correct "Satoshi BTC directory" should be in the log.
Either one should work (I haven't tried if both are set though).

Now, I think you just need to restart your PC in every attempt since most of the time, armorydb will stay running in the background after closing armoryqt keeping the old settings with it.
Alternatively, open "task manager", find armorydb and if it's still there, end its process.

Piggybacking on this threat as I just moved my bitcoin core DB to an external drive and having this same issue with armory. Bitcoin core runs fine.

Armory > File > Settings: I set the bitcoin home directory to e:\Bitcoin, save, and restart.
Result: Databases don't prepare
I also tried changing the setting to e:\Bitcoin\blocks but same result.

Following the previous link on armory pathing, I've created armoryqt.conf with the content: satoshi-datadir="E:\Bitcoin\blocks" and place it in the windows armory directory. Restarted everything.
Result: Databases don't prepare

One question regarding the pathing, should it be e:\bitcoin or e:\bitcoin\blocks?

Log file is consistent whether or not I have the .conf file present:

Satoshi BTC directory : C:\Users\admin\AppData\Roaming\Bitcoin 

DB error: C:\Users\admin\AppData\Roaming/Bitcoin/blocks is not a valid path
 
ArmorySettings has what I expect however (I'm guessing this is pulling from the GUI):
SatoshiDatadir                       | E:\Bitcoin

I'm confused why the log file shows a different directory than the armorysettings file. Conf file having no impact.

Any suggestions on how to have Armory point to e:\bitcoin correctly? 

Is Bitcoin Core installed in a non-standard directory?
If so, you should specify where it is installed in "File->Settings...->Bitcoin Install Dir" and make sure the checkbox above it is ticked.

You may have to move armory's dbdir as well because the database will use more than that available disk space.

Refer to the "pathing" link above for the guide on how to set the dbdir.
I'd recommend the config files because the setting in the GUI is quite buggy when setting Armory's dbdir.

According to this error, seems that the path you have specified is incorrect and that's why Armory can't get data from the blockchain you have downloaded.
Visit the link below. The article should help you to know how to specify the correct path in Armory.
https://btcarmory.com/docs/pathing

2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1164 - C++ block utilities loaded successfully
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1281 -
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1282 -
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1283 -
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: D:\Programs\Armory\ArmoryQt.exe
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine:
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1288 -    Armory Version        : 0.96.5
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1289 -    Armory Build:         : 8730390989
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1290 -    PyBtcWallet  Version  : 1.35
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1292 -    OS Variant            : 10-10.0.18362--Multiprocessor Free
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\Admin\AppData\Roaming
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : C:\Users\Admin\AppData\Roaming\Bitcoin
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\Admin\AppData\Roaming\Armory\
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    :
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1297 -    Total Available RAM   :
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1298 -    CPU ID string         :
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1299 -    Number of CPU cores   :
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1300 -    System is 64-bit      : True
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1301 -    Preferred Encoding    : cp1252
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1302 -    Machine Arch          : amd64
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1303 -    Available HDD (ARM)   : 2 GB
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1304 -    Available HDD (BTC)   : 0 GB
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1305 -
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py:
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     force_segwit    : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     nettimeout      : 2
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     rescan          : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     force_fcgi      : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreAllZC     : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     rescanBalance   : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     disableModules  : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     port            : None
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     interport       : 8223
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     coverageOutputDir: None
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     forceWalletCheck: False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     regtest         : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     rebuild         : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     thread_count    : -1
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     datadir         : DEFAULT
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     clearMempool    : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     offline         : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     armoryDBDir     : DEFAULT
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_port   : 9001
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiPort     : DEFAULT
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     disableConfPermis: False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     useTorSettings  : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     netlog          : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     keypool         : 100
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     coverageInclude : None
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     forceOnline     : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     disableWalletCheck: False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     redownload      : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     rpcBindAddr     : 127.0.0.1
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_ip     : 127.0.0.1
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     multisigFile    : DEFAULT
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     ram_usage       : -1
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreZC        : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     logDisable      : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     settingsPath    : C:\Users\Admin\AppData\Roaming\Armory\ArmorySettings.txt
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     language        : en
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     db_type         : DB_FULL
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     doDebug         : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     enableDetSign   : True
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     mtdebug         : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     testnet         : False
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     rpcport         : DEFAULT
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiHome     : DEFAULT
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiRpcport  : DEFAULT
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     logFile         : C:\Users\Admin\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1311 -     verbosity       : None
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments:
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\Admin\AppData\Roaming\Armory\ArmorySettings.txt
2022-03-19 10:56:55 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
2022-03-19 10:56:55 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2022-03-19 10:56:55 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2022-03-19 10:56:55 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background. 
2022-03-19 10:56:55 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2022-03-19 10:56:55 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2022-03-19 10:56:55 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2022-03-19 10:56:58 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\Admin\AppData\Roaming\Armory\ArmorySettings.txt
2022-03-19 10:56:58 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2022-03-19 10:56:58 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2147 - ***WARNING: Duplicate wallet detected, fbcndYNK
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2158 - Second wallet is more useful than the first one...
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2159 -      Wallet 1 (skipped): C:\Users\Admin\AppData\Roaming\Armory\armory_fbcndYNK_encrypt.wallet
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2160 -      Wallet 2 (loaded):  C:\Users\Admin\AppData\Roaming\Armory\armory_fbcndYNK_.wallet
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2147 - ***WARNING: Duplicate wallet detected, fbcndYNK
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2158 - Second wallet is more useful than the first one...
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2159 -      Wallet 1 (skipped): C:\Users\Admin\AppData\Roaming\Armory\armory_fbcndYNK__WatchOnly.wallet
2022-03-19 10:56:59 (WARNING) -- ArmoryQt.py:2160 -      Wallet 2 (loaded):  C:\Users\Admin\AppData\Roaming\Armory\armory_fbcndYNK_.wallet
2022-03-19 10:56:59 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 1
2022-03-19 10:56:59 (INFO) -- ArmoryQt.py:2190 -    Wallet (fbcndYNK):    "MyWallet                        "   (Encrypted)
2022-03-19 10:56:59 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2022-03-19 10:56:59 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = G:\BitcoinCore\blocks
2022-03-19 10:57:01 (ERROR) -- ArmoryQt.py:1862 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1857, in startBitcoindIfNecessary
  File "SDM.pyc", line 190, in setupSDM
BitcoindError: bitcoind not found
2022-03-19 10:57:01 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0
2022-03-19 10:57:07 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2022-03-19 10:57:07 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = G:\BitcoinCore\blocks
2022-03-19 10:57:07 (WARNING) -- SDM.pyc:402 - Spawning DB with command: D:\Programs\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-port=8333 --datadir="C:\Users\Admin\AppData\Roaming\Armory\" --dbdir="C:\Users\Admin\AppData\Roaming\Armory\databases"
2022-03-19 10:57:07 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['D:\\Programs\\Armory\\ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', '--satoshi-port=8333', '--datadir="C:\\Users\\Admin\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Admin\\AppData\\Roaming\\Armory\\databases"']
2022-03-19 10:57:10 (INFO) -- ArmoryQt.py:1824 - Connecting on port 9001
2022-03-19 10:57:10 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2022-03-19 10:57:10 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\Admin\AppData\Roaming/Bitcoin/blocks is not a valid path
2022-03-19 10:57:10 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0
2022-03-19 10:57:10 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2022-03-19 10:57:10 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2022-03-19 10:57:10 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2022-03-19 10:57:29 (INFO) -- ArmoryQt.py:3671 - Log saved to D:/Documents/armorylog_20220319_1057.txt

Posting the logs may speed things-up, it's in your Armory data directory named armorylog.txt.
There's no information in your post that can tell the actual issue.

If you want to move out those funds from Armory, you can just export the private key of the funded address and import it to another wallet.
If you're interested, you can check this post: https://bitcointalksearch.org/topic/m.43255691

But please be careful with the private key(s) because anyone who got their hands on it will be able to spend your funds.

I installed the 424 GB blockchain through Bitcoin Core, but setting it as the "Bitcoin homedir" hasn't helped. Tried doing
G:/BitcoinCore/blocks
instead of
G:/BitcoinCore
but that hasn't worked. Adding the command line option
"--satoshi-datadir="
also hasn't helped. If you could help, that'd be great, I sent 35$ into this wallet expecting it to actually work like most technology, but that hasn't been the case.