|
Title: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 19, 2014, 10:43:50 PM Please Help Test Armory 0.91-beta!
This new version has a ton of new stability and performance improvements. Including a fix for most users that had crashes at 99% scanning! GPG signature of hashes at the bottom Armory 0.90.99.7-testing for Ubuntu/Debian 64-bit* (https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.7-testing_64bit.deb) 761e4aaf285b28c530a34f522d487ada88733607e297ec7bd61ab7f163738dac Armory 0.90.99.7-testing for Ubuntu/Debian 32-bit* (https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.7-testing_32bit.deb) a89fb24c98d88e991b96d309d2890c285e0012fd4eac6ec3e9b31c3f0e5eb4f9 Armory 0.90.99.7-testing for Windows (including XP!) (https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.7-testing_winAll.exe) c797a9e08e8d845bb085dd45d86d2d82b9911db735e276ff9e7cc85ce4c7ba87 Armory 0.90.99.7-testing for MacOSX (https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.7-testing_osx.tar.gz) 1bbac95eb56046b86cf63b96c0957da6a4dbee9bbf1ca2836a70d517b4534b65 Armory 0.90.99.7-testing for Raspberry Pi (raspbian; armhf) (https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.7-testing_raspbian.tar.gz) 076368590875b4ff2faf1446a4aa1aec4fd94abe0790caf0f323ba703fc5f836 *Apparently we have broken Python2.6 support with this release, and so cannot make a version (yet) that is compatible with older versions of Ubuntu like 10.04. We are working on that... New stuff in 0.90.99.5-testing:
A few points to emphasize:
Recently identified:
If you get this testing version, this should be the last time you need to use GPG to verify Armory installers! Here's the Bitcoin keys we will use for signing announcements and downloads from the secure downloader -- they are hardcoded in the Armory source: 1NWvhByxfTXPYNT4zMBmEY3VL8QJQtQoei (https://github.com/etotheipi/BitcoinArmory/blob/0.91-dev/armoryengine/ArmoryUtils.py#L51) (offline key) 1PpAJyNoocJt38Vcf4AfPffaxo76D4AAEe (https://github.com/etotheipi/BitcoinArmory/blob/0.91-dev/announcefetch.py#L20) (online testing key) Until you get the new version, here is a GPG-signed copy of the 0.90.99.7 Code: -----BEGIN PGP SIGNED MESSAGE----- Version 0.91 automatically identifies messages that match the key and explicitly tell you it's signed by "Armory Technologies, Inc". It's only if you're using an older version that you have manually verify the address. Here's what it looks like in 0.91: https://dl.dropboxusercontent.com/u/1139081/BitcoinImg/verifysigblock_0.91.png We will have OSX and Linux versions posted soon. Some recent changes we made broke our build/release system -- it seems to work for local compiling, but building distributable packages is broken and hopefully fixed later today. Title: Re: Please Help Test Armory 0.91-beta! Post by: LOL on March 20, 2014, 04:58:51 AM Quick bug report:
It appears as if I'm unable to open the "Transaction Info" popup on transactions that have a P2SH output as is standard in mastercoin transactions. In previous releases, the P2SH output was just marked as (I believe it was) "strange." It's not a huge deal considering that no wallet recognizes or can spend those outputs anyway, but it would be nice if the popup worked. Here's an example: Code: OP_1 <pubkey1> <pubkey2> OP_2 OP_CHECKMULTISIG https://blockchain.info/tx/cba042a1e4b4b072084c06e94f84843cdbd17a30f13dd038fabca67baeb20b53 Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 20, 2014, 05:03:20 AM Quick bug report: It appears as if I'm unable to open the "Transaction Info" popup on transactions that have a P2SH output as is standard in mastercoin transactions. In previous releases, the P2SH output was just marked as (I believe it was) "strange." It's not a huge deal considering that no wallet recognizes or can spend those outputs anyway, but it would be nice if the popup worked. Here's an example: Code: OP_1 <pubkey1> <pubkey2> OP_2 OP_CHECKMULTISIG https://blockchain.info/tx/cba042a1e4b4b072084c06e94f84843cdbd17a30f13dd038fabca67baeb20b53 Yes, I added P2SH support throughout the interface. I'm surprised it doesn't work because I did spend a quite bit of time testing that. Anything interesting in the log file? EDIT: I actually see that tx is unconfirmed and I just remembered seeing a bug with unconfirmed transactions a while back. Can you just check again after it's got one confirmation? Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 20, 2014, 05:20:05 AM Quick bug report: It appears as if I'm unable to open the "Transaction Info" popup on transactions that have a P2SH output as is standard in mastercoin transactions. In previous releases, the P2SH output was just marked as (I believe it was) "strange." It's not a huge deal considering that no wallet recognizes or can spend those outputs anyway, but it would be nice if the popup worked. Here's an example: Code: OP_1 <pubkey1> <pubkey2> OP_2 OP_CHECKMULTISIG https://blockchain.info/tx/cba042a1e4b4b072084c06e94f84843cdbd17a30f13dd038fabca67baeb20b53 Figured it out! It's because that's not actually P2SH, it's a plain multi-sig address. P2SH is one way to execute multisig scripts, but it's not used in the transaction you linked. I would totally believe that I broke multisig display because I didn't test that. Whoops! I'll see if I can get it back to the way it was before. P.S. - Just posted an Ubuntu 64-bit installer for testing... Title: Re: Please Help Test Armory 0.91-beta! Post by: LOL on March 20, 2014, 06:24:13 AM Figured it out! It's because that's not actually P2SH, it's a plain multi-sig address. P2SH is one way to execute multisig scripts, but it's not used in the transaction you linked. I would totally believe that I broke multisig display because I didn't test that. Whoops! I'll see if I can get it back to the way it was before. P.S. - Just posted an Ubuntu 64-bit installer for testing... Sorry about that. I actually realized right after that post that I'd been using P2SH interchangeably with multisig in a multitude of places recently. I suppose I'll live with the embarrassment. But while we're on the subject of multisig, do you mind commenting on the feasibility of a wallet recognizing strange outputs as spendable? That's a pretty broad question, but I didn't want to narrow it down so far as to only be applicable to the multisig example I provided. The reason I ask is largely due to mastercoin. Mastercoin uses 1-of-n multisig outputs as a method of storing data in the blockchain without creating unspendable outputs. The catch is that there isn't a wallet that will recognize or spend those outputs. As far as I'm concerned, they are unspendable by the average user. Anyway, do you find reason or incentive to recognize and support fringe case outputs such as the one in the example? If so, would you consider pursuing a wallet model that aims to recognize and spend all outputs that can be spent? Please note, this isn't a request - I'm just curious what a developer's thoughts are. Thank you for the awesome work on Armory! I'm excited to use Armory over the coming months. Title: Re: Please Help Test Armory 0.91-beta! Post by: Automatic on March 20, 2014, 07:09:36 AM Am I glad I backed up my wallets, I launched it to the majority of my comments being wiped out:-
https://i.imgur.com/pkyy1zr.png Every single one of them had a comment before. EDIT:- And one of my bitcoin wallets (of four, not the one that had all it's transaction comment's lost) is also corrupt (Not surprisingly, I manually hex edited this one):- https://i.imgur.com/ouLJsBB.png EDIT2:- Deleted and imported wallet, nothing of interest:- Code: 2014-03-20 07:18 (INFO) -- qtdialogs.pyc:4386 - ***Completely deleting wallet EDIT2:- Can't even downgrade now without Armory crashing. *Yay*, rebuilding databases. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 20, 2014, 07:25:45 AM The missing comments, are they Tx or Address comments?
Title: Re: Please Help Test Armory 0.91-beta! Post by: Automatic on March 20, 2014, 07:27:33 AM The missing comments, are they Tx or Address comments? Address comments are still there, transaction ones are gone. Title: Re: Please Help Test Armory 0.91-beta! Post by: Finnminer on March 20, 2014, 07:54:49 AM OMG, it's actually working! :o For the first time in ages I have a properly working Armory!
I've had a ton of different problems before. They're all gone now. Great job guys! Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 20, 2014, 08:16:45 AM The missing comments, are they Tx or Address comments? Address comments are still there, transaction ones are gone. Do you have an approximate idea of how many comments were in your wallet? The wallet recovery tool displays that so you can compare, and let me know the comments are just gone or if its Armory not displaying them. OMG, it's actually working! :o For the first time in ages I have a properly working Armory! I've had a ton of different problems before. They're all gone now. Great job guys! Not quite done with the ledger fixing yet but I'm glad to hear it works so far. Title: Re: Please Help Test Armory 0.91-beta! Post by: Automatic on March 20, 2014, 09:13:56 AM The missing comments, are they Tx or Address comments? Address comments are still there, transaction ones are gone. Do you have an approximate idea of how many comments were in your wallet? The wallet recovery tool displays that so you can compare, and let me know the comments are just gone or if its Armory not displaying them. Armory 0.90-beta, all 128 of my transactions have notes (In the UI). Armory 0.90.99.3-testing:- You lie, nowhere on the UI could I find it telling me, except for this in the log, which, doesn't specify if they're address or transaction comments:- 284 chain addresses, 0 imported keys and 324 comments were found Although, 284 (Addresses) + 128 (Comments from .90-beta) = 412 ~ 324 comments found (Well, closer than any other numbers. Although, just hex editing the .wallet I can't seem to find any blocks starting with 0x02 (Transaction comment), just 0x01, although, I'm not really the best at parsing files (Just skimming over it). If you give me a minute, I'll throw something together quickly to parse it. Title: Re: Please Help Test Armory 0.91-beta! Post by: Finnminer on March 20, 2014, 09:21:06 AM Not quite done with the ledger fixing yet but I'm glad to hear it works so far. Yeah, I added another wallet that has a large amount of pooled mining transactions and Armory became pretty unresponsive. But it's not crashing so I can live with for now.Title: Re: Please Help Test Armory 0.91-beta! Post by: Automatic on March 20, 2014, 09:41:49 AM Okay, threw this together:-
http://pastebin.com/raw.php?i=YcX5b2rR Not the best code (Actually, results in "Corrupt wallet!" about half the way down the wallet), but, it's 9:30AM, and, it's just going to be used for this, so, what does it matter? I believe that's the format of your wallet (You may want to verify it, which is why I posted it), but, it results in:- Code: Address:- {MyFirstEverAddressComment}So, I'm going to say yes, there are transactions in that wallet, although, the wallet does fuck up my program (Although, that's probably my shoddy 9:30AM programming), so, it may just slightly be corrupt (But, then again, your previous version of Armory (Which I just downgraded to, and, it works fine), still accepts it, so, obviously it's something you've changed between the two versions. How fun.). Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 20, 2014, 10:09:09 AM I can't reproduce the comment issue on my end. Try this:
1) Load you wallet in Armory offline. 2) Restore it from paper. This will rip the meta data from the wallet if it's currently loaded. 3) Load the restored wallet and see if the comments show up Title: Re: Please Help Test Armory 0.91-beta! Post by: digipl on March 20, 2014, 11:16:21 AM In windows 7-64 the problems persist.
The first time I run the program, slow scanning and freezes before finish. The next times the scanning is faster and I can see my balances but the programs freeze again. The process service show that Armory steal alive and consume 25% of my CPU but I cannot do anything except finish process (I will try wait several hours). In my case the only version who works is the 0.88.1. All the 0.9 versions I try, freeze or broke. In this situation even I cannot send a bug reporting. Title: Re: Please Help Test Armory 0.91-beta! Post by: Automatic on March 20, 2014, 11:20:47 AM I can't reproduce the comment issue on my end. Try this: 1) Load you wallet in Armory offline. 2) Restore it from paper. This will rip the meta data from the wallet if it's currently loaded. 3) Load the restored wallet and see if the comments show up Issue with that is it's an offline wallet, I don't really want to restore it from paper to my online computer. Can I just use a digital backup (Watch-only) from my offline computer? Or is there some way to do that without using the paper backup? Title: Re: Please Help Test Armory 0.91-beta! Post by: Sukrim on March 20, 2014, 03:19:14 PM Why is the torrent created as "private" (no DHT, no PEX...) and not just the one jgarzik published (https://bitcointalk.org/index.php?topic=145386.0), which is already quite well seeded? You make it much harder than you need to for others to help seeding.
Also your tracker (tracker.bitcoinarmory.com) is a single point of failure that way, without it your users will NOT be able to find each other. If you want a more recent bootstrap file, maybe suggest a change to https://github.com/bitcoin/bitcoin/blob/master/src/checkpoints.cpp but please at least make your torrent public, so people can find each other via DHT, LPD and PEX too. Title: Re: Please Help Test Armory 0.91-beta! Post by: CircusPeanut on March 20, 2014, 03:36:06 PM In case you have trouble cutting and pasting the signature into the Verify Signed Message Block window, just "Quote" the message as if you want to respond to it, and cut and paste from the editor.
Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 20, 2014, 03:54:11 PM But while we're on the subject of multisig, do you mind commenting on the feasibility of a wallet recognizing strange outputs as spendable? That's a pretty broad question, but I didn't want to narrow it down so far as to only be applicable to the multisig example I provided. The reason I ask is largely due to mastercoin. Mastercoin uses 1-of-n multisig outputs as a method of storing data in the blockchain without creating unspendable outputs. The catch is that there isn't a wallet that will recognize or spend those outputs. As far as I'm concerned, they are unspendable by the average user. Anyway, do you find reason or incentive to recognize and support fringe case outputs such as the one in the example? If so, would you consider pursuing a wallet model that aims to recognize and spend all outputs that can be spent? Please note, this isn't a request - I'm just curious what a developer's thoughts are. The answer to your question is basically: determining spendability of an arbitrary script is an intractible problem. I'm sure it's related to the halting problem (http://en.wikipedia.org/wiki/Halting_problem). Either way, the only way to do this is to simply identify a set of scripts templates and conditions that we know are spendable, and code those directly into the app. When we have a multi-sig solution in Armory, it would be easy to automatically recognize such 1-of-N scripts as spendable. But tying that into the interface may be complex: do we really show those tx as spendable money the same as all the regular single-sig money? It's in a 1-of-N for a reason, maybe it should be identified separately, in which case we need to show that in a different interface or in a different way. Etc. On that note, do you have a watching-only wallet that I could use to test the multi-sig thing. I went to go fix it, and then realized I don't have a good way to get multisig address into any of my wallets. Once i have one, I can fix the display problem pretty fast. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 20, 2014, 04:10:31 PM Why is the torrent created as "private" (no DHT, no PEX...) and not just the one jgarzik published (https://bitcointalk.org/index.php?topic=145386.0), which is already quite well seeded? You make it much harder than you need to for others to help seeding. Also your tracker (tracker.bitcoinarmory.com) is a single point of failure that way, without it your users will NOT be able to find each other. If you want a more recent bootstrap file, maybe suggest a change to https://github.com/bitcoin/bitcoin/blob/master/src/checkpoints.cpp but please at least make your torrent public, so people can find each other via DHT, LPD and PEX too. The torrent library we found (BitTornado) is kind of old and doesn't support DHT. We setup the tracker to accommodate this, and our guy actually found a way to bridge the peer swarms using a tracker compatible with this library (assuming we're using the same torrent, which we will when new official ones are released). We had to make the appropriate design decisions: BitTornado worked flawlessly out of the box on all OS, pure-python, and stupid-easy to integrate. It was more work to change BitTornado than it was to simply do it this way. One problem with the official one is that it's not updated regularly. Until Core 0.9.0, the checkpoints are 3 months behind, and so is the torrent. We wanted to make sure we can provide a more-frequently-updated torrent, as "topping off" the blockchain after bootstrapping appears to be a huge bottleneck. For me, using the old torrent required 2 hours of bootstrapping and 2-3 hours of "topping off". With the newer torrents, it's 2-3 hours total. We're already setting up all the peers to do it, we wanted to optimize that. We have a variety of seedboxes setup across a dozen services to guarantee that our peer swarm is flexible and robust to any one (or 5) service providers going down. I understand the tracker thing, and it's in our plan to get a couple more, setup the same way to add extra robustness. But in the end, it's not really a single point of "failure", because Armory will fall back on regular P2P download if torrent doesn't work. Worst case is status quo. Title: Re: Please Help Test Armory 0.91-beta! Post by: Sukrim on March 20, 2014, 04:24:53 PM https://github.com/etotheipi/BitcoinArmory/blob/0.91-dev/default_bootstrap.torrent is the one I'm talking about and this file being a private torrent has nothing to do with which client you use. You created it with Transmission 2.51 and set this option apparently (knowingly or unknowingly: http://www.bittorrent.com/help/manual/appendixa0403#Other.Private_torrent).
Your client might not support DHT, but it likely supports PEX. This already would be enough to bridge swarms or extend them if the tracker is down, as long as they are able to find a single peer. Also it does not hurt to enter a larger list of trackers in the file, there are a few open ones still around. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 20, 2014, 04:37:10 PM I can't reproduce the comment issue on my end. Try this: 1) Load you wallet in Armory offline. 2) Restore it from paper. This will rip the meta data from the wallet if it's currently loaded. 3) Load the restored wallet and see if the comments show up Issue with that is it's an offline wallet, I don't really want to restore it from paper to my online computer. Can I just use a digital backup (Watch-only) from my offline computer? Or is there some way to do that without using the paper backup? I added this feature to save meta data on restores only. I should also add a way to just rip a wallet's meta data in a separate file, but I don't think that'll fit in 0.91 schedule's. If you use Linux and are willing to pull a side branch, We can work something and you be my guinea pig =P. However that will have to wait a few days, still working on the ledger entry issue. Currently you could move the WO to your offline Armory, and restore from there. This feature isn't meant to work with digital imports. Maybe it should. Title: Re: Please Help Test Armory 0.91-beta! Post by: Kluge on March 20, 2014, 04:42:25 PM At wallet corruption detection, should you choose to fix and need to unlock, Armory will not prompt again if an incorrect password is entered, simply note the error and present no option but to close the window. Would be nice if Armory presented the wallet name instead of ID tag there, too. As if I have any bloody idea what the password to 3CU1BLUti is... :P
Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 20, 2014, 05:04:01 PM At wallet corruption detection, should you choose to fix and need to unlock, Armory will not prompt again if an incorrect password is entered, simply note the error and present no option but to close the window. Would be nice if Armory presented the wallet name instead of ID tag there, too. As if I have any bloody idea what the password to 3CU1BLUti is... :P Thanks for the report, I'll get on it soon. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 20, 2014, 05:40:53 PM Goatpig just pushed a change that might push people through the BDM-timeout barrier if they have these wallets with huge numbers of large transactions. Curious how the performance is after it gets past the synchronization, but at least you should get through it.
Zoella, rocks*, if you can, please checkout the latest 0.91-dev, make clean and make, then try it with your large wallets that were crashing (assuming you are on Linux... if not, we'll make a windows version after we know this solves it) Title: Re: Please Help Test Armory 0.91-beta! Post by: Rock6.3 on March 20, 2014, 06:44:12 PM Goatpig just pushed a change that might push people through the BDM-timeout barrier if they have these wallets with huge numbers of large transactions. Curious how the performance is after it gets past the synchronization, but at least you should get through it. Zoella, rocks*, if you can, please checkout the latest 0.91-dev, make clean and make, then try it with your large wallets that were crashing (assuming you are on Linux... if not, we'll make a windows version after we know this solves it) Windows7 here. Title: Re: Please Help Test Armory 0.91-beta! Post by: Zoella on March 20, 2014, 10:41:01 PM Goatpig just pushed a change that might push people through the BDM-timeout barrier if they have these wallets with huge numbers of large transactions. Curious how the performance is after it gets past the synchronization, but at least you should get through it. Zoella, rocks*, if you can, please checkout the latest 0.91-dev, make clean and make, then try it with your large wallets that were crashing (assuming you are on Linux... if not, we'll make a windows version after we know this solves it) Booting VM, will get back to you soon! Title: Re: Please Help Test Armory 0.91-beta! Post by: Zoella on March 20, 2014, 11:12:39 PM Goatpig just pushed a change that might push people through the BDM-timeout barrier if they have these wallets with huge numbers of large transactions. Curious how the performance is after it gets past the synchronization, but at least you should get through it. Zoella, rocks*, if you can, please checkout the latest 0.91-dev, make clean and make, then try it with your large wallets that were crashing (assuming you are on Linux... if not, we'll make a windows version after we know this solves it) Booting VM, will get back to you soon! Yay, it's working! Woohoo! Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 20, 2014, 11:13:20 PM Goatpig just pushed a change that might push people through the BDM-timeout barrier if they have these wallets with huge numbers of large transactions. Curious how the performance is after it gets past the synchronization, but at least you should get through it. Zoella, rocks*, if you can, please checkout the latest 0.91-dev, make clean and make, then try it with your large wallets that were crashing (assuming you are on Linux... if not, we'll make a windows version after we know this solves it) Booting VM, will get back to you soon! Yay, it's working! Woohoo! Wow finally... Let us know if there is an overall slowness feeled after the initial load. Oh and slam it with nastier wallets if you have any. Title: Re: Please Help Test Armory 0.91-beta! Post by: Zoella on March 20, 2014, 11:22:28 PM Goatpig just pushed a change that might push people through the BDM-timeout barrier if they have these wallets with huge numbers of large transactions. Curious how the performance is after it gets past the synchronization, but at least you should get through it. Zoella, rocks*, if you can, please checkout the latest 0.91-dev, make clean and make, then try it with your large wallets that were crashing (assuming you are on Linux... if not, we'll make a windows version after we know this solves it) Booting VM, will get back to you soon! Yay, it's working! Woohoo! Wow finally... Let us know if there is an overall slowness feeled after the initial load. Oh and slam it with nastier wallets if you have any. Actually faster than I have ever seen it. Actually faster than with NO wallet. https://blockchain.info/tx/c0e8be9ee6db4472454fbaee30bdf85a2245f429b18747e784c9aa33fd2e0cd4 Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 20, 2014, 11:26:27 PM Actually faster than I have ever seen it. Actually faster than with NO wallet. https://blockchain.info/tx/c0e8be9ee6db4472454fbaee30bdf85a2245f429b18747e784c9aa33fd2e0cd4 That's a little scary but alright. Thanks for the donation. I get you had no issues sending either? Title: Re: Please Help Test Armory 0.91-beta! Post by: Zoella on March 20, 2014, 11:31:39 PM Actually faster than I have ever seen it. Actually faster than with NO wallet. https://blockchain.info/tx/c0e8be9ee6db4472454fbaee30bdf85a2245f429b18747e784c9aa33fd2e0cd4 That's a little scary but alright. Thanks for the donation. I get you had no issues sending either? Nope. And to be 100% honest, this really is performing faster than any time I have ever used it. Beyond actually working, there really is a noticeable performance improvement over initial installs with only a couple of small wallets. I now have 4 wallets restored, and it is running faster than times when I have restored a single wallet with only a couple of normal transactions for testing. Definitely make sure this fix gets into the new version! EDIT: I will note that when I initially loaded the watching-only wallet it worked, but no transactions were displayed (same version I sent you). I removedit and loaded the regular wallets, and all transactions were visible. Not sure what happened there. Maybe just a fluke, or maybe something worth checking out. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 21, 2014, 12:26:59 AM Nope. And to be 100% honest, this really is performing faster than any time I have ever used it. Beyond actually working, there really is a noticeable performance improvement over initial installs with only a couple of small wallets. I now have 4 wallets restored, and it is running faster than times when I have restored a single wallet with only a couple of normal transactions for testing. Definitely make sure this fix gets into the new version! EDIT: I will note that when I initially loaded the watching-only wallet it worked, but no transactions were displayed (same version I sent you). I removedit and loaded the regular wallets, and all transactions were visible. Not sure what happened there. Maybe just a fluke, or maybe something worth checking out. I think the speed up is to be credited to njaard and etotheipi work on optimizing the DB. As for the transactions, did you pick show all wallets in the drop down combo box? Some people have it defaulted to "my wallet" and that won't show you transactions for any wallet that you didn't mark as yours. Title: Re: Please Help Test Armory 0.91-beta! Post by: LOL on March 21, 2014, 12:58:09 AM But while we're on the subject of multisig, do you mind commenting on the feasibility of a wallet recognizing strange outputs as spendable? That's a pretty broad question, but I didn't want to narrow it down so far as to only be applicable to the multisig example I provided. The reason I ask is largely due to mastercoin. Mastercoin uses 1-of-n multisig outputs as a method of storing data in the blockchain without creating unspendable outputs. The catch is that there isn't a wallet that will recognize or spend those outputs. As far as I'm concerned, they are unspendable by the average user. Anyway, do you find reason or incentive to recognize and support fringe case outputs such as the one in the example? If so, would you consider pursuing a wallet model that aims to recognize and spend all outputs that can be spent? Please note, this isn't a request - I'm just curious what a developer's thoughts are. The answer to your question is basically: determining spendability of an arbitrary script is an intractible problem. I'm sure it's related to the halting problem (http://en.wikipedia.org/wiki/Halting_problem). Either way, the only way to do this is to simply identify a set of scripts templates and conditions that we know are spendable, and code those directly into the app. When we have a multi-sig solution in Armory, it would be easy to automatically recognize such 1-of-N scripts as spendable. But tying that into the interface may be complex: do we really show those tx as spendable money the same as all the regular single-sig money? It's in a 1-of-N for a reason, maybe it should be identified separately, in which case we need to show that in a different interface or in a different way. Etc. On that note, do you have a watching-only wallet that I could use to test the multi-sig thing. I went to go fix it, and then realized I don't have a good way to get multisig address into any of my wallets. Once i have one, I can fix the display problem pretty fast. Thanks for humoring my question. I'll PM you. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 21, 2014, 04:45:57 AM Testing version 0.90.99.4 for Windows, Mac and Linux*
*Any linux with python2.6 is still borked. However this package should work on any linux system with python 2.7 (we thought we'd found a way to compile universal installers, and we did...as long as it uses the same python version... we think...). YES Mac version compiled and seems to be working! YES The crashing at 99% done scanning seems to be fixed! Offline-signed announce data. No longer need --test-announce for torrent and secure downloading Downloads and info in the top post. Title: Re: Please Help Test Armory 0.91-beta! Post by: gweedo on March 21, 2014, 05:08:30 AM Bug Mac OSX 10.9.2
Code: 2014-03-21 01:06 (ERROR) -- Traceback (most recent call last): Title: Re: Please Help Test Armory 0.91-beta! Post by: Subo1977 on March 21, 2014, 06:23:03 AM WOW .
I had the same Problem with Crash/Freezes in <=0.90.99.4-testing and 0.9 under 0.90.99.4-testing it works fine :-) Thanks Title: Re: Please Help Test Armory 0.91-beta! Post by: Finnminer on March 21, 2014, 08:52:26 AM Testing version 0.90.99.4 for Windows, Mac and Linux* I can confirm that this makes a huge difference compared to 0.90.99.3. The wallet that made the previous version unusably slow now works with almost no slowing down. Also the startup is now crazy fast. Almost a hundredfold increase in startup speed compared to any previous version I've used.But there's a problem with sending from the problematic wallet. I tried to make a donation to you guys but it always fails. I can't send coins to any other address from it either. Sending from my offline wallet works perfectly though. I tried broadcasting the transaction using blockchain.info, but it says that "An outpoint is already spent". Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 21, 2014, 10:38:44 AM Testing version 0.90.99.4 for Windows, Mac and Linux* I can confirm that this makes a huge difference compared to 0.90.99.3. The wallet that made the previous version unusably slow now works with almost no slowing down. Also the startup is now crazy fast. Almost a hundredfold increase in startup speed compared to any previous version I've used.But there's a problem with sending from the problematic wallet. I tried to make a donation to you guys but it always fails. I can't send coins to any other address from it either. Sending from my offline wallet works perfectly though. I tried broadcasting the transaction using blockchain.info, but it says that "An outpoint is already spent". Need your log file for to look at the send issue please. Edit: This could be related to a spent output with the wallet. You should rescan the transactions. No need to rebuild though. I expect the balance will change after the rescan. Title: Re: Please Help Test Armory 0.91-beta! Post by: Zoella on March 21, 2014, 11:48:20 AM <snip> I think the speed up is to be credited to njaard and etotheipi work on optimizing the DB. As for the transactions, did you pick show all wallets in the drop down combo box? Some people have it defaulted to "my wallet" and that won't show you transactions for any wallet that you didn't mark as yours. No idea. I was so shocked I could still move around in the application after transaction scanning was complete, I didn't really spend any time troubleshooting. After about 5 seconds of clicking on things and having them react I shut down and removed the wallet, added others and restarted. It very well may have been user error. Title: Re: Please Help Test Armory 0.91-beta! Post by: Finnminer on March 21, 2014, 11:55:34 AM Edit: This could be related to a spent output with the wallet. You should rescan the transactions. No need to rebuild though. I expect the balance will change after the rescan. Yes, that solved it. I'm happy to report that every single issue I've had (and I've had many) is now resolved. :)https://blockchain.info/tx/dbeaf256a65a95d532ded05526e7eb874e02339f252124edc42cb3bdf2547bef Title: Re: Please Help Test Armory 0.91-beta! Post by: Subo1977 on March 21, 2014, 03:37:55 PM i found a bug in 0.90.99.4 :
After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync) i make a tx and wonder why 0 confirms after 1 Hour. on BC.i the tx confirm is 10 After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart. Greets Title: Re: Please Help Test Armory 0.91-beta! Post by: CircusPeanut on March 21, 2014, 03:59:03 PM i found a bug in 0.90.99.4 : After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync) i make a tx and wonder why 0 confirms after 1 Hour. on BC.i the tx confirm is 10 After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart. Greets Thanks for the report! Please go to Help -> Submit Bug Report Armory will send us everything we need to investigate this bug. Title: Re: Please Help Test Armory 0.91-beta! Post by: Rock6.3 on March 21, 2014, 04:14:12 PM My Armory wallet is finally working again!
Updated to the 0.90.99.4 Beta Updated my BitcoinQT then started Armory Building Databases took 7 minutes Scanning Transaction History took 1 Hour Odd behavior: Just before the 'Scanning Transaction History' completed it changed the time estimate to '16 years'. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 21, 2014, 04:20:42 PM Edit: This could be related to a spent output with the wallet. You should rescan the transactions. No need to rebuild though. I expect the balance will change after the rescan. Yes, that solved it. I'm happy to report that every single issue I've had (and I've had many) is now resolved. :)https://blockchain.info/tx/dbeaf256a65a95d532ded05526e7eb874e02339f252124edc42cb3bdf2547bef Thx for the tip =) i found a bug in 0.90.99.4 : After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync) i make a tx and wonder why 0 confirms after 1 Hour. on BC.i the tx confirm is 10 After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart. Greets Will take a look at this, thx for the report My Armory wallet is finally working again! Updated to the 0.90.99.4 Beta Updated my BitcoinQT then started Armory Building Databases took 7 minutes Scanning Transaction History took 1 Hour Odd behavior: Just before the 'Scanning Transaction History' completed it changed the time estimate to '16 years'. During blockchain build and tx scan, the backend report it's progress to the front end. Now that the wallet ledger pre load is ran from the backend, it lacks the progress reporting. The front end then assumes it's gonna "that" long to get anywhere, as it's not seeing any reports further down the road. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 21, 2014, 04:50:24 PM i found a bug in 0.90.99.4 : After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync) i make a tx and wonder why 0 confirms after 1 Hour. on BC.i the tx confirm is 10 After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart. Greets My block count is updating just fine. Lemme see a log file. Can others confirm or infirm this behavior? Title: Re: Please Help Test Armory 0.91-beta! Post by: Rock6.3 on March 21, 2014, 05:04:50 PM i found a bug in 0.90.99.4 : After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync) i make a tx and wonder why 0 confirms after 1 Hour. on BC.i the tx confirm is 10 After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart. Greets My block count is updating just fine. Lemme see a log file. Can others confirm or infirm this behavior? After updating to new version and having only run Armory once today, and leaving it open, I now show: "Connected (291697 blocks)" Title: Re: Please Help Test Armory 0.91-beta! Post by: mashoo on March 21, 2014, 05:14:59 PM That's great Alan, we'll be eager to try it out!
Marshall Swatt CTO - Coinsetter, Inc. Title: Re: Please Help Test Armory 0.91-beta! Post by: Rock6.3 on March 21, 2014, 05:24:07 PM i found a bug in 0.90.99.4 : After sync at startup, there client didnt sync new incoming block's.( Bitcoin-qt is sync) i make a tx and wonder why 0 confirms after 1 Hour. on BC.i the tx confirm is 10 After armoryrestart and sync, the tx got confirmed.in the right corner stay "Connected" and Blockcount didnt change until next restart. Greets My block count is updating just fine. Lemme see a log file. Can others confirm or infirm this behavior? After updating to new version and having only run Armory once today, and leaving it open, I now show: "Connected (291697 blocks)" Update: My status is now "Connected (291699 blocks)" Thus the Armor is updating Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 21, 2014, 05:33:30 PM Quick bug report: It appears as if I'm unable to open the "Transaction Info" popup on transactions that have a P2SH output as is standard in mastercoin transactions. In previous releases, the P2SH output was just marked as (I believe it was) "strange." It's not a huge deal considering that no wallet recognizes or can spend those outputs anyway, but it would be nice if the popup worked. Here's an example: Code: OP_1 <pubkey1> <pubkey2> OP_2 OP_CHECKMULTISIG https://blockchain.info/tx/cba042a1e4b4b072084c06e94f84843cdbd17a30f13dd038fabca67baeb20b53 @LOL I just fixed the multisig display issue with a one-line change. All the code was already written and integrated, but I didn't account for the variable number of addresses/keys when analyzing a transaction with a multi-sig output. Will push the update shortly to 0.91-dev (in case you're impatient :)) https://dl.dropboxusercontent.com/u/1139081/BitcoinImg/multisigledgerdisp.png Title: Re: Please Help Test Armory 0.91-beta! Post by: simonk83 on March 22, 2014, 02:20:07 AM I'm getting this:
Code: Traceback (most recent call last): The previous version worked fine so not sure what that's about. Don't really know how to fix it either... Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 22, 2014, 02:39:28 AM I'm getting this: Code: Traceback (most recent call last): The previous version worked fine so not sure what that's about. Don't really know how to fix it either... Uhhh, gonna need more details. What OS and version? Did you build it yourself or use our package? Title: Re: Please Help Test Armory 0.91-beta! Post by: simonk83 on March 22, 2014, 02:58:22 AM I'm getting this: Code: Traceback (most recent call last): The previous version worked fine so not sure what that's about. Don't really know how to fix it either... Uhhh, gonna need more details. What OS and version? Did you build it yourself or use our package? Duh, sorry my bad! OSX (Mavericks), used the version in the first post of this thread. Title: Re: Please Help Test Armory 0.91-beta! Post by: BitAddict on March 22, 2014, 10:56:34 AM Finally! Thanks for the release, I will be testing it :)
Title: Re: Please Help Test Armory 0.91-beta! Post by: kerogre256 on March 22, 2014, 07:39:08 PM I just installed this version and Armory don't want go in to online mode, show armory offline mode and noting happend.
Title: Re: Please Help Test Armory 0.91-beta! Post by: kerogre256 on March 22, 2014, 07:42:14 PM I have Now wallet error found and armory fail to initiate bitcoin engine.
Title: Re: Please Help Test Armory 0.91-beta! Post by: Carlton Banks on March 22, 2014, 08:05:45 PM Coinbase transactions no longer respond to "Show Details" in 0.90.99.4. Don't know if that was the case in previous 0.91 test versions, as this is the first I've tried.
Title: Re: Please Help Test Armory 0.91-beta! Post by: kerogre256 on March 22, 2014, 08:12:01 PM 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully
2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1009 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1010 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1011 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************ 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************ 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine: 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1016 - Armory Version : 0.90.99.4 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1017 - PyBtcWallet Version : 1.35 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1019 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1020 - User home-directory : C:\Users\x\AppData\Roaming 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1021 - Satoshi BTC directory : C:\Users\x\AppData\Roaming\Bitcoin\ 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1022 - Armory home dir : C:\Users\x\AppData\Roaming\Armory\ 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs : 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1024 - Total Available RAM : 7.94 GB 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1025 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1026 - Number of CPU cores : 4 cores 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1027 - System is 64-bit : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1028 - Preferred Encoding : cp1252 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1029 - 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py: 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - maxOpenFiles : 0 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - nettimeout : 2 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rescan : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - leveldbDir : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - ignoreAllZC : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - port : None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - interport : 8223 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageOutputDir: None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rebuild : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - datadir : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - offline : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - noWalletCheck : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiPort : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - netlog : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - keypool : 100 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - coverageInclude : None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - forceOnline : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipAnnounceCheck: False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - redownload : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - disableTorrent : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testAnnounceCode: False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - mtdebug : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - skipVerCheck : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - settingsPath : C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - verbosity : None 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - doDebug : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - testnet : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - rpcport : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiHome : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - satoshiRpcport : DEFAULT 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logDisable : False 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1034 - logFile : C:\Users\x\AppData\Roaming\Armory\ArmoryQt.exe.log.txt 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments: 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************ 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully 2014-03-22 19:56 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager. 2014-03-22 19:56 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background. 2014-03-22 19:56 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data. 2014-03-22 19:56 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for 2014-03-22 19:56 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed. 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:3006 - Using settings file: C:\Users\x\AppData\Roaming\Armory\ArmorySettings.txt 2014-03-22 19:56 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory: 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - announce : 88f1e5b41f0a828a1ae440c0490e4136a848b4fc79fa4d41809d309eefc87712 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - bootstrap : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - changelog : d4072bb5c0037ad4bd551dec85601ed8ef1eae04780c08e69e28d62932900441 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - downloads : cec3a5c4381a82860162d9d7d913bda75d88f7b531d6d528620a5464c0020b3d 2014-03-22 19:56 (INFO) -- announcefetch.pyc:92 - notify : 20aa6e8a9d1f947c08f1b21a4c24d53e29b68c2d37b936a082d88192b2513fea 2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2211 - loadWalletsAndSettings 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2269 - Loading wallets... 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2318 - Number of wallets read in: 2 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (2vrvaaUvT): "Piotr " (No Encryption) 2014-03-22 19:56 (INFO) -- ArmoryQt.py:2323 - Wallet (tNKjfKT5): "Offline (Watch) " (No Encryption) 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1758 - Setting up networking... 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1810 - Internet connection is Available: True 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1811 - Bitcoin-Qt/bitcoind is Available: 0 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1812 - The first blk*.dat was Available: True 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1813 - Online mode currently possible: 0 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1932 - startBitcoindIfNecessary 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1972 - setSatoshiPaths 2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB 2014-03-22 19:56 (INFO) -- SDM.pyc:299 - Found bitcoind in the following places: 2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe 2014-03-22 19:56 (INFO) -- SDM.pyc:301 - C:\Program Files\Bitcoin\daemon\bitcoind.exe 2014-03-22 19:56 (INFO) -- SDM.pyc:303 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe 2014-03-22 19:56 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file 2014-03-22 19:56 (INFO) -- SDM.pyc:480 - Setting permissions on bitcoin.conf 2014-03-22 19:56 (INFO) -- SDM.pyc:483 - Setting permissions on bitcoin.conf 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['icacls', 'C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'x:F'] 2014-03-22 19:56 (INFO) -- SDM.pyc:486 - icacls returned: 2014-03-22 19:56 (INFO) -- SDM.pyc:547 - Called startBitcoind 2014-03-22 19:56 (INFO) -- SDM.pyc:264 - Total size of files in C:\Users\x\AppData\Roaming\Bitcoin\blocks is approx 14.8 GB 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['C:\\Program Files (x86)\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=C:\\Users\\x\\AppData\\Roaming\\Bitcoin\\'] 2014-03-22 19:56 (INFO) -- SDM.pyc:607 - PID of bitcoind: 3424 2014-03-22 19:56 (INFO) -- SDM.pyc:608 - PID of armory: 3760 2014-03-22 19:56 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['.\\guardian.exe', '3760', '3424'] 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1076 - setupUriRegistration 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1144 - Armory already registered for current user. Done! Here is log can go online..... Title: Re: Please Help Test Armory 0.91-beta! Post by: kerogre256 on March 22, 2014, 08:12:50 PM 2014-03-22 19:56 (INFO) -- ArmoryQt.py:585 - Usermode: Expert
2014-03-22 19:56 (INFO) -- ArmoryQt.py:1343 - Changing usermode: 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1344 - From: Expert 2014-03-22 19:56 (INFO) -- ArmoryQt.py:1352 - To: Expert 2014-03-22 19:56 (INFO) -- SDM.pyc:772 - Creating proxy in SDM: host=127.0.0.1, port=8332 2014-03-22 19:56 (INFO) -- ArmoryQt.py:5444 - Dashboard switched to auto-InitSync 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:InitializingLongTime 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4878 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline" 2014-03-22 19:56 (INFO) -- ArmoryQt.py:6293 - Another Armory instance just tried to open. 2014-03-22 19:56 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible 2014-03-22 19:56 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.90.99.4&id=98dbb36b 2014-03-22 19:56 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.4 2014-03-22 19:56 (WARNING) -- SDM.pyc:650 - bitcoind exited, bitcoind STDOUT: 2014-03-22 19:56 (WARNING) -- SDM.pyc:652 - 2014-03-22 19:56 (WARNING) -- SDM.pyc:653 - bitcoind exited, bitcoind STDERR: 2014-03-22 19:56 (WARNING) -- SDM.pyc:655 - 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (WARNING) -- SDM.pyc:692 - Overriding not-available state. This should happen 0-5 times 2014-03-22 19:56 (ERROR) -- ArmoryQt.py:5400 - BitcoindNotAvailable: should not happen... 2014-03-22 19:56 (INFO) -- ArmoryQt.py:4820 - Switching Armory functional mode to "Offline" Title: Re: Please Help Test Armory 0.91-beta! Post by: kerogre256 on March 22, 2014, 08:14:26 PM Any help ?
Title: Re: Please Help Test Armory 0.91-beta! Post by: kerogre256 on March 22, 2014, 08:25:10 PM Ok its working now look like problem was with old 32 bit bitcoin-qt client 8.5 after removing it from C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe armory started to scan DB.
Title: Re: Please Help Test Armory 0.91-beta! Post by: spin on March 22, 2014, 11:20:33 PM Installed this on a Ubuntu system and Win7 system (both 64bit).
The default installation gave me announcements on the ubuntu version but nothing on the Win7 version. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 22, 2014, 11:23:16 PM Installed this on a Ubuntu system and Win7 system (both 64bit). The default installation gave me announcements on the ubuntu version but nothing on the Win7 version. Strange. Does the announcement tab similar show nothing on Win7? Or you just didn't get the popups? There should be some messages in the logfile that start with "announcefetch.py". Right now the first URL always fails, the second one [should] always succeed. Title: Re: Please Help Test Armory 0.91-beta! Post by: spin on March 22, 2014, 11:27:14 PM Installed this on a Ubuntu system and Win7 system (both 64bit). The default installation gave me announcements on the ubuntu version but nothing on the Win7 version. Strange. Does the announcement tab similar show nothing on Win7? Or you just didn't get the popups? There should be some messages in the logfile that start with "announcefetch.py". Right now the first URL always fails, the second one [should] always succeed. Code: 2014-03-23 00:55 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?ver=0.90.99.4 Title: Re: Please Help Test Armory 0.91-beta! Post by: spin on March 22, 2014, 11:32:39 PM On windows it shows: There are no announcements or alerts to display. (Under notifications).
On ubuntu it has 3 notifications. Also some transaction tags have disappeared (same ones from both wallets). 1 wallet is watching only and the other is full. Title: Re: Please Help Test Armory 0.91-beta! Post by: spin on March 22, 2014, 11:34:31 PM Nevermind on restart windows had notifications as well.
Title: Re: Please Help Test Armory 0.91-beta! Post by: simonk83 on March 23, 2014, 09:35:37 AM I'm getting this: Code: Traceback (most recent call last): The previous version worked fine so not sure what that's about. Don't really know how to fix it either... Anything I can try here? Title: Re: Please Help Test Armory 0.91-beta! Post by: idoB on March 23, 2014, 09:52:24 AM Any help ? The log file you posted indicated that bitcoind had a problem (unspecified error). Try this:
Title: Not running on XP Post by: Brangdon on March 23, 2014, 04:48:59 PM I've just installed 0.90.99.4 on netbook that I intend to become an offline wallet, and it doesn't seem to run. Clicking the desktop icon, ArmoryQT.exe shows up momentarily in Task Manager, and then disappears again. The notebook is an Asus Eee PC 701 running XP SP3 and not much else. The screen is (faked) 800x600 and there's no network driver; it's a pretty minimal configuration. I've tried adding "--offline", and also giving it an explicit logfile path in the command line, and it doesn't seem to get as far as creating it. I've tried rebooting the machine.
Hmm. Looking in the Program Files directory, there's a file "ArmoryQt.exe" that's only 1k long, and claimed by Windows to be a text file. It contains lines like "(ERROR) BDM.pyc:1122 - Resetting BDM and all wallets". There is also a file "ArmoryQt" (no extension) that's 251k long. Weird. I previously installed it on my Win 8.1 desktop and that seemed fine. I'm using the Windows installer, from the first post in this thread. Scanning this thread, I seem to be the first person to mention using XP. Lucky me. Edit: I've now uninstalled it and tried the old 0.88.1 instead. That runs up fine, so I guess the netbook is capable. (I've not actually created a wallet with it as I'd rather use the new version with the improved randomness.) Title: Re: Not running on XP Post by: goatpig on March 23, 2014, 05:55:33 PM I've just installed 0.90.99.4 on netbook that I intend to become an offline wallet, and it doesn't seem to run. Clicking the desktop icon, ArmoryQT.exe shows up momentarily in Task Manager, and then disappears again. The notebook is an Asus Eee PC 701 running XP SP3 and not much else. The screen is (faked) 800x600 and there's no network driver; it's a pretty minimal configuration. I've tried adding "--offline", and also giving it an explicit logfile path in the command line, and it doesn't seem to get as far as creating it. I've tried rebooting the machine. Hmm. Looking in the Program Files directory, there's a file "ArmoryQt.exe" that's only 1k long, and claimed by Windows to be a text file. It contains lines like "(ERROR) BDM.pyc:1122 - Resetting BDM and all wallets". There is also a file "ArmoryQt" (no extension) that's 251k long. Weird. I previously installed it on my Win 8.1 desktop and that seemed fine. I'm using the Windows installer, from the first post in this thread. Scanning this thread, I seem to be the first person to mention using XP. Lucky me. Edit: I've now uninstalled it and tried the old 0.88.1 instead. That runs up fine, so I guess the netbook is capable. (I've not actually created a wallet with it as I'd rather use the new version with the improved randomness.) Try it with --test-announce, then without. Title: Re: Please Help Test Armory 0.91-beta! Post by: Brangdon on March 23, 2014, 06:17:35 PM --test-announce with/without made no difference.
(Ignore what I wrote earlier about the weird files. Windows was hiding the file extensions. That's what you get from using a freshly-formatted machine; I should know better. The ArmoryQt.exe.log file hasn't been modified since February.) Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 23, 2014, 07:23:44 PM In your Armory data folder, do you have this folder: atisignedannounce ?
Title: Re: Please Help Test Armory 0.91-beta! Post by: digipl on March 23, 2014, 07:34:50 PM All OK. Is the first 0.90.XX.X version who doesn't freeze in my computer. (windows 7 64 bits).
Very fast to scan and much, much less memory. very good work.... Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 23, 2014, 07:57:47 PM Try it with --test-announce, then without. --test-announce is became irrelevant once I published the high-security-signed announcements. Running with and without it should be identical. If anything, run with --skip-announce-check to prevent any announcement stuff from happening. But I suspect it's something else -- I'm pretty sure the announcement stuff fails gracefully. If Armory shows up in the task manager briefly, it's probably opening the log file and dumping errors before quitting. You need to look at the log that it wrote to: C:\Users\<user>\AppData\Roaming\Armory\armorylog.txt Btw, about the filenames in the program files directory: it's because you don't have file extensions shown. That directory has files "ArmoryQt.exe.txt" and "ArmoryQt.exe". But when you haven't told Windows to explicitly show you extensions, they chop off the .txt and .exe respectively in the file browser. So the text file looks like a .exe and the .txt looks like no extension... That just made me realize you could probably fool someone even moderately tech savvy, by giving them a file.txt.exe and they might double-click on without thinking, since it's "obviously" a txt file... Title: Re: Please Help Test Armory 0.91-beta! Post by: Brangdon on March 23, 2014, 08:42:27 PM If Armory shows up in the task manager briefly, it's probably opening the log file and dumping errors before quitting. You need to look at the log that it wrote to: There's no Users folder on this XP machine. There is "C:\Documents and settings\<user>\Application Data\Armory\armory.exe.log.txt", but it's left over from the 0.8.8.1 install. It has data from two runs; the second one begins with:C:\Users\<user>\AppData\Roaming\Armory\armorylog.txt 2014-03-23 20:22 (INFO) -- armoryengine.pyc:816 - Loading Armory Engine: 2014-03-23 20:22 (INFO) -- armoryengine.pyc:817 - Armory Version : 0.88.1 2014-03-23 20:22 (INFO) -- armoryengine.pyc:818 - PyBtcWallet Version : 1.35 2014-03-23 20:22 (INFO) -- armoryengine.pyc:819 - Detected Operating system: Windows 2014-03-23 20:22 (INFO) -- armoryengine.pyc:820 - OS Variant : XP-5.1.2600-SP3-Uniprocessor Free 2014-03-23 20:22 (INFO) -- armoryengine.pyc:821 - User home-directory : C:\Documents and Settings\Owner\Application Data 2014-03-23 20:22 (INFO) -- armoryengine.pyc:822 - Satoshi BTC directory : C:\Documents and Settings\Owner\Application Data\Bitcoin\ 2014-03-23 20:22 (INFO) -- armoryengine.pyc:823 - First blk*.dat file : C:\Documents and Settings\Owner\Application Data\Bitcoin\blocks\blk0001.dat 2014-03-23 20:22 (INFO) -- armoryengine.pyc:824 - Armory home dir : C:\Documents and Settings\Owner\Application Data\Armory\ 2014-03-23 20:22 (INFO) -- armoryengine.pyc:825 - Detected System Specs : 2014-03-23 20:22 (INFO) -- armoryengine.pyc:826 - Total Available RAM : 0.49 GB 2014-03-23 20:22 (INFO) -- armoryengine.pyc:827 - CPU ID string : x86 Family 6 Model 13 Stepping 8, GenuineIntel 2014-03-23 20:22 (INFO) -- armoryengine.pyc:828 - Number of CPU cores : 1 cores 2014-03-23 20:22 (INFO) -- armoryengine.pyc:829 - System is 64-bit : False 2014-03-23 20:22 (INFO) -- armoryengine.pyc:830 - Preferred Encoding : cp1252 I can post the whole thing if it would help. It's about 16k. --skip-announce-check made no difference. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 23, 2014, 09:06:13 PM If Armory shows up in the task manager briefly, it's probably opening the log file and dumping errors before quitting. You need to look at the log that it wrote to: There's no Users folder on this XP machine. There is "C:\Documents and settings\<user>\Application Data\Armory\armory.exe.log.txt", but it's left over from the 0.8.8.1 install. It has data from two runs; the second one begins with:C:\Users\<user>\AppData\Roaming\Armory\armorylog.txt 2014-03-23 20:22 (INFO) -- armoryengine.pyc:816 - Loading Armory Engine: 2014-03-23 20:22 (INFO) -- armoryengine.pyc:817 - Armory Version : 0.88.1 2014-03-23 20:22 (INFO) -- armoryengine.pyc:818 - PyBtcWallet Version : 1.35 2014-03-23 20:22 (INFO) -- armoryengine.pyc:819 - Detected Operating system: Windows 2014-03-23 20:22 (INFO) -- armoryengine.pyc:820 - OS Variant : XP-5.1.2600-SP3-Uniprocessor Free 2014-03-23 20:22 (INFO) -- armoryengine.pyc:821 - User home-directory : C:\Documents and Settings\Owner\Application Data 2014-03-23 20:22 (INFO) -- armoryengine.pyc:822 - Satoshi BTC directory : C:\Documents and Settings\Owner\Application Data\Bitcoin\ 2014-03-23 20:22 (INFO) -- armoryengine.pyc:823 - First blk*.dat file : C:\Documents and Settings\Owner\Application Data\Bitcoin\blocks\blk0001.dat 2014-03-23 20:22 (INFO) -- armoryengine.pyc:824 - Armory home dir : C:\Documents and Settings\Owner\Application Data\Armory\ 2014-03-23 20:22 (INFO) -- armoryengine.pyc:825 - Detected System Specs : 2014-03-23 20:22 (INFO) -- armoryengine.pyc:826 - Total Available RAM : 0.49 GB 2014-03-23 20:22 (INFO) -- armoryengine.pyc:827 - CPU ID string : x86 Family 6 Model 13 Stepping 8, GenuineIntel 2014-03-23 20:22 (INFO) -- armoryengine.pyc:828 - Number of CPU cores : 1 cores 2014-03-23 20:22 (INFO) -- armoryengine.pyc:829 - System is 64-bit : False 2014-03-23 20:22 (INFO) -- armoryengine.pyc:830 - Preferred Encoding : cp1252 I can post the whole thing if it would help. It's about 16k. --skip-announce-check made no difference. Essentially we need the end of the file, like the last 200 lines or so. Pastebin it and post the link here. Title: Re: Please Help Test Armory 0.91-beta! Post by: Brangdon on March 23, 2014, 10:48:42 PM The whole file is at http://pastebin.com/H6q6RHQE. As I said, I'm pretty sure it is all from 0.88.1 that works, not from 0.90.99.4 that fails to run.
Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 23, 2014, 10:56:04 PM That's enough information to know where to look at.
Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 23, 2014, 11:13:55 PM That's enough information to know where to look at. Is it? I don't see any attempts to open 0.90.99.X in that log file. Also, is it correct it's on a system with 512 MB of RAM? Are you trying to run this online? That might be challenging, regardless of the reason it's not loading. Also, I notice it is XP -- has anyone else confirmed that the testing version runs on XP? Title: Re: Please Help Test Armory 0.91-beta! Post by: Brangdon on March 23, 2014, 11:36:41 PM Also, is it correct it's on a system with 512 MB of RAM? Yes.Quote Are you trying to run this online? No. As I said in my first post, this is intended to be an offline wallet, using a cheap netbook running XP.I tried using Process Monitor. That suggests Armory:
Title: Re: Please Help Test Armory 0.91-beta! Post by: jl2012 on March 24, 2014, 05:46:50 PM Does this version (as network connected) still work with old version (as cold storage)?
I guess the old version can't sign P2SH? Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 24, 2014, 05:48:39 PM If you don't use P2SH anywhere, it works fine.
If you use P2SH, it will likely "work", but the offline computer will show useless info for any P2SH addresses. I don't recommend using it, since part of the security comes from being able to review the entirety of the tx on the offline computer. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 24, 2014, 09:19:35 PM Also, is it correct it's on a system with 512 MB of RAM? Yes.Quote Are you trying to run this online? No. As I said in my first post, this is intended to be an offline wallet, using a cheap netbook running XP.I tried using Process Monitor. That suggests Armory:
No wonder it wouldn't work, the WinXP specific code was not in this branch. Fixed now, you'll have to wait for the next build. Title: Re: Please Help Test Armory 0.91-beta! Post by: simonk83 on March 24, 2014, 09:44:17 PM I'm getting this: Code: Traceback (most recent call last): The previous version worked fine so not sure what that's about. Don't really know how to fix it either... Anything I can try here? Ok then. I've gone back to the previous version which is working fine. Title: Re: Please Help Test Armory 0.91-beta! Post by: e4xit on March 24, 2014, 10:28:20 PM I am running OSX Mavericks and when I try to run the app (clicking in applications folder) literally nothing happens? ???
Where should I go from here? Trying to open via Armory located within MacOS folder gives me Code: xxxx's-iMac:MacOS xxxx$ /Applications/Armory.app/Contents/MacOS/Armory Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 24, 2014, 10:39:29 PM So far, everyone who has reported this "image not found" error on OSX is running 10.9.2. I think. Please tell me if you see this error and are not running 10.9.2.
The error is not a missing file, because the exact same package seems to work on other versions of OSX. It's that the same dynamic object used by earlier OSX versions doesn't seem to be compatible with 10.9.2. It's possible we just might need to build a 10.9.2-specific version. Ugh! Go figure I bet it's finally working on 10.9.1 and then Apple goes ahead and makes yet another incompatible version! Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 25, 2014, 02:01:33 AM Am I glad I backed up my wallets, I launched it to the majority of my comments being wiped out:- The comment issue is now fixed in branch 0.91-dev EDIT: just to be clear, the comments were never deleted from your wallet, they were not displayed, as an unattended consequence of the 99% crash fix. Title: Re: Please Help Test Armory 0.91-beta! Post by: jflecool2 on March 25, 2014, 04:32:02 AM I dont think I like the "secure updater" thing. It sounds dangerous.
Also, you defenetly should implement Multisig to armory (a nice gui that would allow a user to generate a multisig address) I would try this version but I have bitcoins that I dont want to risk so I'll wait for a stable release :) Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 25, 2014, 04:36:04 AM I dont think I like the "secure updater" thing. It sounds dangerous. Also, you defenetly should implement Multisig to armory (a nice gui that would allow a user to generate a multisig address) I would try this version but I have bitcoins that I dont want to risk so I'll wait for a stable release :) Not sure why it sounds "dangerous". It's exactly the opposite. It lets you download the latest version and verifies all the digital signatures for you, so you don't have to install and figure out how to use GPG, and then find our GPG key and verify fingerprints. (granted, you should do that the first time you get Armory, but after that assuming you got a good copy, you will always be able to get the next version with the same security but without any effort). We are not implementing automatic updates yet. We're simply providing a mechanism for downloading signed installers and checking the signatures for you. Multisig is my top priority after this version is out. Coming soon! Title: Re: Please Help Test Armory 0.91-beta! Post by: realtime on March 25, 2014, 07:37:29 AM I'm having all sorts of issues trying to move coins from a hot wallet to my cold storage since moving to this release + 0.9.0 BitcoinQT.
This appears to only impact when i do a one to many transaction i.e. Sending from one source address to multiple output addresses. Anyone else encountering the same issue? Also which log file should i be checking for. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 25, 2014, 02:07:06 PM I'm having all sorts of issues trying to move coins from a hot wallet to my cold storage since moving to this release + 0.9.0 BitcoinQT. This appears to only impact when i do a one to many transaction i.e. Sending from one source address to multiple output addresses. Anyone else encountering the same issue? Also which log file should i be checking for. Just use Help->Submit Bug Report :-) Title: Re: Please Help Test Armory 0.91-beta! Post by: Brangdon on March 25, 2014, 07:50:04 PM No wonder it wouldn't work, the WinXP specific code was not in this branch. Fixed now, you'll have to wait for the next build. OK, thanks.Title: Re: Please Help Test Armory 0.91-beta! Post by: dc81 on March 26, 2014, 07:17:59 PM is the datadir flag still working? i'm on win7 and armory is ignoring the datadir location and using the default location.
Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 26, 2014, 07:20:49 PM is the datadir flag still working? i'm on win7 and armory is ignoring the datadir location and using the default location. I just noticed yesterday that --datadir fails if the target directory doesn't exist yet. Rather than bailing, it just switches to using the default directory. We're still not sure exactly how we want to deal with that yet. Besides that, I've been using --datadir constantly, and it works fine (for me) Title: Re: Please Help Test Armory 0.91-beta! Post by: dc81 on March 26, 2014, 08:34:40 PM forgot the double dash.. that's working now, but it's now i have another issue.
when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file. Code: 2014-03-26 15:25 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error Code: 2014-03-26 15:26 (ERROR) -- BDM.pyc:1383 - Error processing BDM input I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 26, 2014, 08:41:53 PM forgot the double dash.. that's working now, but it's now i have another issue. when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file. Code: 2014-03-26 15:25 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error Code: 2014-03-26 15:26 (ERROR) -- BDM.pyc:1383 - Error processing BDM input I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced. bitcoin.conf: did you run Armory as admin? Armory typically sets the permission of the bitcoin.conf to readonly for the current user (since it contains a username and password). And if Armory can't read it, I bet bitcoin core can't read it either, which maybe explains the other error. Though, it's strange error, that looks like what happens when you upgrade the repo without rebuilding the C++ code (enableZeroConf prototype did change recently, so if you only updated the python but didn't recompile, you'd see this error). But I see you're in windows so I don't expect that to be the problem... Title: Re: Please Help Test Armory 0.91-beta! Post by: dc81 on March 26, 2014, 08:57:01 PM forgot the double dash.. that's working now, but it's now i have another issue. when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file. Code: 2014-03-26 15:25 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error Code: 2014-03-26 15:26 (ERROR) -- BDM.pyc:1383 - Error processing BDM input I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced. bitcoin.conf: did you run Armory as admin? Armory typically sets the permission of the bitcoin.conf to readonly for the current user (since it contains a username and password). And if Armory can't read it, I bet bitcoin core can't read it either, which maybe explains the other error. Though, it's strange error, that looks like what happens when you upgrade the repo without rebuilding the C++ code (enableZeroConf prototype did change recently, so if you only updated the python but didn't recompile, you'd see this error). But I see you're in windows so I don't expect that to be the problem... Armory and Bitcoin is ran as a user. I end up having to create a new bitcoin.conf file each time I get this permission error. I am using the windows build from the first post. Title: Re: Please Help Test Armory 0.91-beta! Post by: Kluge on March 26, 2014, 08:58:38 PM
Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 26, 2014, 09:02:44 PM
Because I believe that the data is dumped to the blk*.dat files after bitcoin-qt/bitcoind has processed and indexed it. If it fails to write out the full block and then continues writing, it won't ever notice unless it has to explicitly fetch that block for some reason. I suspect that would only be relevant if that particular block had a tx relevant to your wallet (probably core wallet.dat). As such, errors are effectively ignored until you try to re-index. In our case, we're rescanning those blk*.dat files pretty frequently, and were under the assumption that there was some consistency in there. Apparently not. And it was causing Armory seg faults. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 26, 2014, 09:47:32 PM Has anyone here successfully run 0.90.99.4 on any OSX version? I downloaded and ran it on 10.9, but that system also already has a build environment on it.
It looks like the build has the QNetwork.so error on 10.9.2 and 10.9.1. I have successfully run it on a 10.8 VM and 10.9 host. But both have the build environments... Title: Re: Please Help Test Armory 0.91-beta! Post by: kendog77 on March 27, 2014, 12:41:41 AM Has anyone here successfully run 0.90.99.4 on any OSX version? I downloaded and ran it on 10.9, but that system also already has a build environment on it. It looks like the build has the QNetwork.so error on 10.9.2 and 10.9.1. I have successfully run it on a 10.8 VM and 10.9 host. But both have the build environments... No, I haven't. I downloaded the Windows and OSX version of Armory 0.90.99.4. The Windows version runs well, and the OSX version won't even open on version 10.9.2. Title: Re: Please Help Test Armory 0.91-beta! Post by: aerobatic on March 27, 2014, 04:52:07 PM Has anyone here successfully run 0.90.99.4 on any OSX version? I downloaded and ran it on 10.9, but that system also already has a build environment on it. It looks like the build has the QNetwork.so error on 10.9.2 and 10.9.1. I have successfully run it on a 10.8 VM and 10.9 host. But both have the build environments... No, I haven't. I downloaded the Windows and OSX version of Armory 0.90.99.4. The Windows version runs well, and the OSX version won't even open on version 10.9.2. count me in as well, have got several mac osx computers, all running 10.9.2 (the current OS) and Armory does not start on any of them. i have plenty of apps and none have problems on 10.9.2 except Armory -- Jez Title: Re: Please Help Test Armory 0.91-beta! Post by: doug_armory on March 28, 2014, 06:48:08 PM Has anyone here successfully run 0.90.99.4 on any OSX version? I downloaded and ran it on 10.9, but that system also already has a build environment on it. It looks like the build has the QNetwork.so error on 10.9.2 and 10.9.1. I have successfully run it on a 10.8 VM and 10.9 host. But both have the build environments... No, I haven't. I downloaded the Windows and OSX version of Armory 0.90.99.4. The Windows version runs well, and the OSX version won't even open on version 10.9.2. count me in as well, have got several mac osx computers, all running 10.9.2 (the current OS) and Armory does not start on any of them. i have plenty of apps and none have problems on 10.9.2 except Armory -- Jez Hey everyone. Sorry about the build not running. To be honest, I was out of the country and unable to run some sanity checks against some changes that were made. I can't get the posted build to run as-is. The good news is that the fix is dead simple. In a roundabout way, I've already tested it on the build that was posted. Works like a charm. I'm about to check in the fix. With any luck, the next build should be fine. :) Thanks for your patience! I'm back now and will get everything ironed out ASAP. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 29, 2014, 10:14:54 PM Hey everyone. Sorry about the build not running. To be honest, I was out of the country and unable to run some sanity checks against some changes that were made. I can't get the posted build to run as-is. The good news is that the fix is dead simple. In a roundabout way, I've already tested it on the build that was posted. Works like a charm. I'm about to check in the fix. With any luck, the next build should be fine. :) Thanks for your patience! I'm back now and will get everything ironed out ASAP. And follow-up good news: I successfully built the OSX packages on 10.8.5 and it ran on my 10.9.2 system! The reason I messed it up the first time (0.90.99.4) was kind of funny: there was a hardcoded path in the build process, but both my testing machine and build machine had exactly the same username and build-environment paths, so the hardcoded path actually existed on my test machine! This time I moved the paths around on the build machine, to make sure I couldn't make the same mistake. Still cleaning up a few things with this build, but will have 0.90.99.5 soon. Will also add a bug bounty to it! Besides OSX, we've had pretty solid feedback about this version, so we're pretty excited that this might be the last testing version before release! Title: Re: Please Help Test Armory 0.91-beta! Post by: qnxt on March 30, 2014, 01:39:04 AM I've been running 0.90.99.4 on OS X 10.9.2 since it was posted. (I installed the missing library from Homebrew and symlinked it to the appropriate hardcoded location.)
It's been MUCH more stable than the previous 0.90-beta version, which I ran for about two months. (The first wallet I ever used.) That version would often crash on me and force a full rescan. This version has been absolutely stable. I did notice that some of my comments disappeared, as someone else noted. (Only for certain types of transactions? I can check if you don't know what's causing this.) Sending coins is still a little slow; Armory just sits there for a while before prompting for my wallet password. Is that just my computer being slow? I only have a few dozen addresses with a fairly small number of uncomplicated transactions. Also, is it intentional that I can't set a 0.00001BTC transaction fee (with bitcoin-qt 0.90 and its new lower minimum), or am I doing something wrong? Title: Re: Please Help Test Armory 0.91-beta! Post by: forever3x on March 30, 2014, 09:02:51 AM I have a big wallet with lots of addresses. I can't open it with 0.90.99.4. After rescanned, the GUI is frozen.
In armorylog.txt there're repeating error logs: Code: 2014-03-30 16:51 (INFO) -- ArmoryQt.py:2518 - Syncing wallet: ******** Can you help? Thanks. Title: Re: Please Help Test Armory 0.91-beta! Post by: Brangdon on March 30, 2014, 12:10:37 PM Still cleaning up a few things with this build, but will have 0.90.99.5 soon. Will also add a bug bounty to it! Besides OSX, we've had pretty solid feedback about this version, so we're pretty excited that this might be the last testing version before release! Besides OSX and WinXP.Sorry to go on about it, and I may be the only tester planning to use XP, but the original post listed WinXP support as one of the bolded new features. I hope someone checks that 0.90.99.5 at least runs up on it. Running a cold storage wallet on a cheap, low-end notebook is a valuable feature for Armory, and XP is often the only version of Windows those machines can handle. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 31, 2014, 12:10:58 AM Just updated the downloads and announcements, with 0.90.99.5-testing! Also posted a bounty thread:
https://bitcointalk.org/index.php?topic=550804.0 Please post there any bugs if you want to claim a bounty for your bug reports. I really think this one will work with 10.9.1 and 10.9.2! Title: Re: Please Help Test Armory 0.91-beta! Post by: Subo1977 on March 31, 2014, 09:35:41 AM In the Armory-Log there are many such Outputs:
Code: 2014-03-31 09:32:21 keypool reserve 2 i think a API request to Bitcoin core ervery second is to much !? why no i.e. ever 2 or five second's? Title: Re: Please Help Test Armory 0.91-beta! Post by: forever3x on March 31, 2014, 01:03:05 PM On 0.90.99.5 mac version I still can't open my wallet. Keep getting the following error messages:
Code: 014-03-31 21:00 (ERROR) -- ArmoryQt.py:5942 - Error in heartbeat function Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 31, 2014, 02:21:02 PM Is your wallet gigantic? Or are you poiting at huge transactions? Do you have a Linux or Windows machine to try this wallet on? Would you be willing to send us a watching only copy of your wallet otherwise?
Title: Re: Please Help Test Armory 0.91-beta! Post by: dc81 on March 31, 2014, 03:32:02 PM Downloaded 0.90.99.5 for windows and still getting this error:
Code: 2014-03-31 10:29 (ERROR) -- BDM.pyc:1387 - ERROR: Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 31, 2014, 03:37:58 PM Downloaded 0.90.99.5 for windows and still getting this error: Code: 2014-03-31 10:29 (ERROR) -- BDM.pyc:1387 - ERROR: This really looks like a bundled version of Armory with the newest python code, but outdated C++ engine. I'm not sure how that would happen... What version of Windows are you using? Anyone here tried XP yet? (the previous build was supposed to have all the XP code, but we botched it... it should be right this time). Title: Re: Please Help Test Armory 0.91-beta! Post by: dc81 on March 31, 2014, 03:44:11 PM Downloaded 0.90.99.5 for windows and still getting this error: Code: 2014-03-31 10:29 (ERROR) -- BDM.pyc:1387 - ERROR: This really looks like a bundled version of Armory with the newest python code, but outdated C++ engine. I'm not sure how that would happen... What version of Windows are you using? Anyone here tried XP yet? (the previous build was supposed to have all the XP code, but we botched it... it should be right this time). win 7 Title: Re: Please Help Test Armory 0.91-beta! Post by: analytics on March 31, 2014, 03:59:14 PM Has anyone verified this is really the right person. There are no links from their website to this version.
Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 31, 2014, 04:08:56 PM Has anyone verified this is really the right person. There are no links from their website to this version. The hashes of these installers/binaries are signed by my email GPG key (not as strong as the offline GPG key, but still good). Also, if you are still using 0.90 you can find our hardcoded offline Bitcoin address (https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine.py#L17) which will match the hashes found on the download links announcement (https://s3.amazonaws.com/bitcoinarmory-testing/dllinks.txt). You should be able to us Tools->Message Signing & Verification and copy the contents of that file in as a signed message block, and verify the address show there. Once you have upgraded to one of the new testing versions, and any future version, the "Secure Downloader" does exactly that: it downloads that announcement file, verifies the signatures, and then downloads the new version and verifies the hashes match. I will continue to use my offline GPG key for signing new releases as well, but it will only be necessary the first time you download any new Armory version. After that, you can use the secure downloader to download verified installers (or manually verify them as described above). Also, if you do manual verification, the new version of Armory will recognize the public key and tell you "Signed by Armory Technologies Inc" instead of "Signed by 1NWvhByxfTXPYNT4zMBmEY3VL8QJQtQoei" Title: Re: Please Help Test Armory 0.91-beta! Post by: chrisrico on March 31, 2014, 04:23:50 PM 0.90.99.5 secure downloader works perfectly.
What's the install process for the Raspberry Pi tar? Extract to /? Right now I'm running 0.86 or so offline, is there even any benefit to upgrading? When funds are transferred from a cold storage wallet to an online wallet, do you no longer show two separate transactions (one outgoing from cold storage, one incoming to online)? Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 31, 2014, 04:32:00 PM 0.90.99.5 secure downloader works perfectly. What's the install process for the Raspberry Pi tar? Extract to /? Right now I'm running 0.86 or so offline, is there even any benefit to upgrading? When funds are transferred from a cold storage wallet to an online wallet, do you no longer show two separate transactions (one outgoing from cold storage, one incoming to online)? Not totally sure about the RPi thing yet. I mean, yes, it should be extracted to /, but you will need some other dependencies, which I haven't fully assembled yet. I don't have an RPi setup that I can use for testing atm, so I'm relying on someone else to help me figure out what's missing. Perfecting the RPi offline bundle might have to wait until after the conference, as we have some other priorities. But building for RPi was apparently much more challenging than just getting the dependencies, so hopefully this is one big piece of that puzzle solved for the RPi users. If both wallets are loaded on the online computer, you should see two transactions. As you said, it is two distinct events, one for each wallet, so it should show up (@goatpig: didn't you say something about duplicate ledger entries? did you misread this as a bug and "fix" it?) Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 31, 2014, 04:54:18 PM Testing this now.
There was a convoluted ledger entry misrepresentation that I caught fixing the send to many issue. This is all post .5, sadly. Title: Re: Please Help Test Armory 0.91-beta! Post by: Kluge on March 31, 2014, 04:55:16 PM Clean install, win7, used website to download instead of secure downloader.
https://i.imgur.com/1j1qtpQ.jpg Title: Re: Please Help Test Armory 0.91-beta! Post by: chrisrico on March 31, 2014, 04:55:26 PM I don't have an RPi setup that I can use for testing atm I have an extra Pi lying around if you want it for testing. Quote If both wallets are loaded on the online computer, you should see two transactions. As you said, it is two distinct events, one for each wallet, so it should show up (@goatpig: didn't you say something about duplicate ledger entries? did you misread this as a bug and "fix" it?) Now that you mention it, in addition to no longer seeing an incoming and outgoing entry, I'm also seeing duplicate entires. I created one transaction from an offline to an online wallet, with multiple outputs to the online wallet. In the ledger, I'm seeing multiple entries for the full amount of the transaction, not the individual outputs. If that doesn't make sense, let me know what I can send you. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 31, 2014, 04:56:23 PM I don't have an RPi setup that I can use for testing atm I have an extra Pi lying around if you want it for testing. Quote If both wallets are loaded on the online computer, you should see two transactions. As you said, it is two distinct events, one for each wallet, so it should show up (@goatpig: didn't you say something about duplicate ledger entries? did you misread this as a bug and "fix" it?) Now that you mention it, in addition to no longer seeing an incoming and outgoing entry, I'm also seeing duplicate entires. I created one transaction from an offline to an online wallet, with multiple outputs to the online wallet. In the ledger, I'm seeing multiple entries for the full amount of the transaction, not the individual outputs. If that doesn't make sense, let me know what I can send you. That's the send to many issue I just fixed Title: Re: Please Help Test Armory 0.91-beta! Post by: tlr on March 31, 2014, 06:14:09 PM Out of curiosity, how soon do you expect to implement BIP 32 wallets? I'd like to switch to Armory (or something else) but have tried holding out for BIP 32 support.
Title: Re: Please Help Test Armory 0.91-beta! Post by: gweedo on March 31, 2014, 06:35:23 PM Out of curiosity, how soon do you expect to implement BIP 32 wallets? I'd like to switch to Armory (or something else) but have tried holding out for BIP 32 support. Pretty sure armory has BIP 32, I don't know it follows that protocol, but you only have to backup one thing that will generate all your addresses for you, which is what BIP 32 basically is. Title: Re: Please Help Test Armory 0.91-beta! Post by: chrisrico on March 31, 2014, 06:42:58 PM Out of curiosity, how soon do you expect to implement BIP 32 wallets? I'd like to switch to Armory (or something else) but have tried holding out for BIP 32 support. Pretty sure armory has BIP 32, I don't know it follows that protocol, but you only have to backup one thing that will generate all your addresses for you, which is what BIP 32 basically is. The problem is that it is not interoperable with other BIP 32 implementations. I can't import my Armory seed into my Trezor and vice versa. So it's not BIP 32. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 31, 2014, 06:44:55 PM New wallets are top priority after 0.91-beta which is in testing right now. The following version, 0.92-beta, will include the new wallet format, which includes native BIP32 support along with a ton of other things (including compressed public keys and some multisig capability).
Title: Re: Please Help Test Armory 0.91-beta! Post by: RGBKey on March 31, 2014, 08:27:40 PM Upon running the new version after uninstalling the last version but not deleting the appdata folder.
http://puu.sh/7R9Vj.png Next I will be restoring a wallet that I created in .90 which I just deleted once the blockchain is done downloading. Title: Re: Please Help Test Armory 0.91-beta! Post by: cp1 on March 31, 2014, 08:34:09 PM If I checkout the testing branch of your github will I get the 0.91-beta? I don't want to install a .deb for a beta release, I'd rather put it in a separate directory and not overwrite my current version.
Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on March 31, 2014, 08:37:58 PM If I checkout the testing branch of your github will I get the 0.91-beta? I don't want to install a .deb for a beta release, I'd rather put it in a separate directory and not overwrite my current version. Yes, testing branch should be at 0.90.99.5, the same as the links in this thread. Though, I was just thinking of merging some fixes that goatpig pushed which will be part of .6 or .7 Title: Re: Please Help Test Armory 0.91-beta! Post by: BitAddict on March 31, 2014, 10:51:24 PM I had to redownload the full blockchain but now it is working again ;D
Thanks! Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on March 31, 2014, 11:04:54 PM I had to redownload the full blockchain but now it is working again ;D Thanks! What issue were you experiencing? Title: Re: Please Help Test Armory 0.91-beta! Post by: pdawg on March 31, 2014, 11:06:49 PM Does the latest bitcoin-qt play nice with the latest stable armory?
Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on April 01, 2014, 12:20:43 AM Does the latest bitcoin-qt play nice with the latest stable armory? Yes use the newest Bitcoin core Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on April 01, 2014, 12:40:44 AM Requesting a simple config file for directories. Updating erases my shortcut and I use different Bitcoin and data directories.
Also Windows server not being detected. Server 2012 should be detected as windows 8. 404 https://bitcoinarmory.com/submitbug.php Keep getting update notice http://imgur.com/vITN2tg Title: Re: Please Help Test Armory 0.91-beta! Post by: forever3x on April 01, 2014, 12:55:47 AM Yes, testing branch should be at 0.90.99.5, the same as the links in this thread. Though, I was just thinking of merging some fixes that goatpig pushed which will be part of .6 or .7 Can you help to fix the problem: Code: 2014-04-01 08:54 (ERROR) -- BDM.py:252 - BDM was not ready for your request! Waited 20 sec. Keep getting it and I can't open my wallet :'( Thanks! Title: Re: Please Help Test Armory 0.91-beta! Post by: BitAddict on April 01, 2014, 10:20:34 AM I had to redownload the full blockchain but now it is working again ;D Thanks! What issue were you experiencing? 96-99% analysing crash. Title: Re: Please Help Test Armory 0.91-beta! Post by: ncs0ne on April 01, 2014, 05:28:19 PM I left armory open while system was in standby, after resume armory was more or less frozen (100% cpu on 2/4 cores), OS asking me to kill this process or wait a little longer.
After a restart armory was working again. I created an online transaction and entered my password. Armory was then causing high cpu load again. I left it alone. After some minutes the transaction had been created and broadcasted successfully, armory was reacting again. I clicked on the transaction to view it on blockchain.info which worked as expected. Some minutes later, when I looked after my armory instance it was reacting very very slow (export of log file took ages). The right corner bottom shows "Connected (False blocks)" As next I shut it down via File->Quit which took ~3minutes to finish. After a restart Wallet Consistency Check took place. Then everything was working again, status Connected with current block number. Switching between from tabs 'Announcements' to 'Transactions' to Dashboard was fast, but then clicking on tab Transactions again I had my next freeze. After ~1min the txs where shown, but then the right corner bottom showed "Connected (False blocks)". Now armory doesn't react in a proper time one could think it's frozen, but actually it's very very slowly working with very high cpu load. The tx-table's font is colored in light-gray. I switched the wallet to display (still tab transactions), table content remains in light-gray font, but now armory reacts again until I trigger an action like Settings then it freezes again. Here are some hopefully helpful parts of my log. In case further info is needed let me know please and I'll provide it. Thanks. Code: 2014-04-01 13:15 (ERROR) -- BDM.py:252 - BDM was not ready for your request! Waited 20 sec. Code: 2014-04-01 14:50 (INFO) -- ArmoryQt.py:3193 - Sending Tx, <id cut off> Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 01, 2014, 08:14:35 PM I left armory open while system was in standby, after resume armory was more or less frozen (100% cpu on 2/4 cores), OS asking me to kill this process or wait a little longer. After a restart armory was working again. I created an online transaction and entered my password. Armory was then causing high cpu load again. I left it alone. After some minutes the transaction had been created and broadcasted successfully, armory was reacting again. I clicked on the transaction to view it on blockchain.info which worked as expected. Some minutes later, when I looked after my armory instance it was reacting very very slow (export of log file took ages). The right corner bottom shows "Connected (False blocks)" As next I shut it down via File->Quit which took ~3minutes to finish. After a restart Wallet Consistency Check took place. Then everything was working again, status Connected with current block number. Switching between from tabs 'Announcements' to 'Transactions' to Dashboard was fast, but then clicking on tab Transactions again I had my next freeze. After ~1min the txs where shown, but then the right corner bottom showed "Connected (False blocks)". Now armory doesn't react in a proper time one could think it's frozen, but actually it's very very slowly working with very high cpu load. The tx-table's font is colored in light-gray. I switched the wallet to display (still tab transactions), table content remains in light-gray font, but now armory reacts again until I trigger an action like Settings then it freezes again. Here are some hopefully helpful parts of my log. In case further info is needed let me know please and I'll provide it. Thanks. Sounds like your wallet carries some gigantic transactions, or a lot of them. How long does it take to open the wallet properties windows? We have a long term solution for this but it is part of some massive refactoring and overhauling on the C++ end, so it will have to wait for 0.91.1-beta If you're willing to send us a watching only copy of your wallet, I can give it a detailed look and maybe I can catch a quick optimization to shove into this release. Title: Re: Please Help Test Armory 0.91-beta! Post by: Finnminer on April 02, 2014, 07:26:51 AM Updated from the perfectly working .4 to .5 and it's now back to unusable. :(
A ton of these in the log: Code: 2014-04-02 10:17 (ERROR) -- BDM.pyc:252 - BDM was not ready for your request! Waited 20 sec. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 02, 2014, 09:10:39 AM Updated from the perfectly working .4 to .5 and it's now back to unusable. :( A ton of these in the log: Code: 2014-04-02 10:17 (ERROR) -- BDM.pyc:252 - BDM was not ready for your request! Waited 20 sec. Does it happen after DB build or Tx Scan? The 99% fix in .4 introduced a transaction ledger entry bug, and did not pass the unit tests. .5 partially fixed the ledger entry issue but still didn't pass the tests. .6 fully fixes the ledger entry and passes the tests. Let's see if you can load with .6. It should be out today or tomorrow. EDIT: Identified the issue. Working on it right now. I have a solution but I need to test it to make sure I'm not breaking stuff on the side. Title: Re: Please Help Test Armory 0.91-beta! Post by: justusranvier on April 02, 2014, 03:50:52 PM Armory sometimes gets into a infinite loop of connecting and disconnecting from the node.
It's triggered after a node loses Internet connectivity (maybe it's set up to connect through a proxy and the proxy goes down for some reason). When connectivity is restored and the node starts to catch back up with the network, Armory will start connecting and disconnecting 1-2 times per second, with the GUI showing a "can not connect to node" error message. Closing and reopening Armory (while doing nothing at all to the bitcoind node) resolves the problem. Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on April 02, 2014, 04:00:30 PM Armory sometimes gets into a infinite loop of connecting and disconnecting from the node. It's triggered after a node loses Internet connectivity (maybe it's set up to connect through a proxy and the proxy goes down for some reason). When connectivity is restored and the node starts to catch back up with the network, Armory will start connecting and disconnecting 1-2 times per second, with the GUI showing a "can not connect to node" error message. Closing and reopening Armory (while doing nothing at all to the bitcoind node) resolves the problem. I got that when Bitcoin runs out of connections but yours might d be different. It is possible a spot opened up while restarting tho Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 02, 2014, 04:26:10 PM I'm not sure this is the trigger. My connection at home is currently being very unstable, I get disconnected for tenths of minutes at time, all with Bitcoin core and Armory running, and I don't get this issue at all.
I've experienced on transaction broadcasts that get turned down. Overall I think this is related to ZC transactions. We don't have much on this one yet, and frankly it's low priority right now. I expect that I'll eventually run into it, and that usually enough to identify the cause and fix it. Title: Re: Please Help Test Armory 0.91-beta! Post by: drrussellshane on April 03, 2014, 08:21:48 PM I think I found a bug... when I clicked on a new (unconfirmed) incoming transaction, and clicked "Open Relevant Wallet", the wallet that it opened was not relevant.
Title: Re: Please Help Test Armory 0.91-beta! Post by: aerobatic on April 03, 2014, 08:25:51 PM I think I found a bug... when I clicked on a new (unconfirmed) incoming transaction, and clicked "Open Relevant Wallet", the wallet that it opened was not relevant. i'd like to report a bug in all versions of Mac Armory including 0.91 beta 0.90.99.5) My Mac is set to sleep at 2am, and wake at 9am every day. its part of the energy saver sleep modes (its not a power down, its just a suspended sleep) Quite often, after the mac has been asleep, and woken up... Armory hangs and doesn't recover. When i click into the Armory window, i see the Busy icon, which never goes away. Armory has completely hung, it won't even quit gracefully and has to be 'force quit'd. When i re-run it immediately after, its fine. Bitcoin-QT is still running in the background, and is connected. This is repeatable almost every day for me, as my mac sleeps every night and wakes every day. wish you all the best, and good luck... hope you can reproduce it too. -- Jez Title: Re: Please Help Test Armory 0.91-beta! Post by: doug_armory on April 03, 2014, 09:27:54 PM i'd like to report a bug in all versions of Mac Armory including 0.91 beta 0.90.99.5) My Mac is set to sleep at 2am, and wake at 9am every day. its part of the energy saver sleep modes (its not a power down, its just a suspended sleep) Quite often, after the mac has been asleep, and woken up... Armory hangs and doesn't recover. When i click into the Armory window, i see the Busy icon, which never goes away. Armory has completely hung, it won't even quit gracefully and has to be 'force quit'd. When i re-run it immediately after, its fine. Bitcoin-QT is still running in the background, and is connected. This is repeatable almost every day for me, as my mac sleeps every night and wakes every day. wish you all the best, and good luck... hope you can reproduce it too. Hello. I just tried this a few times on my setup. I haven't been able to reproduce it yet. My suspicion is that this is a Qt (or maybe PyQt?) issue. I'll continue to look into it, though, and do some overnight sleeps. Thanks for letting us know. Title: Re: Please Help Test Armory 0.91-beta! Post by: L0rdCha0s on April 03, 2014, 10:22:33 PM Just reporting an issue I've seen in Armory 0.90.99.5
Outbound transactions seem to be 'disappearing' from the transaction list, but the wallet balance is correct, and you can still see the transaction if you go to the Addresses involved in the Wallet Properties and look at the Address's transaction list. About the only unusual thing about my wallet is that it contains 4000 addresses (we're a bitcoin merchant services company). Steps to reproduce 1. Environment: Ubuntu 13.04, Armory 0.90.99.5, Bitcoin Core 0.90 2. Create new offline transaction in online Armory (in my case,for the entire wallet balance). 3. Sign transaction offline 4. Broadcast transaction online. 5. The unconfirmed transaction does appear in the transaction list 6. Wait for a block 7. Outbound transaction suddenly disappears from transaction list, but the balance stays correct. Has anyone else seen this? EDIT: Confirming this doesn't happen in 0.90.x Title: Re: Please Help Test Armory 0.91-beta! Post by: e4xit on April 04, 2014, 10:44:47 AM Armory sometimes gets into a infinite loop of connecting and disconnecting from the node. It's triggered after a node loses Internet connectivity (maybe it's set up to connect through a proxy and the proxy goes down for some reason). When connectivity is restored and the node starts to catch back up with the network, Armory will start connecting and disconnecting 1-2 times per second, with the GUI showing a "can not connect to node" error message. Closing and reopening Armory (while doing nothing at all to the bitcoind node) resolves the problem. justusranvier I solved this on my machine by editing my bitcoin.conf file to add 127.0.0.1 as a mandatory peer. This allowed Armory to maintain connection to Bitcoin-Qt(/d) even when Bitcoin-QT/d maxed out allowed peers with external nodes. I may have misinterpreted your problem though. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 04, 2014, 11:56:17 AM I think I found a bug... when I clicked on a new (unconfirmed) incoming transaction, and clicked "Open Relevant Wallet", the wallet that it opened was not relevant. Unattended consequences of the transaction ledger mess up in .4 and .5 I think I found a bug... when I clicked on a new (unconfirmed) incoming transaction, and clicked "Open Relevant Wallet", the wallet that it opened was not relevant. i'd like to report a bug in all versions of Mac Armory including 0.91 beta 0.90.99.5) My Mac is set to sleep at 2am, and wake at 9am every day. its part of the energy saver sleep modes (its not a power down, its just a suspended sleep) Quite often, after the mac has been asleep, and woken up... Armory hangs and doesn't recover. When i click into the Armory window, i see the Busy icon, which never goes away. Armory has completely hung, it won't even quit gracefully and has to be 'force quit'd. When i re-run it immediately after, its fine. Bitcoin-QT is still running in the background, and is connected. This is repeatable almost every day for me, as my mac sleeps every night and wakes every day. wish you all the best, and good luck... hope you can reproduce it too. -- Jez May or may not be a Qt issue. We are moving to a more scalable model in 0.91.1, which will introduce a comminucation framework that will be a lot more resilient to this kind of desyncing between Armory's frontend/backend/Bitcoin core Just reporting an issue I've seen in Armory 0.90.99.5 Outbound transactions seem to be 'disappearing' from the transaction list, but the wallet balance is correct, and you can still see the transaction if you go to the Addresses involved in the Wallet Properties and look at the Address's transaction list. About the only unusual thing about my wallet is that it contains 4000 addresses (we're a bitcoin merchant services company). Steps to reproduce 1. Environment: Ubuntu 13.04, Armory 0.90.99.5, Bitcoin Core 0.90 2. Create new offline transaction in online Armory (in my case,for the entire wallet balance). 3. Sign transaction offline 4. Broadcast transaction online. 5. The unconfirmed transaction does appear in the transaction list 6. Wait for a block 7. Outbound transaction suddenly disappears from transaction list, but the balance stays correct. Has anyone else seen this? EDIT: Confirming this doesn't happen in 0.90.x Related to the transaction ledger snafu too. All this will be fixed in .6, which CircusPeanut is currently help me test. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on April 04, 2014, 08:20:50 PM Alright, lots of the issues with 0.90.99.5 have been resolved, and pushed to 0.90.99.7. I just pushed the new version along with notifications. Hopefully the notifications will actually work properly this time (no more "You are using version X+1 please upgrade to X+1!").
Title: Re: Please Help Test Armory 0.91-beta! Post by: qnxt on April 04, 2014, 08:58:51 PM Alright, lots of the issues with 0.90.99.5 have been resolved, and pushed to 0.90.99.7. I just pushed the new version along with notifications. Hopefully the notifications will actually work properly this time (no more "You are using version X+1 please upgrade to X+1!"). Still broken. :( https://i.imgur.com/sVCdvX1.png (I downloaded from the web, not via the secure downloader. Also, I put the new version in ~/Desktop instead of /Applications, where 0.90.99.5 is.) Title: Re: Please Help Test Armory 0.91-beta! Post by: SimonBelmond on April 04, 2014, 09:19:44 PM Alright, lots of the issues with 0.90.99.5 have been resolved, and pushed to 0.90.99.7. I just pushed the new version along with notifications. Hopefully the notifications will actually work properly this time (no more "You are using version X+1 please upgrade to X+1!"). Just updated Bitcoin Core and Armory and all worked like a charm. So pleased to see the Armory-Team being well earthed and constantly improving. The work you guys are doing is awesome and absolutely key to the development of Bitcoin and Co. I congratulate and thank you guys. The new features are cool and I know there is lots more in the pipeline. Still had to click away the message mentioned above though. ;-) Shall I use the bug reporting? ;-) Title: Re: Please Help Test Armory 0.91-beta! Post by: Finnminer on April 04, 2014, 09:49:47 PM Updated from the perfectly working .4 to .5 and it's now back to unusable. :( I'm happy to report that this problem is fixed in .7. A ton of these in the log: Code: 2014-04-02 10:17 (ERROR) -- BDM.pyc:252 - BDM was not ready for your request! Waited 20 sec. Title: Re: Please Help Test Armory 0.91-beta! Post by: Carlton Banks on April 04, 2014, 10:05:14 PM
bitcoin core 0.9.0, Ubuntu 12.04 Title: Re: Please Help Test Armory 0.91-beta! Post by: L0rdCha0s on April 04, 2014, 10:49:26 PM Related to the transaction ledger snafu too. All this will be fixed in .6, which CircusPeanut is currently help me test. Perfect! Works great in 0.90.99.7 :) Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 04, 2014, 11:36:39 PM Broken Notification: working on it as we speak
bitcoin core 0.9.0, Ubuntu 12.04 Thanks for the report. Regarding the 3rd issue, .4 was populating the ledger partially, so that's not a fair comparison. This will be much snappier in 0.91.1, with the push model backend. Will look into the other ones. Title: Re: Please Help Test Armory 0.91-beta! Post by: qnxt on April 04, 2014, 11:58:35 PM 0.90.99.7 is occasionally freezing on me on OS X 10.9.2, just sitting at the main window idle. I've only noticed so far when switching back after leaving it in the background for a while. It beachballs and shows "Disconnected", without me being able to do anything. The first few times it did that, it came back after 3 - 5 minutes, but it just got stuck for about 20 or 30 minutes before I did a force quit.
Last logfile entry: 2014-04-04 19:25 (INFO) -- announcefetch.py:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.7 (Is there some additional logging level I failed to turn on?) Doesn't use up much CPU when it's doing that, either. Title: Re: Please Help Test Armory 0.91-beta! Post by: mattbit on April 05, 2014, 12:22:44 AM Since a week ago, Armory is constantly crashing at 23% when scanning transaction history. I was using the previous stable release and tried upgrading to the beta version but it's still happening. Here is the log:
Log file opened at 1396656691: /home/matt/.armory/armorycpplog.txt -INFO - 1396656693: (BlockUtils.cpp:2311) Set home directory: -INFO - 1396656695: (BlockUtils.cpp:2333) Set blkfile dir: /home/matt/.bitcoin/blocks -INFO - 1396656695: (BlockUtils.cpp:2343) Set leveldb dir: /home/matt/.armory/databases -INFO - 1396656695: (BlockUtils.cpp:2299) SetBtcNetworkParams -INFO - 1396656695: (BlockUtils.cpp:4337) Executing: doInitialSyncOnLoad -INFO - 1396656695: (BlockUtils.cpp:4378) Number of registered addr: 1257 -INFO - 1396656695: (leveldb_wrapper.cpp:399) Opening databases... -DEBUG - 1396656695: (BlockUtils.cpp:4390) Called build&scan with (0,0,0,1) -INFO - 1396656697: (BlockUtils.cpp:2424) Total blk*.dat files: 130 -INFO - 1396656697: (BlockUtils.cpp:2442) Current Top block in HEADERS DB: 294168 -INFO - 1396656697: (BlockUtils.cpp:2443) Current Top block in BLKDATA DB: 294168 -INFO - 1396656697: (BlockUtils.cpp:2444) Current Applied blocks up to hgt: 0 -DEBUG - 1396656700: (BlockUtils.cpp:5597) Organizing chain w/ rebuild -DEBUG - 1396656701: (BlockUtils.cpp:5721) Done organizing chain -INFO - 1396656703: (BlockUtils.cpp:2545) First unrecognized hash file: 129 -INFO - 1396656703: (BlockUtils.cpp:2546) Offset of first unrecog block: 29280764 -INFO - 1396656703: (BlockUtils.cpp:2555) First blkfile not in DB: 129 -INFO - 1396656703: (BlockUtils.cpp:2556) Location of first block not in DB: 29280764 -INFO - 1396656703: (BlockUtils.cpp:4423) Fetching stored script histories from DB -INFO - 1396656704: (BlockUtils.cpp:4465) Reading all headers and building chain... -DEBUG - 1396656704: (BlockUtils.cpp:5597) Organizing chain w/ rebuild -DEBUG - 1396656705: (BlockUtils.cpp:5721) Done organizing chain -INFO - 1396656712: (BlockUtils.cpp:4469) Total number of blk*.dat files: 130 -INFO - 1396656712: (BlockUtils.cpp:4470) Total number of blocks found: 294169 -INFO - 1396656712: (BlockUtils.cpp:4482) Getting latest blocks from blk*.dat files -INFO - 1396656712: (BlockUtils.cpp:4483) Total blockchain bytes: 17,337,233,740 -INFO - 1396656712: (BlockUtils.cpp:4489) Parsing blockchain file: /home/matt/.bitcoin/blocks/blk00129.dat -INFO - 1396656712: (BlockUtils.cpp:4622) /home/matt/.bitcoin/blocks/blk00129.dat is 33,554,432 bytes -INFO - 1396656713: (BlockUtils.cpp:4503) Processed 1 raw blocks DB (0 seconds) -INFO - 1396656713: (BlockUtils.cpp:4535) Starting scan from block height: 0 -ERROR - 1396656927: (StoredBlockObj.cpp:1082) Cannot get tx copy, because don't have full StoredTx! Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on April 05, 2014, 12:43:08 AM Since a week ago, Armory is constantly crashing at 23% when scanning transaction history. I was using the previous stable release and tried upgrading to the beta version but it's still happening. Here is the log: .... Code: -INFO - 1396656713: (BlockUtils.cpp:4503) Processed 1 raw blocks DB (0 seconds) Haven't seen this one in a while, but we think it's caused by building your DB with the old version and corrupt blk*.dat files from Bitcoin Core. Since your DB is already built, you need to rebuild it with the new version. We'd love to know if this fixes your problem -- because we actually haven't run into the "don't-have-full-tx" problem on any of our own systems before, so we can't test whether we fixed it! So please use "Help"->Rebuild & Rescan Databases. With some luck that fixes it. If not, I recommend you do a factory reset and redownload the blockchain (because this is ultimately caused by bad blk*.dat files which will only be fixed with a redownload). With the new bittorrent stuff, it's a heck of a lot faster than it used to be! Title: Re: Please Help Test Armory 0.91-beta! Post by: Winterfrost on April 05, 2014, 04:19:06 AM Loaded the latest testing version, and now my wallets don't appear. Armory still thinks they're loaded though.
https://i.imgur.com/jUVe2HA.png Edit: Nevermind. I rebooted and everything is back to normal. That's what I get for doing things late at night. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 05, 2014, 12:46:20 PM 0.90.99.7 is occasionally freezing on me on OS X 10.9.2, just sitting at the main window idle. I've only noticed so far when switching back after leaving it in the background for a while. It beachballs and shows "Disconnected", without me being able to do anything. The first few times it did that, it came back after 3 - 5 minutes, but it just got stuck for about 20 or 30 minutes before I did a force quit. Last logfile entry: 2014-04-04 19:25 (INFO) -- announcefetch.py:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.7 (Is there some additional logging level I failed to turn on?) Doesn't use up much CPU when it's doing that, either. There is no higher verbose level available to you without rebuilding from source. You're experiencing this issue on OSX 10.9.2. With have had some trouble so far delivering a stable experience on OSX. We recently stabilized 10.9.1 and Apple recently updated .9.2 which got us in trouble again. If you want to help isolating the issue, do the following: if you can easily reproduce the issue, try and reproduce it on another OS. If you fail to, then this is a pure OSX issue. At this point save your current log file, delete it from Armory's datadir, then reproduce the error, and send us both log files with your observations. This would take us a quite a few steps forward in fixing the issue. Title: Re: Please Help Test Armory 0.91-beta! Post by: doug_armory on April 05, 2014, 04:42:09 PM 0.90.99.7 is occasionally freezing on me on OS X 10.9.2, just sitting at the main window idle. I've only noticed so far when switching back after leaving it in the background for a while. It beachballs and shows "Disconnected", without me being able to do anything. The first few times it did that, it came back after 3 - 5 minutes, but it just got stuck for about 20 or 30 minutes before I did a force quit. Last logfile entry: 2014-04-04 19:25 (INFO) -- announcefetch.py:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.90.99.7 (Is there some additional logging level I failed to turn on?) Doesn't use up much CPU when it's doing that, either. There is no higher verbose level available to you without rebuilding from source. You're experiencing this issue on OSX 10.9.2. With have had some trouble so far delivering a stable experience on OSX. We recently stabilized 10.9.1 and Apple recently updated .9.2 which got us in trouble again. If you want to help isolating the issue, do the following: if you can easily reproduce the issue, try and reproduce it on another OS. If you fail to, then this is a pure OSX issue. At this point save your current log file, delete it from Armory's datadir, then reproduce the error, and send us both log files with your observations. This would take us a quite a few steps forward in fixing the issue. Agreed. I've received reports of similar issues but have had a lot of trouble reproducing most of them. The closest I've come is that Armory will sometimes take about 30-60s in order to shut down, but it will shut down eventually. (That being said, I've noticed that BC-Core can also take a little while to shut down as of 0.9.) Title: Re: Please Help Test Armory 0.91-beta! Post by: forever3x on April 06, 2014, 03:14:11 PM Still can't open a wallet with lots of transactions in 0.90.99.7. Repeating errors:
Quote 2014-04-06 23:09 (ERROR) -- BDM.py:1383 - Error processing BDM input 2014-04-06 23:09 (ERROR) -- BDM.py:1385 - Received inputTuple: Passthrough [15, 4547982, True, 'scanRegisteredTxForWallet', <CppBlockUtils.BtcWallet; proxy of <Swig Object of type 'std::vector< BtcWallet * >::value_type' at 0x1a50c91b0> >, None] 2014-04-06 23:09 (ERROR) -- BDM.py:1386 - Error processing ID (4547982) 2014-04-06 23:09 (ERROR) -- BDM.py:1387 - ERROR: Traceback (most recent call last): File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/BDM.py", line 1343, in run output = getattr(self.bdm, funcName)(*funcArgs) File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/CppBlockUtils.py", line 1882, in scanRegisteredTxForWallet def scanRegisteredTxForWallet(self, *args): return _CppBlockUtils.BlockDataManager_LevelDB_scanRegisteredTxForWallet(self, *args) NotImplementedError: Wrong number or type of arguments for overloaded function 'BlockDataManager_LevelDB_scanRegisteredTxForWallet'. Possible C/C++ prototypes are: BlockDataManager_LevelDB::scanRegisteredTxForWallet(BtcWallet &,uint32_t,uint32_t) BlockDataManager_LevelDB::scanRegisteredTxForWallet(BtcWallet &,uint32_t) BlockDataManager_LevelDB::scanRegisteredTxForWallet(BtcWallet &) 2014-04-06 23:09 (ERROR) -- ArmoryQt.py:5947 - Error in heartbeat function Traceback (most recent call last): File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 5850, in Heartbeat self.finishLoadBlockchain() File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Timer.py", line 99, in inner ret = func(*args, **kwargs) File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 2557, in finishLoadBlockchain self.createCombinedLedger() File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Timer.py", line 99, in inner ret = func(*args, **kwargs) File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 2720, in createCombinedLedger unconfFunds += wlt.getBalance('Unconfirmed') File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/PyBtcWallet.py", line 401, in getBalance return self.cppWallet.getUnconfirmedBalance(currBlk, IGNOREZC) File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/CppBlockUtils.py", line 1713, in getUnconfirmedBalance def getUnconfirmedBalance(self, *args): return _CppBlockUtils.BtcWallet_getUnconfirmedBalance(self, *args) NotImplementedError: Wrong number or type of arguments for overloaded function 'BtcWallet_getUnconfirmedBalance'. Possible C/C++ prototypes are: BtcWallet::getUnconfirmedBalance(uint32_t,bool) BtcWallet::getUnconfirmedBalance(uint32_t) Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on April 06, 2014, 03:14:44 PM Try .91
Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on April 06, 2014, 03:18:24 PM Sorry guys, running around like a chicken with my head cut off. I did post 0.91 yesterday. We have a conference tomorrow, and I'll be out for a few days. Of course changing from X.XX-testing to X.XX-beta broke the notifications... gonna have to tweak some things. But it is posted on our website. We'll send out something to the email list too :) (sign up on the webpage).
@forever3x: I am going to guess you have lots of transactions. Like thousands? We are aware that we have a problems with that, and we're not exactly sure of a good short-term solution. But any information about the wallet would be useful so we can try to run with a wallet like it to fix it in the future. Title: Re: Please Help Test Armory 0.91-beta! Post by: amix on April 06, 2014, 05:51:00 PM using armory .91 windows 7 x64 system. Receiving this error - dont think it completes downloading the block chain whne it springs up.
Microsoft Visual C++ Runtime Library Runtime Error! This application has requested the Runtime to terminate it in an unusual way. Please contact the applications support team for more information. been getting this for a while now - tried the updates, bitcoin updates too, reinstalled the c++ libraries no effect can anyone help out or point me in right direction please. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 07, 2014, 01:07:42 AM Anyone else getting a "Wallet Corruption Found!!!" error after installing either 0.90.99.7 or 0.91-beta? I'm a little concerned as it wants me to enter my pass phrase to fix the wallet. That means fix your wallet. It will appear again and again until you fix your wallet, as it will keep on running into the same wallet corruption. If you're uncertain about the corruption, copy and paste your error log in PMs, or create a ticket for it. using armory .91 windows 7 x64 system. Receiving this error - dont think it completes downloading the block chain whne it springs up. Microsoft Visual C++ Runtime Library Runtime Error! This application has requested the Runtime to terminate it in an unusual way. Please contact the applications support team for more information. been getting this for a while now - tried the updates, bitcoin updates too, reinstalled the c++ libraries no effect can anyone help out or point me in right direction please. Does Armory crash before you get to see the GUI, or do you crash halfway through sync/build/scan? Can you start Armory in offline mode? Title: Re: Please Help Test Armory 0.91-beta! Post by: forever3x on April 07, 2014, 01:15:56 AM @forever3x: I am going to guess you have lots of transactions. Like thousands? We are aware that we have a problems with that, and we're not exactly sure of a good short-term solution. But any information about the wallet would be useful so we can try to run with a wallet like it to fix it in the future. Sent you a PM. Thank you etotheipi. Title: Re: Please Help Test Armory 0.91-beta! Post by: Rampion on April 07, 2014, 09:57:24 AM Tested 0.91-beta on OSX 10.9.2
Beautiful update, only quirk is that it seems that one of the few bugs I had with 0.90-beta, which was Armory crashing after the system went on sleep and QT out of sync is still not solved... Now it doesn't crash completely, it just freezes and I have to force it to close. One of the updates I consider more important is the "safe download" option: I have to admit that downloading a new version from the webpage and verifying the files manually had me a little nervous, I feel much more comfortable by having a trusted and automatic way to download updates. Title: Re: Please Help Test Armory 0.91-beta! Post by: unbalancedeq on April 07, 2014, 11:09:36 AM Are there Version 0.91-beta: Signed hashes available? there doesn't seem to be a link on the download page
Title: Re: Please Help Test Armory 0.91-beta! Post by: Rampion on April 07, 2014, 11:19:20 AM Are there Version 0.91-beta: Signed hashes available? there doesn't seem to be a link on the download page FYI: Could someone tell me where to get the signed hash for the Mac version of 0.91? It seems to be missing from the download page. Thanks roy Sorry, my new release script forgot to pull it from the offline computer. It will be posted to the website shortly. Until then: https://s3.amazonaws.com/bitcoinarmory-media/armory_0.91-beta_sha256.txt.asc Title: Re: Please Help Test Armory 0.91-beta! Post by: amix on April 07, 2014, 03:31:45 PM Anyone else getting a "Wallet Corruption Found!!!" error after installing either 0.90.99.7 or 0.91-beta? I'm a little concerned as it wants me to enter my pass phrase to fix the wallet. That means fix your wallet. It will appear again and again until you fix your wallet, as it will keep on running into the same wallet corruption. If you're uncertain about the corruption, copy and paste your error log in PMs, or create a ticket for it. using armory .91 windows 7 x64 system. Receiving this error - dont think it completes downloading the block chain whne it springs up. Microsoft Visual C++ Runtime Library Runtime Error! This application has requested the Runtime to terminate it in an unusual way. Please contact the applications support team for more information. been getting this for a while now - tried the updates, bitcoin updates too, reinstalled the c++ libraries no effect can anyone help out or point me in right direction please. Does Armory crash before you get to see the GUI, or do you crash halfway through sync/build/scan? Can you start Armory in offline mode? Yes i get to see the GUI, and its appears to crash towards the end of the scan about 93%. And yes i can use it in offline mode. In both offline and normal mode my wallet balance is blank - is this normal until its completed the download of the block chain? it used to work fine and it was around the time i upgrade to bitcoin 0.9. so i downgraded which didnt help, also tried reinstalling both bitcoin and armory, and the runtime c++ library files. bitcoin is x64 - also tried the x86 build of bitcoin no joy. EDIT:: it crashes at 95% Title: Re: Please Help Test Armory 0.91-beta! Post by: runeks on April 08, 2014, 12:25:29 PM One small bug: in Settings, under "Set Armory as default URL handler", when I click "Set Armory as default", the popup that appears says:
Quote Armory just attempted to register itself to handle "bitcoin:" links, but this does not work on all operating systems. You can test it by going to the Bitcoin Armory website (https://bitcoinarmory.com/) and clicking the link at the bottom of the homepage. but there is no such link at the bottom of the homepage. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 09, 2014, 02:16:43 AM Yes i get to see the GUI, and its appears to crash towards the end of the scan about 93%. And yes i can use it in offline mode. In both offline and normal mode my wallet balance is blank - is this normal until its completed the download of the block chain? it used to work fine and it was around the time i upgrade to bitcoin 0.9. so i downgraded which didnt help, also tried reinstalling both bitcoin and armory, and the runtime c++ library files. bitcoin is x64 - also tried the x86 build of bitcoin no joy. EDIT:: it crashes at 95% First thing to do is to rebuild the database. Go to help -> Rebuild and Rescan Databases In offline mode you will never see your balance. You dont get to see your balance when trying to get online because it never finishes loading. If deleting the DB doesnt get you any further, create a ticket. Title: Re: Please Help Test Armory 0.91-beta! Post by: doug_armory on April 09, 2014, 02:28:08 AM Tested 0.91-beta on OSX 10.9.2 Beautiful update, only quirk is that it seems that one of the few bugs I had with 0.90-beta, which was Armory crashing after the system went on sleep and QT out of sync is still not solved... Now it doesn't crash completely, it just freezes and I have to force it to close. One of the updates I consider more important is the "safe download" option: I have to admit that downloading a new version from the webpage and verifying the files manually had me a little nervous, I feel much more comfortable by having a trusted and automatic way to download updates. Thanks for the compliments, and sorry to hear about the freezes. I've heard multiple reports about this. The weird thing is that I haven't been able to reproduce it yet! If you see this again, can you file a ticket and include the logs (/Users/(Your Username)/Library/Application Support/Armory/armorycpplog.txt and armorylog.txt)? While I'm here, thanks to everybody who came out to the Inside Bitcoins conference! It was great to hear the feedback - good and bad - about Armory and the Mac build. Keep the feedback and bug reports coming! Both help us improve Armory. Title: Re: Please Help Test Armory 0.91-beta! Post by: amix on April 10, 2014, 02:40:44 PM Yes i get to see the GUI, and its appears to crash towards the end of the scan about 93%. And yes i can use it in offline mode. In both offline and normal mode my wallet balance is blank - is this normal until its completed the download of the block chain? it used to work fine and it was around the time i upgrade to bitcoin 0.9. so i downgraded which didnt help, also tried reinstalling both bitcoin and armory, and the runtime c++ library files. bitcoin is x64 - also tried the x86 build of bitcoin no joy. EDIT:: it crashes at 95% First thing to do is to rebuild the database. Go to help -> Rebuild and Rescan Databases In offline mode you will never see your balance. You dont get to see your balance when trying to get online because it never finishes loading. If deleting the DB doesnt get you any further, create a ticket. Thanks that was just the trick its working perfectly now. I was wondering if updating the bitcoin-qt caused this as it seemed to work fine before i did that. Or is it just good practice to rebuild the database after an undate of either bitcoin or armoury? Or maybe it was something else i did around the same time that threw everything off...... Away it working fine now. Thanks soo much! Title: Re: Please Help Test Armory 0.91-beta! Post by: japandrew73 on April 10, 2014, 06:49:12 PM Running OSX 10.9.2, Bitcoin-qt 0.9.1, and Armory 0.91-beta.
I waited for Bitcoin Qt to download the entire block chain and now my satoshi client is synced up with the network 100% and acts normal. When I open Armory it says 1.5 Hours left for 'building databases' and doesn't move from that point. Also in the bottom right corner in green is says Connected (0 Blocks). Any help? I thought since my satoshi client already downloaded the entire blockchain that Armory would start working immediately? Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on April 10, 2014, 06:52:04 PM Running OSX 10.9.2, Bitcoin-qt 0.9.1, and Armory 0.91-beta. I waited for Bitcoin Qt to download the entire block chain and now my satoshi client is synced up with the network 100% and acts normal. When I open Armory it says 1.5 Hours left for 'building databases' and doesn't move from that point. Also in the bottom right corner in green is says Connected (0 Blocks). Any help? I thought since my satoshi client already downloaded the entire blockchain that Armory would start working immediately? No armory has its own database too now. It should be quick. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 10, 2014, 11:52:37 PM Thanks that was just the trick its working perfectly now. I was wondering if updating the bitcoin-qt caused this as it seemed to work fine before i did that. Or is it just good practice to rebuild the database after an undate of either bitcoin or armoury? Or maybe it was something else i did around the same time that threw everything off...... Away it working fine now. Thanks soo much! Not necessarely. The previous release (0.90) was the first version using LevelDB as our background engine for the DB. In this release (0.91) we tweaked LevelDB's settings to squeeze some extra speed. This is what made the older DBs incompatible with the newer ones. Chances are we won't touch these settings again, or at least not in the near future. Title: Re: Please Help Test Armory 0.91-beta! Post by: Carlton Banks on April 16, 2014, 10:49:42 PM Minor bug, not sure how long it's been there.
Using 'Simple' software keyboard for passphrase entry, the & character generates 2 keypresses (not sure if either of them is correct, I just used the hardware keyboard for that character) Title: Re: Please Help Test Armory 0.91-beta! Post by: mattbit on April 18, 2014, 09:26:31 AM Since a week ago, Armory is constantly crashing at 23% when scanning transaction history. I was using the previous stable release and tried upgrading to the beta version but it's still happening. Here is the log: .... Code: -INFO - 1396656713: (BlockUtils.cpp:4503) Processed 1 raw blocks DB (0 seconds) Haven't seen this one in a while, but we think it's caused by building your DB with the old version and corrupt blk*.dat files from Bitcoin Core. Since your DB is already built, you need to rebuild it with the new version. We'd love to know if this fixes your problem -- because we actually haven't run into the "don't-have-full-tx" problem on any of our own systems before, so we can't test whether we fixed it! So please use "Help"->Rebuild & Rescan Databases. With some luck that fixes it. If not, I recommend you do a factory reset and redownload the blockchain (because this is ultimately caused by bad blk*.dat files which will only be fixed with a redownload). With the new bittorrent stuff, it's a heck of a lot faster than it used to be! Thanks. It looks like this worked. I moved the blockchain files to another partition as my hard drive space was filling up. Perhaps during the copy some files got corrupted. Title: Re: Please Help Test Armory 0.91-beta! Post by: _r2h on April 18, 2014, 09:25:42 PM Any issues reported with the torrent download not working? Log reveals
Quote 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it None 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it for hours on end. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on April 18, 2014, 09:41:36 PM Any issues reported with the torrent download not working? Log reveals Quote 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it None 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it for hours on end. This is the first report we've heard of problems with torrent. It's been pretty reliable so far. It sounds like there's a corrupt block in the file being downloaded, and it's not recovering. I would close Armory, go into the Bitcoin homedir (C:\Users\<user>\AppData\Roaming\Bitcoin or /home/<user>/.bitcoin) and remove bootstrap.dat.partial and/or bootstrap.dat. Armory will restart the download next time you start it. Title: Re: Please Help Test Armory 0.91-beta! Post by: _r2h on April 19, 2014, 04:26:23 PM Any issues reported with the torrent download not working? Log reveals Quote 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it None 2014-04-18 16:23 (ERROR) -- torrentDL.pyc:303 - piece 7984 failed hash check, re-downloading it for hours on end. This is the first report we've heard of problems with torrent. It's been pretty reliable so far. It sounds like there's a corrupt block in the file being downloaded, and it's not recovering. I would close Armory, go into the Bitcoin homedir (C:\Users\<user>\AppData\Roaming\Bitcoin or /home/<user>/.bitcoin) and remove bootstrap.dat.partial and/or bootstrap.dat. Armory will restart the download next time you start it. I attempted a couple more times, always failed to sync a single block. Just downloaded another torrent of the blockchain and it recovered just fine. Armory is currently rebuilding it's database. Not really sure what the issue was. Title: Re: Please Help Test Armory 0.91-beta! Post by: chadwickx16 on April 23, 2014, 07:35:47 PM using armory .91 windows 7 x64 system. Receiving this error - dont think it completes downloading the block chain whne it springs up. Microsoft Visual C++ Runtime Library Runtime Error! This application has requested the Runtime to terminate it in an unusual way. Please contact the applications support team for more information. been getting this for a while now - tried the updates, bitcoin updates too, reinstalled the c++ libraries no effect can anyone help out or point me in right direction please. Getting this same error when building the database. I have done "Rebuild and Rescan Databases" after I received the C++ Error, now Armory crashes immediately upon opening in "Online Mode" works in "Offline Mode". I have upgraded to Bitcoin Core, and am in the process of reinstalling the C++ Libraries. Any other suggestions please? Thanks! Chad EDIT: Had corrupted blocks in Bitcoin Core. Problem solved. Title: Re: Please Help Test Armory 0.91-beta! Post by: Klazzik on April 26, 2014, 11:32:19 AM Hi,
I'm running Armory-0.91 on Linux, and it crashes after it finishes synchronizing with the network. Once it starts 'Building Databases' I see a 'Connected 0 blocks' at the bottom then it shuts down. Edit: it used to work fine a couple days ago. Edit #2: I was going to try to rebuild the database using Help > Rebuild and Rescan Databases but I don't even have a Help menu, not even that menu at the top. Is this supposed to be only on Windows clients? I don't remember ever having this! Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on April 26, 2014, 10:11:58 PM Hi, I'm running Armory-0.91 on Linux, and it crashes after it finishes synchronizing with the network. Once it starts 'Building Databases' I see a 'Connected 0 blocks' at the bottom then it shuts down. Edit: it used to work fine a couple days ago. Edit #2: I was going to try to rebuild the database using Help > Rebuild and Rescan Databases but I don't even have a Help menu, not even that menu at the top. Is this supposed to be only on Windows clients? I don't remember ever having this! What distro are you using? Title: Re: Please Help Test Armory 0.91-beta! Post by: 7queue on May 01, 2014, 05:28:48 PM Is this pop-up message legit?
Quote Your version of Armory is now outdated. Please upgrade to version 0.91.1 through our secure downloader inside Armory (link at the bottom of this notification window). Alternatively, you can get the new version from our website downloads page at: https://bitcoinarmory.com/download/#ubuntu I pull from git for both bitcoind and Armory, I don't see this version in git repository? Quote Loading Armory Engine: Armory Version: 0.91 PyBtcWallet Version: 1.35 Detected Operating system: Linux OS Variant : ('Ubuntu', '14.04', 'trusty') * remote origin Fetch URL: git://github.com/etotheipi/BitcoinArmory.git Push URL: git://github.com/etotheipi/BitcoinArmory.git HEAD branch: master Remote branches: 0.88 tracked 0.91-dev tracked . . Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) bitcoind 0.9.1 * remote origin Fetch URL: https://github.com/bitcoin/bitcoin.git Push URL: https://github.com/bitcoin/bitcoin.git HEAD branch: master Remote branches: . . 0.9.1 tracked blockheaders tracked freenode-verf tracked master tracked Local branch configured for 'git pull': 0.9.1 merges with remote 0.9.1 Local ref configured for 'git push': 0.9.1 pushes to 0.9.1 (up to date) 8 ) Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on May 01, 2014, 05:35:42 PM Yes, we just pushed the new version 0.91.1. It's actually on the testing branch, haven't merged it into master yet. But there is a signed tag for it:
https://github.com/etotheipi/BitcoinArmory/tree/v0.91.1 Title: Re: Please Help Test Armory 0.91-beta! Post by: PRab on May 01, 2014, 10:11:00 PM I just used the secure downloader and it added an extra "," to the end of the file name. I ended up getting "armory_0.91.1_winAll.exe.signed.exe," when I downloaded the file.
Edit: Ah, I realized that is a side effect of checking the "Save with offline-verifiable signature". I checked that expecting to get 2 files. The actual download and a signature file, but just got the 1 file with the botched filename. Edit2: Ok, I played around with it a little more. Once I got rid of the ".exe," from the end of the file I was able to use Help --> Verify Signed Package to verify it. I would still like to be able to do this manually, but couldn't figure out the right incantation to pass to gpg. Title: Re: Please Help Test Armory 0.91-beta! Post by: 7queue on May 01, 2014, 10:26:21 PM Thanks!
Up and running, looks good so far. 8 ) Title: Re: Please Help Test Armory 0.91-beta! Post by: prezbo on May 02, 2014, 03:37:06 PM Am I the only one having trouble downloading using the secure downloader? All I get is "There was a failure downloading this file: 0" message. Downloading bitcoin-core works fine though.
Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on May 03, 2014, 06:23:25 AM Am I the only one having trouble downloading using the secure downloader? All I get is "There was a failure downloading this file: 0" message. Downloading bitcoin-core works fine though. Perfect here Title: Re: Please Help Test Armory 0.91-beta! Post by: Roy Badami on May 03, 2014, 01:33:54 PM I see you've dropped the message 'No Wallet Error Found'.
The first time I saw that, my brain parsed it as 'Error: No Wallet Found' :-) Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on May 03, 2014, 01:39:02 PM I see you've dropped the message 'No Wallet Error Found'. The first time I saw that, my brain parsed it as 'Error: No Wallet Found' :-) Me too! Title: Re: Please Help Test Armory 0.91-beta! Post by: xe99 on May 03, 2014, 04:43:03 PM download links on first page are broken.
Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on May 03, 2014, 04:52:49 PM download links on first page are broken. About to release a new version, and the website is undergoing some updates too. Title: Re: Please Help Test Armory 0.91-beta! Post by: xe99 on May 03, 2014, 05:01:07 PM Ah! ok sounds good. will check back in a couple days.
Title: Re: Please Help Test Armory 0.91-beta! Post by: keewee on May 06, 2014, 09:29:26 AM Here's an easy one, I suspect :) On Mac OS X 10.9.2 Armory 0.91.1 failed to start because I had moved the app package to a folder in Applications called "Crypto Wallets". It does not like the space in the folder name. Once I renamed the folder to "CryptoWallets" everything worked fine.
Title: Re: Please Help Test Armory 0.91-beta! Post by: Rampion on May 06, 2014, 11:20:43 AM Should the signed version of Armory downloaded from the secure feature be verified offline? How risky is to verify it online?
Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on May 06, 2014, 12:40:46 PM Should the signed version of Armory downloaded from the secure feature be verified offline? How risky is to verify it online? You're already online so if they got you locally nothing you can do. If installing on offline then recheck. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on May 06, 2014, 02:47:46 PM If the offline computer is already upgraded to 0.91+, then you can use the secure downloader to grab the package and "Save with offline-verifiable signature". Then take that to the offline computer and use "Help"->"Verify Signed Package". That will check the offline Bitcoin signature and let you save the installer (only after the signature is verified).
This is specifically so you don't have to trust your online computer, and you don't have to deal with GPG. The Bitcoin signing key used here is handled at the same security level as the offline GPG key. Title: Re: Please Help Test Armory 0.91-beta! Post by: ACVentures on May 07, 2014, 12:52:00 AM I'm trying to use Armory online on an OSX 10.8.5
When upgrading from a perfectly working copy of 0.90 beta to the new 0.91.1 beta (and always checking to make sure the sig hash is correct) -> armory app will not even open. Does not load the main application window. Splash screen image for a few seconds, then generic OSX message informing me that Armory quit unexpectedly. Trying to reopen the app OSX again informs me that last time it was being opened it quit out, and asks if I'm sure to reopen. Always fails and crashes. Where can I mail the log file? What I think are the relevant bits (the crashed thread) are pasted below: Quote Thread 2 Crashed: 0 _CppBlockUtils.so 0x000000010580bbec InterfaceToLDB::getValueRef(DB_SELECT, BinaryDataRef) + 44 1 _CppBlockUtils.so 0x000000010580aafe InterfaceToLDB::getStoredDBInfo(DB_SELECT, StoredDBInfo&, bool) + 94 2 _CppBlockUtils.so 0x0000000105809d9a InterfaceToLDB::openDatabases(std::string, BinaryData const&, BinaryData const&, BinaryData const&, ARMORY_DB_TYPE, DB_PRUNE_TYPE) + 1242 3 _CppBlockUtils.so 0x000000010585806c BlockDataManager_LevelDB::initializeDBInterface(ARMORY_DB_TYPE, DB_PRUNE_TYPE) + 412 4 _CppBlockUtils.so 0x00000001058639a3 BlockDataManager_LevelDB::buildAndScanDatabases(bool, bool, bool, bool) + 403 5 _CppBlockUtils.so 0x0000000105a6906b _wrap_BlockDataManager_LevelDB_doInitialSyncOnLoad(_object*, _object*) + 107 6 org.python.python 0x00000001000afcb7 PyEval_EvalFrameEx + 20487 7 org.python.python 0x00000001000b2532 fast_function + 194 8 org.python.python 0x00000001000ade55 PyEval_EvalFrameEx + 12709 9 org.python.python 0x00000001000aaa41 PyEval_EvalCodeEx + 1729 10 org.python.python 0x0000000100035dac function_call + 364 11 org.python.python 0x0000000100010883 PyObject_Call + 99 12 org.python.python 0x00000001000ae17d PyEval_EvalFrameEx + 13517 13 org.python.python 0x00000001000aaa41 PyEval_EvalCodeEx + 1729 14 org.python.python 0x00000001000b2599 fast_function + 297 15 org.python.python 0x00000001000ade55 PyEval_EvalFrameEx + 12709 16 org.python.python 0x00000001000b2532 fast_function + 194 17 org.python.python 0x00000001000ade55 PyEval_EvalFrameEx + 12709 18 org.python.python 0x00000001000b2532 fast_function + 194 19 org.python.python 0x00000001000ade55 PyEval_EvalFrameEx + 12709 20 org.python.python 0x00000001000aaa41 PyEval_EvalCodeEx + 1729 21 org.python.python 0x0000000100035dac function_call + 364 22 org.python.python 0x0000000100010883 PyObject_Call + 99 23 org.python.python 0x000000010001d806 instancemethod_call + 166 24 org.python.python 0x0000000100010883 PyObject_Call + 99 25 org.python.python 0x00000001000b1cfd PyEval_CallObjectWithKeywords + 93 26 org.python.python 0x00000001000ec146 t_bootstrap + 70 27 libsystem_c.dylib 0x00007fff91b85772 _pthread_start + 327 28 libsystem_c.dylib 0x00007fff91b721a1 thread_start + 13 and from the armorylog.txt the very last few lines are: Quote 2014-05-06 19:57 (INFO) -- ArmoryQt.py:1794 - Setting up networking... 2014-05-06 19:57 (INFO) -- ArmoryQt.py:1846 - Internet connection is Available: True 2014-05-06 19:57 (INFO) -- ArmoryQt.py:1847 - Bitcoin-Qt/bitcoind is Available: 8333 2014-05-06 19:57 (INFO) -- ArmoryQt.py:1848 - The first blk*.dat was Available: True 2014-05-06 19:57 (INFO) -- ArmoryQt.py:1849 - Online mode currently possible: True 2014-05-06 19:57 (INFO) -- ArmoryQt.py:2036 - loadBlockchainIfNecessary 2014-05-06 19:57 (INFO) -- ArmoryQt.py:2082 - Setting netmode: 1 2014-05-06 19:57 (INFO) -- BDM.py:431 - Setting online mode: True (wait=False) 2014-05-06 19:57 (INFO) -- BDM.py:1357 - Go online requested 2014-05-06 19:57 (INFO) -- BDM.py:914 - Setting Armory Home Dir: /Users/REDACTED/Library/Application Support/Armory/ 2014-05-06 19:57 (INFO) -- BDM.py:915 - Setting BlkFile Dir: /Users/REDACTED/Library/Application Support/Bitcoin/blocks 2014-05-06 19:57 (INFO) -- BDM.py:916 - Setting LevelDB Dir: /Users/REDACTED/Library/Application Support/Armory/databases 2014-05-06 19:57 (INFO) -- ArmoryQt.py:1106 - setupUriRegistration And then something causes a hard crash. Also, I'm using the 0.9.1 core bitcoin-QT client and it shows that it's connected and sync'd fine, still receiving new blocks. Any ideas? Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on May 07, 2014, 02:19:46 AM If you updated from 0.90 to 0.91+, you most likely have to rebuild your databases.
Unfortunately, if you can't even get it to open, you'll have to manually delete the databases. On OSX it is under the following directory by default: ~/Library/Application Support/Armory/databases You can navigate to the Armory directory and delete the databases directory (which holds a lot of data). Next time you start Armory, it will rebuild and rescan, which might take a couple hours, but it should be smooth after that. Title: Re: Please Help Test Armory 0.91-beta! Post by: ACVentures on May 08, 2014, 05:57:15 AM If you updated from 0.90 to 0.91+, you most likely have to rebuild your databases. Unfortunately, if you can't even get it to open, you'll have to manually delete the databases. On OSX it is under the following directory by default: ~/Library/Application Support/Armory/databases You can navigate to the Armory directory and delete the databases directory (which holds a lot of data). Next time you start Armory, it will rebuild and rescan, which might take a couple hours, but it should be smooth after that. Yes, that fixed it, thanks. I suspected that would do the trick, but was hoping to avoid having Armory rescan the whole block chain. By the way, cool Secure Downloader feature. Did you just update Armor further? I downloaded 0.91.1 and initially had the error I posted about yesterday, successfully fixed it as you instructed, and now today the secure download area is saying there's a newer Armory version. Clicking it tells me it cant determine the correct version for my OS, and asks me to select from the list of all versions. The only version newer for OSX 10.8 is 0.91.2 but it's listed as a testing branch. Is that to be expected? Title: Re: Please Help Test Armory 0.91-beta! Post by: bitpop on May 08, 2014, 06:08:14 AM That's normal, same here on Windows
Really wish change log is included otherwise testing version looks scary Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on May 08, 2014, 02:13:50 PM Sorry about that -- we had to release a few tweaks to 0.91.1 to fix a wallet-recovery tool bug and some unicode path issues. I put it out as a testing release so it would be available and ready for people to download if needed, but wouldn't spam people with more notifications (of course, I forgot it's going to notify everyone with testing notifications on!). I'll try to give more of a heads up about it, next time.
Basically, unless you have path issues or wallet recovery tool issues, there's no real reason to upgrade to 0.91.2. Title: Re: Please Help Test Armory 0.91-beta! Post by: laurentb on May 08, 2014, 03:00:31 PM There is no git tag for 0.91.2, nor are there any tarball source releases on the website.
This is very inconvenient for packagers. Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on May 08, 2014, 03:02:52 PM There is no git tag for 0.91.2, nor are there any tarball source releases on the website. This is very inconvenient for packagers. Ye ask and ye shall receive: I just pushed the signed tag. I already had it the tag signed I just forgot to push it to the repo. We will eventually start doing source tarballs, but we have had a problem where it's bundling up the git repo itself, so the source tarballs are like 100 MB. Once we figure out how to get dpkg-build to stop doing that, we will add the tarballs to our regular release cycle. Title: Re: Please Help Test Armory 0.91-beta! Post by: laurentb on May 10, 2014, 02:11:26 PM Thanks!
I'm not sure I get what's happening, but git has a convenient "git archive" feature. Title: Re: Please Help Test Armory 0.91-beta! Post by: LunarBit on May 10, 2014, 04:55:00 PM Hello.
I have fatal error on "Build Databeses" step of Armory first run. The order in which I did everything: 1) Installed Armory. 2) Installed Bitcoin-qt. 3) Waited days for Bitcoin-qt to sync. 4) Opened Armory, it said it cant find anything. So I installed "bitcoind" through terminal. 5) Opened Armory again - it did "wallet check" and "initializing bitcoin engine", but after that - crash. I got fresh lastest Ubuntu, installed just for Bitcoin use. Please help. Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on May 10, 2014, 05:59:48 PM Hello. I have fatal error on "Build Databeses" step of Armory first run. The order in which I did everything: 1) Installed Armory. 2) Installed Bitcoin-qt. 3) Waited days for Bitcoin-qt to sync. 4) Opened Armory, it said it cant find anything. So I installed "bitcoind" through terminal. 5) Opened Armory again - it did "wallet check" and "initializing bitcoin engine", but after that - crash. I got fresh lastest Ubuntu, installed just for Bitcoin use. Please help. You should make a ticket for that... Are you using Ubuntu 14.xx? Title: Re: Please Help Test Armory 0.91-beta! Post by: LunarBit on May 11, 2014, 01:13:16 AM You should make a ticket for that... Are you using Ubuntu 14.xx? 13.10. Ticket where? Title: Re: Please Help Test Armory 0.91-beta! Post by: goatpig on May 11, 2014, 02:11:27 AM https://bitcoinarmory.com/support/
Title: Re: Please Help Test Armory 0.91-beta! Post by: bcbrad on May 11, 2014, 07:48:54 PM Please consider adding an indication the Caps Lock key is on for ANY password field. I had a minor meltdown today when trying to access a wallet I had recently set up. It turns out the Caps Lock key was inadvertently on when I originally typed the password (it's very easy to accidentally hit on my keyboard). I had my backup handy either way, but it was very frustrating not being able to access my wallet when I expected to. I even thought to check the Caps Lock state when failing to unlock my wallet and only much later had the idea to try it with Caps Lock on. Because I couldn't see the password when originally typing, I had no idea it was set incorrectly from the start.
A bright yellow indicator that Caps Lock is on for all password entry fields (setting and unlocking) would go a long way towards avoiding mistakes like this. Title: Re: Please Help Test Armory 0.91-beta! Post by: S5QUwMta4CM6 on May 12, 2014, 01:45:39 AM I have just upgraded to 0.91.1 and one of my wallets was corrupt. I tried to repair it and eventually restored it from a paper backup. I think about 90 per cent of my bitcoins are missing from the wallet. I think this is because no change has been restored to the wallet.
For example https://blockchain.info/tx/ca1c362e6c9130d1bee164613e1143ed60f6838bf129aba28791a8e0542174fb I sent 0.007727 BTC from 16Rj.. to 15jd.. and received 0.076973 in change to 14B1.. but 14B1.. is no longer associated with the spending wallet. I don't know the cause of this yet and I have opened a support ticket but I just want to send a word of caution - if Armory is working fine and you haven't upgraded yet, then think twice—unless you know what caused my problem and if you do, can you please let me know ??? Title: Re: Please Help Test Armory 0.91-beta! Post by: etotheipi on May 12, 2014, 02:35:09 AM I have just upgraded to 0.91.1 and one of my wallets was corrupt. I tried to repair it and eventually restored it from a paper backup. I think about 90 per cent of my bitcoins are missing from the wallet. I think this is because no change has been restored to the wallet. For example https://blockchain.info/tx/ca1c362e6c9130d1bee164613e1143ed60f6838bf129aba28791a8e0542174fb I sent 0.007727 BTC from 16Rj.. to 15jd.. and received 0.076973 in change to 14B1.. but 14B1.. is no longer associated with the spending wallet. I don't know the cause of this yet and I have opened a support ticket but I just want to send a word of caution - if Armory is working fine and you haven't upgraded yet, then think twice—unless you know what caused my problem and if you do, can you please let me know ??? We need people to upgrade. The upgrade itself is not responsible for any wallet issues -- any issues happened a while ago, it's upgrading that helps you identify that it happened. I found your support ticket and will respond shortly. We will get this fixed for you. Title: Re: Please Help Test Armory 0.91-beta! Post by: Rampion on May 12, 2014, 09:16:43 AM Two short questions:
If consistency check is OK on 0.9.1 then we are all good? 0.9.2 is still unstable and thus 0.9.1 is the recommended release? Thank you Alan. Title: Re: Please Help Test Armory 0.91-beta! Post by: S5QUwMta4CM6 on May 12, 2014, 11:03:07 AM I have just upgraded to 0.91.1 and one of my wallets was corrupt. I tried to repair it and eventually restored it from a paper backup. I think about 90 per cent of my bitcoins are missing from the wallet. I think this is because no change has been restored to the wallet. For example https://blockchain.info/tx/ca1c362e6c9130d1bee164613e1143ed60f6838bf129aba28791a8e0542174fb I sent 0.007727 BTC from 16Rj.. to 15jd.. and received 0.076973 in change to 14B1.. but 14B1.. is no longer associated with the spending wallet. I don't know the cause of this yet and I have opened a support ticket but I just want to send a word of caution - if Armory is working fine and you haven't upgraded yet, then think twice—unless you know what caused my problem and if you do, can you please let me know ??? We need people to upgrade. The upgrade itself is not responsible for any wallet issues -- any issues happened a while ago, it's upgrading that helps you identify that it happened. I found your support ticket and will respond shortly. We will get this fixed for you. Thanks for your prompt reply. I have also discovered in 0.91.1 that —performing a Wallet Recovery > Select Loaded Wallet brings up no data fields and no Spendable BTC. —a Full Recovery then results in "Wallet is consistent, nothing to fix" but all transaction balances are set to 0 (zero) with a 0.00 wallet balance. Quitting and restarting Armory will correct this and cause the previous balance to be displayed in that wallet again. This leads me to conclude there are other potential problems with 0.91.1 which are that
This is in addition to the problem above. Thanks. Title: Re: Please Help Test Armory 0.91-beta! Post by: ResonantBlue on November 01, 2014, 12:25:25 AM Hi, I'm running Armory-0.91 on Linux, and it crashes after it finishes synchronizing with the network. Once it starts 'Building Databases' I see a 'Connected 0 blocks' at the bottom then it shuts down. Edit: it used to work fine a couple days ago. Edit #2: I was going to try to rebuild the database using Help > Rebuild and Rescan Databases but I don't even have a Help menu, not even that menu at the top. Is this supposed to be only on Windows clients? I don't remember ever having this! I know this is an old topic, but I was recently getting the same results and couldn't figure out why. I am using Armory 0.92.3 (the 0.91-beta is history now) on Ubuntu 14.04.1 and every time it would get to the "Building Databases" section, it would crash right as it was beginning to rebuild the databases. However, I had my databases installed in a separate NTFS partition that I share with Windows. I don't know if that has anything to do with it but I figured I'd try and move my databases to the default /home/.armory directory to see if there was a difference. Now it's been building the databases for a while and it hasn't crashed. I wonder if any other Linux users have found problems when Armory is installed in a directory other than the default home directory. My brother recommended Armory, so I've been wanting to give it a try. However, he uses Windows and I use Linux so he's been using his for a while now and I've been struggling to get mine to work for the last couple of weeks. I'll report back later after I make more progress. |
