building database issue

[hadhad]

Hi,

I bought some BTC many moons ago and locked them up tight in Armory. I also created a watching wallet in an offline PC. Then I just left them...

Now a couple of years have passed since I updated everything and I'm having all kinds of trouble! Perhaps someone can offer me some help?

I updated my Bitcoin core and downloaded the blockchain - 5 days later it was fully synced. I then ran Armory which located the blockchain and moved onto rebuilding database. This has taken an absolute age. I've left it running overnight for about 2 weeks so far and after about 150 hours it had crawled to 93% complete. I then woke up this morning and discover that it has decided to delete the contents of level_db folder and start again!

Oddly, in the first 6 hours it "raced" to 44% complete but is now estimating 5 days until completion.

This cannot be right, can it? What is likely causing this snail's pace progress? Why did it delete over 100GB of data and start again?


Can anyone offer some advice? What sort of details do you need from me to diagnose the problem?

[goatpig]

Post you logs. Use pastebin.

[hadhad]

Ok - which logs do you need to see? I only have the armorylog.txt with me at the moment (at work).

[goatpig]

Every log you got.

[hadhad]

Thanks for the responses goatpig

Here's a pastebin of the armorylog:

https://pastebin.com/rdvVvKHs

I'll do the rest when I get home.

[hadhad]

Armorycpplog:
https://pastebin.com/UnkWJ90w

blkfiles:
https://pastebin.com/NjaRqcLm

Armory setings:
https://pastebin.com/MKuHYvSN


Any log files I missed?

I running Armory 0.90-beta, the same on my offline laptop. I cant update because my partner has "tidied up" my paper seed...
I am trying to find it but hoping it will not be needed anymore if I move my BTC to my nano ledger.

The pastebin in the previous post is truncated as it was well over the size limit (4000kb) of my basic pastebin account limit. It does capture the moment the database switched from 93% completion to starting again though.

[goatpig]

I running Armory 0.90-beta

Update.

[hadhad]

How will that effect my watching wallet? Cant update that currently...

[goatpig]

Update on your online machine. Ignore the offline signer for now. I do not understand why you can't update, you will have to elaborate if you want guidance.

[hadhad]

I cant update because i didn't want to be in a situation where the offline signer was a different version than the online version. My paper seed has been misplaced so I didn't want to have to update the software. If this isn't a problem then fine, I'll try an update.

[goatpig]

Just update the online machine for now, you can figure out the offline part later. The installer only replaces binaries so you can just run it on top of an existing installation.

[hadhad]

Right, so far so good.

Updated to 0.96 and i'm all synced up and ready on my online PC. I did get a crash whilst scanning the transaction history though. It was saying 61% complete with 1 second left to go for about 10 minutes. Then it closed itself. I loaded it again and in a flash it was up and running like nothing had happened!

Anyway, it's amazing how much more efficient the ArmoryDB was! Kudos to you goatpig. I will address the offline PC issue when I next get the chance. Can I just update that software to or is it more complicated than that?!


Thanks for your help up to this point; another step closer to my goal 

[goatpig]

Can I just update that software to or is it more complicated than that?!

It's no different from installing the new stuff on the online machine.

It was saying 61% complete with 1 second left to go for about 10 minutes. Then it closed itself. I loaded it again and in a flash it was up and running like nothing had happened!

0.96 has some issues with bootstrapping the DB on slower machines. Maybe your DB is actually synced. Post your dbLog.txt to be sure.

[hadhad]

Pretty happy my databases are synced now.

Starting to think about updating the offline signer to a version that will be compatible with 0.96 now.

My offline signer is an old piece of rubbish - 32 bit XP system. Where can I download the armory client for this?

[goatpig]

XP is a bit harsh, even Microsoft doesn't support it anymore. I'll be putting offline builds for 0.96.1, looking to do a 32bit build as well, but I don't have any hopes it will run on XP (even though the compiler says it generates XP compatible binaries).

[Casimir1904]

Pretty happy my databases are synced now.

Starting to think about updating the offline signer to a version that will be compatible with 0.96 now.

My offline signer is an old piece of rubbish - 32 bit XP system. Where can I download the armory client for this?

I would suggest to install debian/ubuntu on that machine

[hadhad]

Hmmm, XP coming back to bite me it seems.

I've found my paper seed. Phew!

Can I just restore my wallet and by-pass the whole need to get the offline signing working?

[hadhad]

Right, I've restored the wallet from the paper backup. Everything is synced and loaded. Transaction history has been scanned etc

I cannot send any BTC. I keep getting a tx timeout error or Armory just crashes.

Armory log:
https://pastebin.com/Dy91xLnG

dblog:
https://pastebin.com/CWM1R6JH


I've tried with a few times with higher fees but just cannot send. What is up with this?

[achow101]

Right, I've restored the wallet from the paper backup. Everything is synced and loaded. Transaction history has been scanned etc

I cannot send any BTC. I keep getting a tx timeout error or Armory just crashes.

Armory log:
https://pastebin.com/Dy91xLnG

dblog:
https://pastebin.com/CWM1R6JH


I've tried with a few times with higher fees but just cannot send. What is up with this?

This is a known issue that has been "fixed" (not really, just hacked to not fail) in the latest 0.96.1 testing build. You should upgrade to that, available here: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing

Don't keep trying to spend after the first error. You'll end up making a bunch of double spends and that is bad.

[hadhad]

Cheers achow. I updated to 0.96.0.3 and have successfully moved my BTC. Thanks for the suggestion.