For some reason you managed to get the mem leak bug. Shutdown Bitcoin Core and start the DB alone. What are your system specs btw?

What's the process CPU load? RAM load?

There is nothing in your log indicating an issue, just let it finish.

Post your dbLog. If you want to see the command prompt, you'll have to start ArmoryDB from within a prompt.

Yes


No

Another 300 or so. Kill the process and use the version I pointed you to.

I explicitly told you to use the testing builds.

If you are having stability issues, you want to use this:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing

Bootstrap the DB like this:

1) Delete the content of C:\Users\XXXXXX\AppData\Roaming\Armory\databases. Don't delete the folder, the DB won't create it for you, just empty its content

2) Don't run Bitcoin at all. Open your command line prompt (type cmd in the search bar), cd to the Armory binary folder, and type ArmoryDB.exe in there. This will run the DB on its own. Let it build. Once it is done, it should tell you something like "Enabling zero conf parsing".

3) With the DB still running and the build phase over, start ArmoryQt. This will send the DB in its scan phase.

4) Once that's done you should be done with the hard part. You can shut all that stuff down, start your node and let it catch up, then start Armory the regular way.

Post both logs in full. Use pastebin.

Pushed a fix for that

Don't troll other people's thread please.

Armory uses qt4, therefor qt5's lrelease may or may not get Armory to choke on the language packs. Ideally, it should run qt4's lrelease.

I'll add the missing include (no idea why this is breaking compilation, as it has not been an issue so far). I'll also add a check for lrelease in the executable path.

Means your node has bad connectivity/is overloaded. Update to 0.96.0.3 for better verbose.


https://btcarmory.com/docs/pathing

1) Delete this folder: C:\Users\DOM\AppData\Roaming\Armory\databases
2) Start BitcoinQt manually, don't let Armory manage it for now
3) Update to the lastest testing builds: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing

It's gonna be nearly impossible to debug this if you don't have any C++ in you sorry.

This is basically saying it can't build std::function

Create a .cpp and test the lib against that. File would look something like this:

This is a relevant symptom. How large is your node's mempool? Anything worth of note getting to that point? Let the Armory run for a few hours, does it get to that point?


Which one is it? WO's can be considered your wallet as long as you specify that in the ownership field. They are not by default however.

Will have to figure it out with autotools. yey....

These are warnings not errors. Post the entire make output on pastebin for me to look at.

If the bug is still there, you gonna have to try and narrow it down. It didn't happen anymore in my testing after the fix.