Bitcoin Forum

Hi guys,

I'm trying to get Armory running. Took me a while to get everything set up but finally, it worked.
After restarting it again I wasn't able to get online to send some BTC.At the dashboard it says Armory
is online but the Node is offline nonetheless, it looks like Armory is not starting Bitcoin core automatically
even though it was running with the exact same setup.Any ideas what to do?

Got it online now and tried to send some BTC from my wallet. Everything worked fine until I received the following error message "The transaction that you just attempted to broadcast has timed out.The RPC interface of your node is disabled, therefor Armory cannot use it to gather more information about the time.It is recommended that you enable the RPC and try again.".I had RPC checked and got no idea what's going on. I would be very delighted if anyone could help me out.

It'll be your setup with Bitcoin Core... by default, Bitcoin Core doesn't have the the RPC enabled for other apps.

Shutdown Armory and Bitcoin Core. Then, add the following to your "bitcoin.conf"

Then restart Bitcoin Core. Then restart Armory.


NOTE: you may need to create the bitcoin.conf as it is not created by default. It should be place in the Bitcoin Core "datadir"... you can find the location of this directory by looking at "Window -> Information" dialog in Bitcoin Core.

I just had a look and wasn't able to find any of these folders.The Bitcoinfolder offers "blocks" , "chainstate","daemon", "doc".Is it necessary to have Bitcoin core installed in English?

In the meantime, Armory decided not to work.It might be my lack of understanding but why does it work smoothly one time and few hours later without any changes,it is completely lost.

The "datadir" is where the "blocks" and "chainstate" folders are... so what you have called "The Bitcoinfolder". So, create a file in that folder called "bitcoin.conf"... then add the "server=1" line... then restart Bitcoin Core.


