-INFO - 1481145183: (..\DatabaseBuilder.cpp:268) parsed block file #378
This is way off. This is your last block file. It should be in the #700 instead. You are missing a lot of block data.
I'll explain the model so you get an idea of what's going on:
You are running 3 pieces of software at once:
- First, your bitcoin node. This connects to the bitcoin network, downloads and maintains blockchain data. Bootstrapping the blockchain is long and resource heavy. This is the longest part of the whole process. Once you have the blockchain data, the subsequent startups will be much faster.
The data is found in saved in block files, named blkXXXXX.dat (the XXXXX represent the block file number). You can find them here:
-INFO - 1481144202: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\Zebra\AppData\Roaming/Bitcoin/blocks
In your case, you have < 400 of these files, and that's an issue. You are missing about half the data you need to use Bitcoin properly.
- Second, ArmoryDB. This software parses the blkXXXXX.dat files directly from disk. This phase is called building the db.
The process needs to know where the blockchain data is (so far it has found it), and it needs the data to be consistent and complete. In you case, it is consistent but incomplete. Whenever this process says "Enabling zero-conf tracking", it means it has initialized and is now on standby. ArmoryDB interfaces with your node to maintain itself.
- Third, ArmoryQt. This is the client, holding your wallet data and providing the GUI. It interfaces with the DB for its needs. Your client serves the wallet data to the db. The db has to scan the wallets it is presented for the first time. This phase is called scanning the wallet history. It is the second longest, but nowhere as long as bootstrapping your node. This phase will crash if your block data is inconsistent.
Under normal circumstances, you only run the client, and it automates the other 2 processes for you. Since you are having issues, I'm having you run through the process step by step to try and troubleshoot the issue.
-------------------------
Seeing you are very short on block data, you need to start BitcoinQt and let it catch up. Consider adding server=1 in your bitcoin.conf to be get better feedback. Expect this part to take hours. Once that is done, run ArmoryDB again, then post your dbLog.txt again.
Bitcoin will never take hold when you have complicated problem with wallets. When person that hasn't designed the program and it crashes through no fault of their own is unsolvable. The keys ( solution) to the problem lay with an individual company or person to get it going. If you piss them off or they go under you are doomed to never recover....I guess being insolent to the customer doesn't count. I will donate but it doesn't encourage me to give as much.
To run a full node solution like Armory you need good internet bandwidth, a decent computer and you can't be afraid of getting technical. Your reward is a full fledged experience and a much better understanding of Bitcoin.
If you can't/won't go through these steps, you will have to look for a more user friendly wallet, at the cost of some important properties that make Bitcoin what it is.
There will always be people on this sub forum ready to explain and help those in need. In return, you should not abuse their patience and generosity by lacking in patience yourself, making it hard for them to help you, or ignore/cherry pick their instructions. That, and be civil when possible.
Show Posts
