My recovered WALLET file are 28kb is that the only file I need? Sorry for being such a noob  Yes. Import it in Armory or copy it into your datadir |
|
|
|
|
1) You should always have a backup.
2) You only need the first 256 bytes or so of the wallet file to recover the encrypted root key. If you got a file that is about that long, use the wallet recovery tool in Armory and hope for the best.
3) If you manage to recover your wallet, make a backup =)
|
|
|
|
|
Tx was broadcasted, something GUI element failed after that.
|
|
|
|
|
Does it work with Core? There is no reason it shouldn't work with Classic, it's the same file structure and magic word.
|
|
|
|
Is there a way to determine the size of the transaction in Armory before finalizing its generation? If not, is that something that can somehow be incorporated into the next release (user-friendly) since transaction fees are critical nowadays for a successful transmission?
I'll be adding that at some point in the upcoming release. |
|
|
|
I noticed that Armory was removed from bitcoin.org recommended clients list. It's becasue of such overwhelming user-friendliness, or there is something more behind it?
It was removed because my fork is not the official work from ATI, nor does ATI offer links to my versions on their web page. At the same time, I don't have a web page, I just deliver my binaries through the github release feature. In other words, they think the situation is confusing. |
|
|
|
Free space at last! Free space at last!
Upgrade to 0.94 |
|
|
|
|
rebuild & rescan then try again
|
|
|
|
|
You can empty it or remove it. Ideally you want to back up the old DB in case 0.94 gives you a headache, but so far it has proven to be stable so you should be able to go all the way with this.
I'm adding a DB version check in the next release so this kind of issues don't happen anymore.
|
|
|
|
|
Let bitcoin resync first.
If you are experience issues with Armory controlling bitcoind, first backup your bitcoin datadir. Then turn off auto managed bitcoind in Armory (first check box in the File -> Settings menu) and run Bitcoin-Qt manually instead.
Once bitcoin is synced, you will have to do a rebuild & rescan in Armory to get it working. Also, do not let 0.94 run in the same dbdir as 0.93's.
|
|
|
|
|
need armorycpplog.txt as well
|
|
|
|
Here is a new log file. The log is too big and pastbin will not accept it. I hope this site works for you. http://filebin.ca/2lFIroguz2BW/armorylog_20160617_0837.txtadding these lines to bitcoin.conf rpcport=8333 rpcconnect=127.0.0.1 results in armory not being able to start bitcoind and a new error however using rpcport=8332(the defalt) allows bitcoind to start. Is there anyway to make armory use the 8332 port? bitcoin-cli can connect on the 8332 port. My bitcoin.conf file does contain 2 lines added by armory rpcuser=generated_by_armory rpcpassword= *****Random text here******* running armory as root has no effect so I do not believe it is a permission thing, unless armory auto drops root permission. Any help would be nice as I have some funds tied up in this wallet at the moment. I have found a Solution. Manually starting bitcond with the 8332 port and in armory unchecking "Let Armory run Bitcoin-Core in the background" allowed armory to connect. It would be nice if armory could handle bitcoind for me but not that big a deal. You shouldn't set your RPC port to 8333, that's the P2P port. |
|
|
|
|
log files.
also, most likely a permission issue.
|
|
|
|
|
Can't see the log file on that site, please use pastebin instead.
The connection is Armory trying to get ahold of your bitcoin node through p2p. It needs to be able to talk to localhost:8333. Either that or you didn't point it at the correct blockchain data folder (use --satoshi-datadir)
|
|
|
|
Sorry I haven't replied. I think its resolved now. One observation I saw was when I originally installed 0.94.1 and created a new wallet, the wallet size seems to be unusually (255Kb) large. Even the backup wallet is this large. There was 10 receiving addresses and perhaps only a dozen transactions. Things I've tried: 1) Relocating armory datadir to another drive. 2) Repairing wallet which indicated no errors. 3) Reinstalling Armory ( https://github.com/goatpig/BitcoinArmory/releases/tag/v0.94.1) Finally what I did was uninstall every damn thing, Armory and Bitcoin core. Reinstall (default locations) and reindex everything (Bitcoin blockchain and Armoy db) and new wallet again. Finally seems to be ok now. Conclusion, I've no idea why it's ok now  , however to all who read this I don't think its an issue with Armory. The wallets you restore from a root are larger than wallets you just create. Created wallets have 100 address precomputed, restored wallets precompute 1000 addresses, thus the size difference. Thinking about it, maybe your issue is permission access. If you were using a custom folder for your datadir and the user you were logged on as did not have credentials to access the path, it would have the data in RAM but fail to write it to disk. Although I expect the errors in the log file to be clearly signify this, so this doesn't exclude some sort of RAM or HDD issue. |
|
|
|
Is this a known problem with the armory wallet?
First time I see this. That code hasn't changed in 3 years or so, if it was common we'd know by now. |
|
|
|
There was an error constructing your transaction, due to a quirk in the way Bitcoin transactions work. If you see this error more than once, try sending your BTC in two or more separate transactions if len(utxoSelect) == 0:
QMessageBox.critical(self, tr('Coin Selection Error'), tr("""
There was an error constructing your transaction, due to a
quirk in the way Bitcoin transactions work. If you see this
error more than once, try sending your BTC in two or more
separate transactions."""), QMessageBox.Ok)
return False
This is the error it is referring to. In other words, it fails to select utxos to create your transaction, which suggest your outputs are all zero confirmed (or they are immature coinbase). Also, are you trying to spend all your coins in one go? Is Core suggesting a big fee? The only way I could get Armory to work, after trying all the methods described here, was to start Bitcoin Core first, then start armory with the setting for "Allow Armory to manage bitcoinqt" unchecked. Worked beautifully for a few days. That's the mode I recommend (self managed BitcoinQt). I only tolerate bitcoind auto management because it has been there long enough people are used to it (and expect it). It's the source of about 80% of all errors with Armory. EDIT: Rescanning made no difference. Rebuild? Rebuild what, the blockchain download? I sure hope that's not what you mean. It took me a WEEK to get the whole thing.
Rebuild & rescan the Armory DB, what you are talking about is a blockchain redownload. Look in the help menu, should be below rescan. |
|
|
|
|
Show Posts
