Topic: bitcoin core 26.0.0 with armory 0.96.0 (Read 246 times)

If you installed Armory, you should have an "Armory Offline" option in the Windows start menu option. Otherwise you can create a shortcut of ArmoryQt.exe and append "--offline" at the end of the target field. Lastly, you can start it from the command line:



This is because it chokes looking for your Bitcoin Core binaries, which you installed in the D drive. This doesn't serve much of a purpose, the binaries are only a few MB, it's the blockchain data that is gigantic.

The instruction I gave you with will allow you to start ArmoryQt and turn off the auto bitcoind step, which will prevent ArmoryQt from choking as it won't try to take charge of running Core for you. This will fix this primary issue and allow us to progress your case.

How will I start my watching-only Armory system in offline mode? I am unable to launch armory at all. The GUI is not available to me so that I can change any of the Armory settings. The only indication from Armory that it attempted to launch is that the splash screen says: Armory and the message at the top of the screen is loading: 100%. Armory stops there. It never opens up.

I run the commands from the CLI. I have been using the exact ones that you have in your most recent post. I have posted the log armotylog.txt in my last post. Please help -- is there anyone who can help with this?

1. Start Bitcoin Core
2. With Core still running, from the command line prompt, start ArmoryDB.exe. Copy paste the output of the prompt in here. You can feed it your paths directly, like this:


3. You can find your logs where you wallets live, not where the binaries live; armorylog.txt is useful at any rate.

4. Alternatively, start offline Armory and turn off auto bitcoind in the File -> Settings menu (first check box in there)

5. Once ArmoryDB is done setting up (when it starts talking about zc parser threads), you can start ArmoryQt on top of it. It will detect the instance of ArmoryDB and sync up.

First I uninstalled Armory and reinstalled. The latest armorylog.txt

https://pastebin.com/JcDNFXwb

I changed the bitcoin.conf to include the directories datadir and blocksdir. I also uncommented the parameter 'listen'

I am unable to locate the dblog.txt file. Maybe that's because I installed bitcoin core to the D: drive, not to the C: drive, where the user directories are. I have
c:\users\*usrname*\appdata\Armory but no c:\users\*usrname*\appdata\Bitcoin

There is no dblog.txt on either the C: drive or on the d: drive.

Would it help to post my main tab from the options menu in bitcoin-qt? I also have the "Window - information" tab from bitcoin-qt

Armory is launched at the CLI.
D:\Armory\Armoryqt.exe" --dbdir="D:\Armory" --satoshi-datadir="D:\Bitcoin\"

I am rebooting the system between each new attempt to launch Armory successfully. It stops at the splash screen that reads Armory: loading 100%
I have tried both
-launching bitcoin core, syncing up, and then starting armory using the CLI commands and
-exiting bitcoin core first and launching armory after the it shuts down to let Armory start bitcoin in the background.
The result has been exactly the same.

Any suggestions?

There will be an entry in the command line prompt telling you how long ArmoryDB took to build the database.

i too just downloaded the complete 6xxGB  block chain   and mine is  stuck   for 48 hours so far   see post https://bitcointalksearch.org/topic/restoring-old-wallets-but-stuck-on-database-sync-5520555


..
I am newbe to Armory again

How long will it take to build the chain db? How will I be able to verify that the process is running?


It's 651 GB

It appends the "/blocks" itself, don't add it.


There's a python GUI (ArmoryQt) and a c++ database (ArmoryDB). The each generate a log file. The log file you can extract from ArmoryQt concatenates the two. armorycpplog.txt is one of those. You can clear these up yourself if they grow too big.

Would the path be "\bitcoin data\blocks" or just "bitcoin data"?
What is the significance of the armorycpplog.txt file? I noticed one that had been created and had grown to about 45 MB.

You can ignore that setting for the most part, simply running Core manually will be enough for ArmoryDB to find the instance, as it looks for its listen server. What you need to provide ArmoryDB is the blockchain data path, which is set via --satoshi-datadir.

.
I would like to include that argument on the command line. At this point, Armory isn't launching to the point where the GUI is available.

Maybe I'll try this solution:
--satoshi="D:\bitcoin"
--satoshi-datadir="D:\bitcoin data"

Please I have a problem with Armory. It no longer connects online and when I open it offline, I can't export my key, iT SHOWS NONE, because it does not recognize P2SH-P2WPKH address in offline mode. How can I get armory to open segwit in offline mode, so I can export my key???

This error is a false positive. Armory does not know where to look for your Bitcoin Core binaries to manage it on your behalf, but that doesn't stop it from launching. You will have to start Bitcoin Core manually but we can figure this part out later. ArmoryDB does not need Bitcoin Core to start to bootstrap, it only cares for where the blockchain data is for the initial load.


1. ArmoryDB CANNOT run on a pruning node. A pruned node grabs the chain data, checks it, then discards >98% of it. Armory needs to look at the whole blockchain. What is the size of your blockchain folder? If it's not 300+ GB, you unfortunately have a pruned node and need to turn that off.

2&3. The RPC is nice to setup, it adds some helpful features. All you need to do to setup modern Core is to add this line to bitcoin.conf:

bitcoin.conf lives in your bitcoin datadir. If it's missing, you can create one using the notepad, save a plain text file. But again, ArmoryDB does not really use the connection to Core until after the initial big build&scan phase.

I tried to reproduce this in Windows11 and I got the same log with extra " at the end of the set directory, the the extra backslash at the end of the directory "D:\Bitcoin\" caused this.
Use --satoshi-datadir="D:\Bitcoin" instead.

