Topic: Armoury 0.95 - "Building database" forever (Read 3208 times)

Isn't 0.95 when they separated ArmoryDB from ArmoryQT? When ArmoryDB is called by ArmoryQT, it doesn't pass the proper settings, so you have to run ArmoryDB on its own.

Now I'm confused if 0.94.1 works 0.95 should also work (after pasting guardian.exe in it) but I think it is now becasue of an processor.
Have you also deleted databases in %appdata%\Armory\? if yes and it still does not work pls try BitCoin Core 0.13.1 (27.10.2016)
May with the newest Bitcoin it works for you, for me it also works with 0.13.1

That caused an immediate crash. On the second attempt it started up with plenty of repeated errors...
GUI still stuck at the same spot.

Try commenting out (with a # in front of the lines) those lines in the bitcoin.conf and see if it will work then.

Bitcoin Core (64-bit) 0.13.0

That error is due to it being unable to connect to Bitcoin Core's RPC server. What version of Bitcoin Core are you using? What is inside of the bitcoin.conf file?

No such luck. I even tried reindexing my Bitcoin database and then ran ArmoryDB. ArmoryQT in debug mode spams out...
Armory 0.93.3 and 0.94.1 work fine, but not 0.95.0. Maybe it's because I'm using an old AMD 1090T processor?

Now pls backup the guardian.exe File from C:\Program Files (x86)\Armory and install 0.95 then copy it back. Thats all

I just tried 0.94.1 and it appears to be working.

1) I forgot guardian.exe on the Windows package, my bad. You can still run Armory if you turn off auto bitcoind management and run BitcoinQt yourself. I'll fix the release sometimes this week.

2)


Ugh, don't post unsigned 100Kb executables online, that's a poor idea. Guardian.exe is the same accross all versions, ever since it was introduced. If you can't wait for a fix, grab the file from older packages.

3)


DB is failing to detect older versions and still reads ahead, which results in this error. I'll fix that along with guardian. The end result is the same, you need to provide the DB with another a fresh dbdir or wipe your existing one.


This is not accurate. 0.95 is compatible with SegWit chains that Core 0.13 enabled on the testnet and 0.13.1 will eventually enable on the mainnet. The requirement is for Armory to be updated to 0.95 to run against a SegWit chain. 0.95 can run against any older version of the blockchain.


It will be 0.95.1. No point disturbing the versioning pattern. The slow startup I believe is related to starting bitcoind first. The client waits on bitcoind to get ready before processing any further. Test this assumption by turning off auto bitcoind, starting BitcoinQt yourself, then starting Armory. The DB should spawn right away.

This issue will go away in the next subrelease (0.95.2 now), once I'll have all the bitcoind management moved to the DB.


There is no "normally" per se yet. 0.95 just introduced the DB as its own binary. It used to run within the client's virtual address space as a shared library before.

I've left the DB command line dialog visible in Windows on purpose, as I explained in the release post. This is to make debugging easier and make users aware of the architectural shift. I'll hide it in 0.95.2

I'm running 0.95 on Windows 10 x64 so it's not related to Windows 10.
If you have TeamViewer I may could help you

BTW which BitCoin Version are you running? Pls update to v0.13 (as it is the minimum requirement --> https://btcarmory.com/0.95.0-release/ )


Why Back? You can just simply have both installed with different Installationdirectorys And why 0.93.3 and not 0.94.1?

I tried it again. ArmoryDB went fine, but when I run ArmoryQT I still get...

(DEBUG) SDM.pyc:794 - generic jsonrpc exception

Eventually ArmoryDB pops up on its own, but it uses the default path which doesn't exist.

Maybe it's because I am using Windows 10? Bitcoind does run in the background with ArmoryQT. Back to 0.93.3.

This will result in the same thing becasue ArmoryQT is starting ArmoryDB itself. At this 0.95 version there is a bug and it starts in visible (normaly it starts it in the Background) but it starts it anyway.
Btw you dont have to regenerate 59GB, it just creates 700MB DB;) (Building DB and scanning takes for me 10 min on SSD)

Did you try skipping ArmoryDB and run ArmoryQT without it?

It's an annoyance to regenerate 59GB's worth of files.

I know, this happens because guardian.exe is missing in the 0.95 Windows installationfile.
Pls just watch the post above you

That was the error I got before I emptied the Armory data directory. When you empty the directory, ArmoryDB.exe will work without error, but that doesn't mean ArmoryQT will work.

[EDIT]
Looks like you got it to work with guardian.

For all Windowsuser getting the same error like me and getting this error in ArmoryQT.exe.log:


Download this File (guardian.exe 109 KB) :

Zippyshare
Mega.nz
G-Drive

if you dont trust me (this files) download 0.94.1 and install it to another directory. Then continue with your own guardian.exe

place this file in the installationdirectory (standard is C:\Program Files (x86)\Armory)

If you now got this error by running ArmoryDB.exe:


Close and exit Armory (even in the tray)
Go to %appdata%\Armory\ and delete the folder called databases then start ArmoryDB.exe again.
After it finished start ArmoryQT.exe and wait (on HDD maybe about 5min) now ArmoryDB.exe starts itself and does everything what is necessary.

Have fun.


Proof of work -->

https://i.imgur.com/p1Ghh0H.png
https://i.imgur.com/atQBm62.png


I guess there will be a 0.95.0.1 with including guardian.exe

@goatpig: on Windows I have to wait about 1 min when I start ArmoryQT (like this) untill it starts ArmoryDB itself. Could you pls watch out what makes it taking so long?
Thanks!

This is what it showed me:


I had to run ArmoryDB.exe as Admin and first garant network access. (without admin it stuck at #96)
BTW: ArmoryQT.exe.log shows me:



But in the end nothing changed and it's still not working
For me it looks like you forgot to add Guardian to the 0.95-Bundle of Windows

I uninstalled 0.95 and went back to 0.93.3, since I am not having any problems with the old version.

ArmoryDB wrote 797MB and the log ended with...

-DEBUG - 1477260767: (..\Blockchain.cpp:232) Organizing chain
-INFO  - 1477260780: (..\DatabaseBuilder.cpp:49) updated HEADERS db in 1127.35s
-INFO  - 1477260780: (..\BlockUtils.cpp:1619) Enabling zero-conf tracking

Started Armory and ArmoryQt.exe.log shows...

(ERROR) SDM.pyc:376 - Could not find guardian script: .\guardian.exe
(ERROR) ArmoryQt.py:2247 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 2243, in startBitcoindIfNecessary
  File "SDM.pyc", line 468, in startBitcoind
  File "SDM.pyc", line 577, in launchBitcoindAndGuardian
  File "SDM.pyc", line 377, in getGuardianPath
FileExistsError