Armory 0.96.5

[btcArmory user]

My configuration is exactly like the one you posted. i have repeatedly closed down armory and bitcoin core and restarted the PC. I checked for the armory.conf file in the appdata\roaming\Armlory subdirectory on the C: drive. There is no file by that name, but there is an ArmorySettings with the value for SatoshiDatadir set appropriately.

[1713928099]

1713928099

[1713928099]

1713928099

[1713928099]

1713928099

[1713928099]

1713928099

[btcArmory user]

OK, I am waiting for further direction.

[HCP]

Ok, I have responded to your PM (and provided some alternative contact methods if you are having issues with the PM send limit that "newbie" accounts have here on Bitcointalk)...

Note that I'm travelling on business over the next day or so, so might not be able to respond immediately, but I'll do my best... in the meantime, if you could try posting up the latest versions of your log files, I'll take a look and see if the changes seem to be reflected in the log files.

[btcArmory user]

https://pastebin.com/WkZWvTbw
https://pastebin.com/pg7m0tZP

current logs

[HCP]

Have you not attempted to start Armory for a couple of days?

The last timestamp in the log file is from 13th March.

Code:

2021-03-13 11:20:32 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\enduser\AppData\Roaming/Bitcoin/blocks is not a valid path
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode

It still seems to be attempting to use the "default" Bitcoin Core datadirectory for some reason... I'm not sure why setting the path in the Armory settings is not being recorded correctly.

What directory is your bitcoin-qt.exe file in? Is it in "C:\Program Files\Bitcoin"? or is it somewhere else?

[btcArmory user]

I have at least two versions of bitcoin-qt installed. The one that I have been launching is on the d: drive. I'll shut down and then try the one in the path you indicated on the c: drive.

bitcoin-qt on the c: drive launches 0.14.2
the version on the d: drive - d:\bitcoin\bitcoin-qt launches 0.20.1

I  am trying to import a .jpg of the d:\ listing

How does that work on this blog?

There are a number of related directories on the d:\ drive.

[btcArmory user]

Maybe this will help to show where the path is being misdirected. Since the upgrades to bitcoin core 0.20.1 and Armory 0.96.5 this watching wallet installation has been offline and does not scan databases.

https://pastebin.com/5C5zQ3fh

Please let me know if anyone can see a configuration tweak that will get armory running again. Will it be necessary to upgrade bitcoin core from 0.20.1 to 0.21.0?

[HCP]

Aside from the "DB Error" issue with your blocks file not being "valid".... this is also of concern:

Code:

(ERROR) ArmoryQt.py:2180 - ***WARNING: Wallet could not be loaded: C:\Users\enduser\AppData\Roaming\Armory\armory_2ot51ac3y_.wallet (skipping)
Traceback (most recent call last):
  File "ArmoryQt.py", line 2140, in loadWalletsAndSettings
  File "armoryengine\Timer.pyc", line 99, in inner
  File "armoryengine\PyBtcWallet.pyc", line 2156, in readWalletFile
  File "armoryengine\PyBtcWallet.pyc", line 2457, in doWalletFileConsistencyCheck
  File "shutil.pyc", line 133, in copy
  File "shutil.pyc", line 97, in copyfile
IOError: [Errno 13] Permission denied: u'C:\\Users\\enduser\\AppData\\Roaming\\Armory\\armory_2ot51ac3y_.wallet'

Seems like you have some Windows permissions issues... Armory is not able to read the wallet file... are you able to view the properties of that file and see who the "owner" is? Are you running Armory as "administrator"?

[btcArmory user]

I am currently syncing up bitcoin core. Would it be typical to start bitcoin core using the bitcoin-qt executable?

I found an armory settings file with no appropriate data directory setting. It's in d:\btc

https://pastebin.com/yJPGf3e4

[btcArmory user]

are you able to view the properties of that file and see who the "owner" is? Are you running Armory as "administrator"?