Armory can't find your Bitcoin Core install directory.
You can set it in the GUI's settings so Armory can find it, "File->Settings...->Bitcoin Install Dir".

Those aren't related to the main issue but prune setting should be looked at.
Armory wont work if you enable "prune block storage" setting or prune= in Bitcoin Core.

I have changed the names of directories to elminate dashes and spaces, but it looks as if there is an armory error.

https://pastebin.com/Ngczgp8k

That armorylog.txt file was produced by using this command:
D:\"armory0965\Armory\Armoryqt.exe" --dbdir="D:\armory0965\Armory" --satoshi-datadir="D:\Bitcoin\"

Also, I found these requirements for successfully launching armory in other posts:


It's from a 2020 thread. https://bitcointalksearch.org/topic/m.55111554

Potential issues - will I need to check these? Do I need these?
*nonpruning instance of bitcoin core
*Bitcoin Core RPC
*listening on 8333

Is there a bitcoin.conf file that I could use as a template? Mine looks like nothing has been changed from the defaults.

There's a zombie ArmoryDB instance, likely running on the wrong arguments. Find in from the task manager and kill it. Then try again. If that doesn't help you, try dbdir without spaces or dashes in it.


You should not mix the binaries install folder (ArmoryQt.exe, ArmoryDB.exe) with the database folder (what is set by --dbdir). They do not need to live in the same place.

If you want to validate your DB pathing without having to go through the whole shortcut thing, you can run ArmoryDB.exe directly from the command line, giving it the --dbdir agrument. Then you can start ArmoryQt as is and it should find the existing instance of ArmoryDB.


Logs are useful, WER is not.

Pathing is apparently causing me problems. I downloaded bitcoin core 26.0.0 and armory 0.96.5 to my D: drive and installed both of them from there. bitcoin core seems to run with no issues when launched from the D: drive. I am trying to launch armory from the command line in adminstrator mode. I have tried both of these two commands:

D:\"armory 0-96-5\Armory\Armoryqt.exe" --dbdir="D:\armory 0-96-5\Armory" --satoshi-datadir="D:\Bitcoin data\blocks"
this one produces a Report.WER file, but no visible entries in the log files in the d:\armory 0-96-5\armory directory

D:\"armory 0-96-5\Armory\Armoryqt.exe" --dbdir="D:\armory 0-96-5\Armory" --satoshi-datadir="D:\Bitcoin data"
this one produces a log file armorylog.txt in the D:\armory 0-96-5\Armory directory.

I noticed that the default path for the armory installation was used by the installation routine anyway, and a shortcut to the armory location on the D: drive was installed there. Whether that mattters or not, idk.

 the c:\user\*user data*\appdata\roaming\armory subdirectory contains shortcuts to armory executables on the d: drive.

The current error that I'm getting is this:
ArmoryQt.py:5975 - Socket already in use.  Sent CLI args to existing proc.

Do I need to reboot to take care of this? Is it possible to use a command from the CLI to clear the existing socket?

Should I post logs to pastebin? Is the WER file of any use?

You should be trying with 0.96.5, you will have a much better experience:

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


It's better to let Core run then start Armory.


For now, let Core grab the whole chain, then start Armory without any wallet in it, it will build the chain db. Then you can import a watching only copy of your wallet in Armory, that will scan the chain for your addresses, at which point you should see your balance. Come back here if you run into issues.

If that's the goal, you can export the addresses (and private keys) with Armory's backup feature,
Then import the addresses to a wallet that supports importation of individual addresses, e.g.: Electrum.
You can also create an Electrum wallet in a separate offline PC (latest Electrum wont work on WindowsXP) to import your private keys and it will be able to sign the transactions created by the watch-only wallet.

Here's a post by HCP on how to export the keys and addresses (including unused ones).
Link: https://bitcointalksearch.org/topic/m.43255691
Tick "address string" to list your addresses and untick those that you don't want to see.

I installed bitcoin core 26.0.0 a few months ago on a Windows 11 machine. I got enough time to return to it again, and I am near the end of the process of downloading the blockchain. My plan originally was to use the latest armory version to attempt to restore a paper wallet. It looks like I will be using v 0.96.0 -- ?
It looks like bitcoin core could be upgraded to v 28.0.0 right away. Is that necessary?
Is this the right procedure for the upgrade?
-shut down bitcoin core completely
-run the v 28.0.0 installation from a *.exe
-sync up to the network again

I'd like to find a tutorial on the whole process, in as much detail as is possible.

After upgrading to bitcoin 28.0.0, would my next steps be as follows?
-shut down bitcoin core completely
-install armory's latest version
-configure armory to recognize bitcoin core and use the blockchain

OR

does armory recognize the bitcoin installation and automatically run bitcoin core in the background?

Are there known issues with the 28.0.0 version of bitcoin core and the latest version of armory?
Will there be any problems with running everything on an external drive? Maybe it was more conventional to run armory from the c: drive in the past?

You can see that I need a lot of advice. My first objective is to restore my bitcoin wallets from 2013 through 2019. I want the public addresses and the logs.
There is probably still some BTC in one of the wallets. That is a secondary objective.
I started with armory in 2013. I have cold storage set up on a Windows 7 machine. It still runs. My watching only wallet was set up on a Windows 7 machine that upgraded to Windows 10. I lost the use of that, due to hardware issues.

Please help.