Hi, I'm using Armory 0.93.3 with Core 0.11.1
That's an old stack. You should consider upgrading. I've seen that Armory 0.95.1 with Segwit is out (no idea what that is), but shouldn't be sending work as expected with the 0.93.3 client? Is there a known bug?
I'm not sure what the issue is, but I know that it wouldn't happen in 0.95. At any rate, try manually setting a higher fee to spend, looks like the automated fee bump is failing. In the log there is no error or anything I could see.
That's really for me to say. Post your logs. I thought of changing the wallet password to see if unlocking works, but I'm afraid now to change anything if there is something wrong anyway.
You did not get as far as unlocking your wallet. |
|
|
|
|
Use pastebin next time =D.
If you go into your wallet's property dialog, do you see the balance? I'm not sure exactly what the issue is, do you mind sending a screenshot of the main lobby and the inside the wallet property dialog? Feel free to mask out privacy leaking stuff.
|
|
|
|
|
I'd have to have time to go over it. Not my priority atm sorry. If someone else takes over that project, I'd be happy to assist them.
|
|
|
|
|
Ok, what about fetching missing history by address?
|
|
|
|
Prior to ATI's stagnation, the was a lot of development, and a lot of other work that was going to be incorporated into armory but never had the chance to due to ATI stopping development. Furthermore the was a lot more testing and higher quality assurance than right now. I'm sure you have noticed that goatpig's releases have many bugs that would have been caught if there were more testing.
For my defense, my first 2 solo versions came with a lot deep changes to the DB and a lot of new code, which increases the bug surface tremendously. Upcoming versions won't modify the DB anywhere as much. |
|
|
|
|
Do you get the full history by loading the wallet in ArmoryQt?
|
|
|
|
and my money is gone.
Have you checked the addresses on a blockchain explorer? Most likely the coins are there and you never got Armory to sync. They cut support for 32 bit (good luck finding a copy), only link is hosted on Amazon, which they blocked.
ATI is not maintaining Armory anymore. I do it now, on my own pocket and dime. You can find my releases here: https://github.com/goatpig/BitcoinArmory/releasesAs for 32 bit versions, ATI still host their last version of 32bit offline signers on this page: http://www.bitcoinarmory.com/download/There is no 32 bit support anymore for online Armory because of technical reasons. Basically, the underlying database engine cannot access files larger than 2GB on x86 systems. The new, compact DB in my versions are well below 2GB, so I could in theory revive online x86 support, but you have to keep in mind that any native x86 processor out there is utterly underpowered for the current size of the blockchain. On that regard, if you only have some old hardware to sync Armory on, I strongly suggest you simply extract your private keys and try your hand at a lightweight wallet instead, as you don't have the hardware to run a full node stack. Email services is down, and their support forum link is down.
No paid employees, no free support (somehow that sounds off). Ask nicely and plenty of people will be glad to help you over here. Fuck this company, fuck Bitcoin Armory. Fuck incompetence and fuck broken programs.
There is no company anymore. You seem to confuse incompetence with dropped support. At any rate, Bitcoin in general has always been free open source beta software, and the same goes for Armory, whether under ATI or my lead. You should manage your expectations accordingly. |
|
|
|
Thanks for this, I looked at the backup in Notepad++ and all it is is nil values, so I guess the backup wasn't done correctly or was corrupted.
So I guess no point trying for this, but hopefully the exercise showed a few things.
Did you create this backup from the GUI or just copied the wallet file? If it's from the GUI, then this is possibly a bug on Armory's end and I need to go over it. Cheers goatpig, and i'm happy to volunteer with the website if noone else is!
The website is in dire need of tutorials and a FAQ. I'd be glad to merge in your contributions if you feel so inclined. You can submits PR directly to the gh-pages branch or coordinate with achow101 on the IRC channel (#bitcoin-armory at freenode) |
|
|
|
|
Let me see the whole log file then.
|
|
|
|
That alone (only unchecking the box) works! A new window (that looks like the one I get on entering “cmd.exe”) is opening and then each block is obviously scanned. Something like ..\DatabaseBuilder.cpp:268 parsed block file #xx There was no need to start BitCoin Core, simply unchecking the box was enough.
After it finished, I closed this command-line-window and Armory kept on working. Without having me manually started BitCoinCore (And I can not see in the Task Manager that Windows Core would be running either).
While you can bootstrap Armory against just the blockchain data, you need to let Core run to receive block updates. Simply initializing Armory against the data on disk is not enough to actually be online. The distinction isn't visible in the GUI atm, but I'll be going over that for the next version. At any rate, once you are initliazed, Core should be running. Out of curiosity, simply because I want to understand what is happening and why (despite I´m more a Noob than a Nerd in IT things and quite a heavy bit older than the average here on the forum, I guess) I did this as well.
First, this resulted in having BitCoinCore (v 0.13.1) to do a full verification of all my blocks. After that I started Armory and it worked the same way as described just above (a new command line-like window opened up etc.)
At some point Armory is failing to automate Core (bitcoind) properly. Most likely, it isn't passing the proper paths to the bitcoind. |
|
|
|
|
Oh wow, didn't expect you to come back.
Your files are here: C:\Users\Kate\AppData\Roaming\Armory\
I suggest you upgrade to 0.95.1, then delete C:\Users\Kate\AppData\Roaming\Armory\databases and try from the top. If you run into issues, post dbLog.txt, you'll find it in that same folder.
|
|
|
|
|
Post armorylog.txt please.
|
|
|
|
|
You will have to force the path manually in that dialog instead of relying on the auto detection.
|
|
|
|
|
Are you using several wallets? In armoryd, you need to select a wallet to be active in order to fetch data for it. At any rate, since I've taken over Armory alone, I have neglected armoryd. I intent to go over it for the upcoming version. Feel free to drop by the IRC channel (#bitcoin-armory on freenode) or create a issue on the github page to go over the bugs you have encountered and I'll make sure to fix them for 0.96.
|
|
|
|
|
Verifying the blockchain is a taxing task. Unless you got a high end CPU/RAM/SSD combo, it will take tens of hours.
|
|
|
|
|
Last few blocks are damaged. You will have to:
1) Delete the last 5 or so blkXXXXX.data files in your blockchain dir
2) Start BitcoinQt manually, let it do its thing
3) Delete Armory's DB and rebuild from scratch
|
|
|
|
Funny Armory doesn't check that on startup (something like multiple instances running error would be nice  That's planned for the next version |
|
|
|
|
Make sure there is no ArmoryDB process running, then delete the databases folder and try again. If that fails, post dbLog.txt.
|
|
|
|
|
Show Posts