The owner is 'enduser' - it's the only login that is being used on this system. I will see if I can run armory as administrator when the time comes. Maybe my armory 0_96_5 installation is still misconfigured? There are no current files in the \appdata\roaming\armory directory. There are only files from 0.96.3. It looks as if the 0_96_5 are all in the d:\armory 0_96_5 directory.

How much simpler and easier would it be to reinstall everything on a new system and restore the wallet for watching only?

[btcArmory user]

Bitcoin core is not running anymore. I can launch the splash page that checks wallet consistency. Then it says done loading
Bitcoin core never opens up and syncs. I tried running Bitcoin Core and Armory as administrator. I don't know what could have happened.

[btcArmory user]

Install bitcoin core 0.21.0 and then reinstall the .exe version of armory 0_96_5? Install the armory to the C:\...\appdata\roaming\armory directory? Last time, I probably installed to the d:\ drive.

[btcArmory user]

Does anyone have an idea as to where to go from here? It looks like everyone else has dropped off this thread.

[goatpig]

Make a thread dedicated to your specific issues please. This isn't really the place.

[HCP]

Does anyone have an idea as to where to go from here? It looks like everyone else has dropped off this thread.

Apologies... I had a rather unexpected "hospital adventure" that literally put me out of action for the better part of 2 weeks

As goatpig has suggested, you might want to create your own thread and we can start afresh and see if we can't get Armory and Bitcoin Core up and running on your machine.

A completely fresh start on a fresh system would definitely be the easiest way, but should not be necessary. The trick is to take things one step at a time...

1. Get Bitcoin Core setup and running properly (This includes getting it setup and using any "custom" locations" that you want, which seems to be applicable in your situation)
2. Make sure that Bitcoin Core is fully synced. This is very important. Armory will likely do weird things until Bitcoin Core is fully synced.
3. Get Armory up and running (and setup using any "custom" locations) and talking correctly to Bitcoin Core.


Using Windows 10, Armory 0.96.5 and Bitcoin Core 0.21 it should be relatively easy to get it all going.

[Aurik]

Dear,

is the software (armory) still maintained or updated?
So are there any plans to get 0.97 out? If so, any eta?

Thanks.

[HCP]

is the software (armory) still maintained or updated?

Yes... the website to use is here: https://btcarmory.com/
The github is here: https://github.com/goatpig/BitcoinArmory

So are there any plans to get 0.97 out?

Yes.

If so, any eta?

Im not good with ETAs, don't ask. Soon (TM)

Soon™

[jnagyjr]

is the software (armory) still maintained or updated?

Yes... the website to use is here: https://btcarmory.com/
The github is here: https://github.com/goatpig/BitcoinArmory

So are there any plans to get 0.97 out?

Yes.

If so, any eta?

Im not good with ETAs, don't ask. Soon (TM)

Soon™

Will this new version recognize more than 447,219 blocks?

[HCP]

Will this new version recognize more than 447,219 blocks?

The current version (0.96.5) works perfectly fine and syncs all the way up to the current block height:



If you are having issues with Armory 0.96.5 and it is only syncing up to 447219, then there is something wrong with your setup... either Bitcoin Core hasn't actually synced past that block (out of diskspace etc) so the data isn't available for Armory to scan or it could be that you have corrupted blockchain data and it is causing Armory to crash.


If you'd like assistance getting your Armory synced up properly, then I would suggest that you start a new thread, describe your issue as best as you can and make sure that you post your armory logs (ie. armorylog.txt and dblog.txt) to https://pastebin.com/ and copy/paste the generated pastebin links in your thread.

[NotATether]

One annoying detail as a result of goatpig's Armory forking from etothepi's version is that the new, forked Armory can't be searched on Github because it has less stars (401) than the parent repo (677). This causes Github not to index the fork and as a result you can only search for code & issues on the old outdated parent.

[I could just clone it and search offline but it's not as good as on Github]

It was inconvenient to the point where I cloned and uploaded my own copy just to enable this feature, though I apparently pushed a really out of date version from 2018.

So if you're reading this and you have etithepi's repo starred, unstar it, and star goatpig's Armory I guess, so that Github will finally index it for searching.