To fully understand why things are not running correctly, you would need to post your log files. Copy/Paste the contents of your log files (armorylog.txt and dbLog.txt) to pastebin.com (https://pastebin.com/) and then post the URL that is generated when you click "create new paste"

Note: you can also use the "Export log file..." File menu option within Armory to create the log files.

I just had a look at the log files and it seems like there are issues with Bitcoin Core. According to the size (> 990 GB)  of the files, the blockchain has been loaded 2,5x times. I'll take care of it now and update the topic afterward.
Thank you very much for your help, I very much appreciate it.

After reinstalling Bitcoincore I got Armory in online mode now, lets see if it stays the way. Regarding the server = 1 file , should I simply create a .txt file?

You can create that file with a text editor, but you need to save it as bitcoin.conf and not as bitcoin.conf.txt

If you are on windows (what i am assuming), then it might be helpful to enable the option to show file extensions, which makes it easier for you.

I'm starting to feel like in a bad movie :(:In the process of getting back online, I'm stuck at "Parsing T x Hashes" , unfortunately, the process isn't shown,Any idea how long it takes usually?

"Parsing Tx Hashes" shouldn't take very long... certainly not more than a few minutes...

If it is stuck, you'll need to post up the latest version of your log files. Alternatively, you can try using the "Help -> Rebuild and Rescan Database" option and then restart Armory.

Here is my latest log file , maybe this helps to find the error. I anonymized some information for privacy reasons.



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

Unfortunately this is the beginning of your log file and doesn't contain any relevant information and doesn't show anything which would cause the issue you have.

Could you please upload the whole log file to pastebin (https://pastebin.com) or any similar service, then provide us the link.
Feel free to replace all personal information (you can use the replace all feature in most text editors to replace your username with some x's).

What seems strange is that it doesn't seem like Armory is spawning ArmoryDB??!? ??? There isn't any line that says: something like:

So, it's possible there is a "zombie" ArmoryDB process running in the background which is screwing things up. Shutdown Armory... then use the Windows Task Manager to kill any "Armory" or "ArmoryDB" tasks that you can find (right click on task in Task Manager -> End task). Alternatively, shut everything down and then restart your computer, that will 100% guarantee that any zombie processes are killed ;)

Then, try running Bitcoin Core+Armory again... if it is still hanging... you'll need to post the contents of your dbLog.txt, as I suspect that it is ArmoryDB that is having issues.

First of all, thank you very much for your help it is very much appreciated.I uploaded my whole log file after reinstalling bitcoin core, I'm very sorry as it is a wall of text but you asked for it:).
https://pastebin.com/2CcqNGRC

As I said, the latest "runs" are showing that Armory is not spawning ArmoryDB... there is most likely a zombie "ArmoryDB" process that is stopping things from working correctly.

So you need to either:
- Shut down Armory... kill zombie process with Task Manager... restart Armory
or
- Shut down computer, reboot... start Armory

I rebooted several times, it hasn't shown any significant difference. I'm not sure if I'm using the right path to let Armory load and open the blockchain. It is saved on another hard drive, not the default location. Furthermore the blockchain occupies > 700 GB now , it seems like there are some block saved in the wrong direction (double ofc as well).

Armory believes that your Bitcoin Core "datadir" is: E:\Bitcoin

This folder should have folders labelled "blocks", "chainstate" and "database" (and possibly one or two others)... it should also contain your wallet.dat file.

I'm not sure why you have > 700Gb of blockchain data... is that the size of E:\Bitcoin\Blocks folder? ??? It's possible that you've misconfigured something and it has started downloading to one location, and then you've changed the datadir config and it has downloaded to another location.


Can you please post the contents of your dbLog.txt file.

I just had a look , the file is 1,2 GB.Sounds way to big for my liking.I will look into it and post asap.I also searched the Task Manager while having Armory open and there is only 1 process (ArmoryDB)running .None other looked relevant, in terms of being a Zomby DB.

You need to check why you get 700GB files of blockchain data and maybe your Armory is confused and has a different blockchain path.

Try to use the search button instead to look for another folder with blockchain. Use keyword "blocks" let see if you can see two folder that has blockchain data.

Also check this path C:\Users\xxx\AppData\Roaming/Bitcoin/blocks

What do you see in Task Manager when Armory is not open? Is there still an ArmoryDB process? ???

The whole problem with the zombie process, is that it is "stuck" and will then prevent a "new" ArmoryDB from starting... Basically, Armory sees that there is already an ArmoryDB process running (but doesn't know that it is "stuck") and won't try and restart ArmoryDB :-\

Then, when you shut down Armory, it'll send a message to ArmoryDB to shutdown, but because ArmoryDB is "stuck", it won't shutdown and will just hang around forever... then when you restart Armory, the same thing happens, it sees the "stuck" one so doesn't bother trying to start a new ArmoryDB etc etc etc...

When armory is closed there is no such process as ArmoryDB or alike opened. I understand what you think might be the problem here, but this would mean that Armory works smoothly after restarting the PC but that isn't the case.
For my limited understanding, there must be a problem with Bitcoin Core and this is the reason why I can't get Armory online. While watching the processes carefully I recognized that BTC Core is not opened every time Armory is running.
Keep in mind that BTC Core is not installed in the default path and I'm not sure if I have given Armory the correct guide to finding it.My "Bitcoin Install Dir" f.e. is "E:\Bitcoin\daemon" and the "Bitcoin Home dir" "E:\Bitcoin". Regarding the size
of the blockchain there are 2 folder installed by default: - "Bitcoin" which includes folders like "blocks","chainstate","daemon", "database", "doc" and various files including bitcoin-qt.The other folder is called "btc" including "blocks","chainstate","Wallets"
only but apparently the blockchain is safed into both folders.

This is what I've been able to extract from the Dblog : https://pastebin.com/tbb8vbLF .I've got no idea why it is 1,2 GB but only shows data of the last run.

Then I'm not sure why (according to your armorylog.txt debug log) that sometimes Armory is not spawning ArmoryDB... The only reason I can think why that happens is because it detects that ArmoryDB is already running.

I assume you clicked the "more details" button in Task Manager and that you've checked all the background tasks:
https://talkimg.com/images/2023/11/15/z3GqC.png

Still, as you say, a restart should fix that problem... so it's not likely that a zombie process is the issue here.


I think your "pathing" is fine... you can see in the debug output that it finds your bitcoind.exe ok:



And ArmoryDB is finding your blocks OK:


This output is a little worrisome tho:
It seems you're missing ~90000 blocks??!?

The Bitcoin blockchain is currently at block #666366... so either your node is not fully synced, or it's actually using the "btc" folder instead of "bitcoin" and Armory is looking in the wrong place, or there is some corrupt data stopping Armory from scanning the blocks properly.


It's possible that your Bitcoin Core GUI setup has been configured to store the blocks in "btc\blocks"? ??? whereas, when Armory is spawning "bitcoind.exe" it is explicitly using the "Bitcoin\blocks" folder... If you run the Bitcoin Core GUI (aka BitcoinQt) and look in the "Window -> Information" screen... what are the values for "datadir" and "blocksdir"? ???

Either that, or it's an old datadir from a previous install? ??? What is the highest number blkXXXXX.dat file in the "btc\blocks" directory? ??? What is the highest number blkXXXXX.dat file in the "Bitcoin\blocks" directory? ???


You mean the dbLog file is 1.2 gigs??!? :o :o :o Something not right there... I'd try shutting Armory down and deleting both armorylog.txt and dbLog.txt... and then restart Armory. It'll help get rid of any old debug that isn't relevant anymore.

I did check the background processes yes, nothing odd there.Here is a screenshot of my task manager while running armory: https://imgur.com/QgkZPUa .Once again the Bitcoin core process looks strange to me and it differs from the one you posted. Armory is currently at node 577593 blocks, looks like you are on the right track here. I've uninstalled the core completely before but haven't set up any new paths.Bitcoin- blocks is currently on blk02413.dat , furthermore there are a lot of revxxx.dat which seem to match the blk data.The status at btc-blocks is blk02402.dat and rev02402.dat and was updated a week ago. When I run Bitcoin Qt without Armory it says there are 7 days in backlog.

Ok... I think I can see why you have two different copies of the blockchain.

In Armory settings, you have "Let Armory run Bitcoin Core/bitcoind in the background" checked don't you? ??? If my assumption is correct, what is happening is that the "bitcoind" that you see in your task manager (grouped under the Armory process) is being spawned by Armory and is using "-datadir=E:\Bitcoin".

However, when you run BitcoinQT manually, it appears to be using "E:\Bitcoin\btc". You can confirm this by running BitcoinQT (without Armory) and in the "Window -> Information" menu, you will see "datadir" and "blockdir"... what are these set to? ??? If my hunch is correct, is will say "E:\Bitcoin\btc" and "E:\Bitcoin\btc\blocks".

If that turns out to be true, we can reconfigure either Bitcoin Core (or Armory) so that both are pointing to the same data folder... then you'll be able to remove one of those folders and reclaim some "wasted" storage space ;)

Yes, its checked. Looks like your assumption is spot on https://imgur.com/nImQMac .Can you help me out setting up the pathing as well?

Ok, which one would you prefer to change? Probably easiest to change Bitcoin Core... basically, you just start Bitcoin Core using the -choosedatadir commandline switch, and it will pop up the "first run" dialog asking where you want to store the data...
https://talkimg.com/images/2023/11/15/z32Lw.png

A few things to note with this dialog...

1. Make sure you select the "Use a custom data directory" option and then set the path correctly, or it will create a THIRD copy of the blockchain! :P
and
2. Make 110% sure that the "Discard blocks after verification" box is NOT checked! If you leave this checked, it will immediately delete all but the most recent 2 gigs of blockchain data! :o :o :o


Also, if you see any "free space" warning in red like in my screenshot, you can probably ignore it... you already have the full blockchain downloaded in E:\Bitcoin, so it doesn't actually need 324 GB "free" as it won't need to download them. :P

Couldn't find an answer, whats the "-choosedatadir commandline switch" ?

It is a startup parameter.

Either 1) start the software (in this case: core) via the command line and add -choosedatadir at the end
or 2) right-click the shortcut -> details and edit the exeuction path by adding -choosedatadir at the end. Remember to remove this after starting it using that parameter. Otherwise you will be asked each time.

I just changed the location and updated the blockchain at "E:\Bitcoin" but it only added the most recent blocks. I've deleted the whole content of "E:Bitcoin/blocks" now to download the blockchain once again.Let's see if it works, I will update if the download is completed.

Did you make sure that "Discard blocks after verification" was "unchecked" when using -choosedatadir? And also that in Bitcoin Core GUI in "Settings -> Options -> Main" menu, that the "Prune block storage" is also unchecked? ???

I did uncheck "Discard blocks after verification"  but didn't know about other option. Is it necessary to uncheck "prune block storage" to get it running? Armory is currently building Databases which takes ages , maybe that's a good sign and it does run afterwards.

Hopefully... but yes, you must ensure that the "prune block storage" option is UNchecked... Armory cannot function with a "Pruned" node... it needs the full blockchain available to scan all the blocks.

Is the "building databases" progressing? ??? You might want to check the dbLog.txt file and make sure that it is actually logging the "parsed block file #xxxx" lines... if it's not, then it might be "stuck". When it gets to "scanning transactions" in Armory GUI, then you should see a bunch of lines in dbLog.txt like: "scanned from block #xxxxxx to #yyyyyy".

And yes, both of these processes can take quite a while to complete.

I got Armory running now, which gives me some hope. It seems to have the "right" amount of blocks (667530) as well. I can't send BTC though, I guess it's a matter of enabling RBF now. Can you give me a quick guide on how to do it properly?

Why can't you send your BTC ? Any error message?



How do you come to that conclusion?
Did you already send a transaction  and now want to increase its fee afterwards? Because that's what RBF is for.

Whether RBF is enabled or not is completely irrelevant to your wallet software. It can send transactions either way. It is just an optional flag.

When I'm trying to send BTC with the "Auto fee byte"  option checked and "enable RBF" unchecked I'm receiving the message "This is lower than the suggested minimum fee rate of 200 sat/B", I can decide whether I want to continue with this low fee or not. After choosing "yes" simply nothing happens. I decided to enable RBF and up the fee rate to the suggested 200 sat/B, after pressing "Send!" it is just not reacting, seems like Armory is not "receiving" the input. My explanation for this was that RBF is not working by default like I was told earlier in this thread.

Show me your logs.

RBF is (or at least should) be completely independent from this.

Please upload your logs to https://pastebin.com/ (http://pastebin) or any similar service and provide us the URL.
You can retrieve your logs by clicking  File -> Export Log File

Another day , another post on the Bitcoin Forum :).Thanks for your help and not getting tired of my problems.Here is my most recent log https://pastebin.com/knR2cmnR

Sorry to be a bore... but can you please post the dbLog.txt log file as well? ???

There may be something a little more descriptive there:

It's not boring me at all , it keeps me on the edge actually^^.Is there any sophisticated way of abstracting the content?Wordpad and Editor show nothing, OpenOffice only a huge number of ######.

Push

Does anyone got an idea how to extract the information from Dblog?

dbLog.txt, just post that file here, we'll go over it.

Please see the above post, when I try to open it the file is either empty or full of hashtags.

It's just a plaintext file... it shouldn't require any sort of "fancy" editor like OpenOffice or Word or anything... Notepad or Notepad++ should work just fine. If it's full of garbage then something is broken somewhere :-\

I guess something is broken then.Any idea what to do now?

Shut everything down, delete armorylog.txt, dbLog.txt and then reboot the PC... then once it has resstarted. Give it another try. If you're still getting the hashtags in the file instead of proper output, then shut everything down again, delete the logs and then try starting Bitcoin Core manually, let it sync... then run ArmoryDB.exe manually from the command line...

It should be in: C:\program files (x86)\Armory\

Note, because you have Bitcoin datadir set to a custom path, you'll need to use the --satoshi-datadir argument:

See if you get any weird errors displayed on the terminal window... if not, check dbLog.txt again.

Deleting both files worked and I was able to open dbLog with Wordpad.Here are the most recent outputs of armorylog: https://pastebin.com/TkMbYfKV and dbLog: https://pastebin.com/8GZ45jC9 . While scrolling through the settings I found another thing that made me curious, I'm trying to send to a SegWit address but apparently Armory uses the Legacy Armory addresses (P2PKH), could this be the reason why I'm not able to make transactions?

Top of the file may be filled by a lot of blanks as part of a log file truncation bug, the bottom half should have the data nonetheless.


Where do you see that? At any rate the bug you're experiencing is most likely this:


It's trying to grab the parent tx for the output being consumed but the DB can't find it. Is it ZC parent? Otherwise you should rescan your db.

Deleting the dbLog.txt solved the problem, there are no hashtags, blanks, or whatsoever.

I found the described address type at -> File -> Settings -> Fee and Address Types -> Change Address Type.

Please help me out what is the parent tx and a ZC parent?

I can rescan the DB but have done that several times before, without any success.

Parent TX = Which transaction created that UTXO that you're trying to spend?
ZC Parent = Zero Confirmation Parent... ie. is the parent transaction unconfirmed or confirmed?

If thats the only option you see I will rescan the DB and try to send again.Does not sound very promising to me bc it has been renewed so many times by now but I'm desperate to get Armory running now.

How are you creating the transaction that leads to this error?

When I'm trying to send BTC with the "Auto fee byte"  option checked and "enable RBF" unchecked I'm receiving the message "This is lower than the suggested minimum fee rate of 200 sat/B", I can decide whether I want to continue with this low fee or not. After choosing "yes" simply nothing happens. I decided to enable RBF and up the fee rate to the suggested 200 sat/B, after pressing "Send!" it is just not reacting, seems like Armory is not "receiving" the input. My explanation for this was that RBF is not working by default like I was told earlier in this thread.

Pretty much this.

It doesn't have anything to do with RBF, it has to do with some of your UTXOs. How many are there? You can check that in the UTXO selection dialog?

Currently, I can't do anything. I've rescanned the database and had to cancel after waiting for a day each time. Don't know what to do now because obv I don't know if it is even "working", according to the taskmanager it uses < 0,1 CPU and I've been waiting for 24h before canceling it bc it felt odd to take this long.

Are you saying you cancelled the database rescan? or you were cancelling trying to send the transaction?

Also, can you please post your latest logs.

Delete your Armory databases folder and try again.

Honestly I'm not sure if I can go through this process it feels like I wasted a month of my life already with this program.What other options do I get the coins out of my wallet?

Extract your keys, then import your keys into another wallet (like Electrum... or even Bitcoin Core seeing as how you have the node fully synced already).

You can follow my guide here for info on how to extract your keys: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691

Looks pretty straightforward, i think I'll give that a try.

If you follow those instructions exactly... you'll get hundreds of private keys as it includes all the "unused" ones (or what Armory thinks are unused if the wallet is not synced properly). If you've checked in Armory and know the exact addresses, you can also tick the "Address String" box and then find the specific private key(s) that you need.

Also note that you don't want to copy the "PrivBase58:" part when you are copying the private key(s)... you only want the 51 chars (starting with a "5") or the 52 chars (starting with an "K" or "L")

If you have any issues, let me know... and what wallet you're trying to import into to.

Alright, I have swept the coins into electrum and received them shortly after, very happy I was able to recover my balance.
Special thanks to HCP and the others who have helped me a ton, I don't take this for granted. Unfortunately, I have to say a
word of caution as well, even though Armory is often named as one of or the safest cold storage option it should not be used by
beginners. So many things can go wrong so easily and there will be no way to fix them by novices.

To end on a positive note, thanks again guys it seems like you are a very nice and very helpful community.