no i haven't. I will do it. I think though I can sort of believe my balance though right? I only had transactions from a few years ago and they seem to be showing up.
The only way to know for sure is to check your balances against the current longest chain. |
|
|
|
|
Your chain data is borked. Have you tried deleting Armory's database folder yet?
|
|
|
|
|
1) Delete the content of this folder: C:\Users\Luke\AppData\Roaming\Armory\databases
2) Start BitcoinQt, leave it running
3) Delete your logs (armorylog.txt and dbLog.txt)
4) From the command line, browse to your Armory install folder (C:\Program Files (x86)\Armory\) and run "ArmoryDB.exe"
5) Start ArmoryQt the usual way, let it catch up, report here. If it fails, post the fresh logs.
|
|
|
|
|
Wait till Core catches up, then start Armory.
|
|
|
|
|
Start BitcoinQt, does it load properly?
|
|
|
|
|
Post the links here, how else am I supposed to look at the logs?
|
|
|
|
|
Paste in the lower half, or break it into smaller instances.
|
|
|
|
Will un-installing both armory and bitcoincore, then re-installing be an easier option?
Not really, need the logs to see what's wrong. Both logs
armorylog.txt and dbLog.txt Armory datadir
Depends on your operating system. Assuming Windows, the default location is C:\Users\*yourusername*\AppData\Roaming\Armory You have to show hidden folders to reveal AppData. You can also start Armory in offline mode to extract logs through the menu option. Once you got the logs, post them on pastebin. If you get the logs from the GUI, you'll only get one file, as it merges the 2 logs into a single one. |
|
|
|
How do I find the logs?
Look for armorylog.txt and dbLog.txt in ~/.armory |
|
|
|
|
You can find both log files in your Armory datadir.
|
|
|
|
I searched my pc for mempool.dat, found it, deleted it and now armory will not load up, it gets to 100% but doesn't actually open up the program?
The two are unrelated. You shouldn't go around nuking your db without presenting logs first. |
|
|
|
|
You need to clear the mempool for your node. Delete mempool.dat in your Bitcoin datadir.
|
|
|
|
No, I'm asking why having "D:\BitcoinCore" as Bitcoin Home Dir in the settings failed.
I have not investigated it, most likely the setting in the GUI gets bypassed at some point. If your question is does this work as intended, the answer is no, this is a bug. |
|
|
|
yes, in the settings window i checked "let armory run Bitcoin Core in the background"
and have "D:\BitcoinCore" as Bitcoin Home Dir
goatpig Why didn't this work in the first place? Might it be helpful for Armory to display an error message in the future (like "can't find satoshi -datadir") instead of hanging on "preparing database"? This is a client side issue. Only DB stuff gets reported in the GUI, cause it's not expecting to fail itself. I'll push a bug fix release with a bunch of such fixes sometimes soon. |
|
|
|
Thanks, good to know. It looks like Bitcoin Cash clients have 2 magic patterns
What an ugly hack. I don't think wiping the DB is necessary in that light, but I'd say it's preferable (unless you don't have the BCH chain and are just using the BTC one). I'm considering adding an option to stop DB scanning at a user defined height (to scan up to pre fork height without the need to mess with blockchain data). |
|
|
|
You mean have args to provide the rpclog/pass in the armory.conf? Reading another .conf than the one your node is started with would not help and introduce a lot of confusion.
Usually I provide the credentials in /home/user/.bitcoin/bitcoin.conf which only contains two lines: rpcuser and rpcpassword. Then a have a global bitcoin.conf in /etc with all the options I need. To enable armory to read my credentials I copied bitcoin.conf (with only rpcuser/password) to satoshi-datadir. I'll just add args to feed the log/pass from armory's own config files |
|
|
|
|
1) Where are you getting armoryd from?
2) Post armorylog.txt
3) What version of Python are you running?
|
|
|
|
All right, I was expecting armory to read bitcoin.conf from my home directory but it reads it only from the Bitcoin Home Dir. Now I have everything working great.
Thanks for your help!
You mean have args to provide the rpclog/pass in the armory.conf? Reading another .conf than the one your node is started with would not help and introduce a lot of confusion. |
|
|
|
RPC is configured with rpcuser and rpcpassword and working (at least with bitcoin-cli and lightningd). I see that ArmoryDB is running with "--cookie" but I can't use this as bitcoind is running with its own user with very limited permissions and the cookie file can't be read by other users.
Where can I tell armory the right rpcuser and rpcpassword?
You can't do that, it tries to read it from your bitcoin.conf on its own. You'd have to hardcode your log/pass in code and build it yourself. |
|
|
|
|
Do you have python twisted installed?
|
|
|
|
|
Show Posts
