Topic: Armory - Discussion Thread - page 118. (Read 521761 times)
I have just started encountering an issue which prevents the blockchain from loading. I have 0.87.2-beta, it worked perfectly the first few times, and I didn't open it for awhile. Now every time I try to open it I get a runtime error. I have already un-installed and re-installed armory. What should I try now? I have both wallets backed up and paper wallets made for each as well.
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Same behavior in 0.88.2.
Effectively, I can only sign messages with keys from unencrypted wallets, or copy a privkey manually into the window.
Encrypted or offline wallets don't work or crash Armory completely.
I, personally, simply removed encryption for a minute and re-encrypted it after my message was signed.
I almost feel bad reporting a bug, I love Armory so much! :-)
Ente
Because of the incompatibility with Bitcoin-Qt (and thus, lack of usefulness), I haven't really maintained that interface at all. I was waiting for the message signing bounty, and then I was going to redo the whole interface.
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Same behavior in 0.88.2.
Effectively, I can only sign messages with keys from unencrypted wallets, or copy a privkey manually into the window.
Encrypted or offline wallets don't work or crash Armory completely.
I, personally, simply removed encryption for a minute and re-encrypted it after my message was signed.
I almost feel bad reporting a bug, I love Armory so much! :-)
Ente
New day, freshly booted debian, now it works as expected! Connected, online, transactions, blockcount.
No idea what was going on, will dig deeper if it happens again.
Will check back on message signing after work!
Glad it's working!
I wouldn't hold your breath about message signing, unless it's Armory-to-Armory. I will eventually merge jackjack's message signing (from a bounty) into Armory... but it's not there yet
Yes, I am talking about regular Armory-signing.
I am following the work and progress of jackjack closely though, I like where this is going! :-)
Ente
New day, freshly booted debian, now it works as expected! Connected, online, transactions, blockcount.
No idea what was going on, will dig deeper if it happens again.
Will check back on message signing after work!
Glad it's working!
I wouldn't hold your breath about message signing, unless it's Armory-to-Armory. I will eventually merge jackjack's message signing (from a bounty) into Armory... but it's not there yet
I just updated Armory:
..and am now on 0.88.2.
After scanning it says "Armory is online!", shows the balances of the wallets, shows no tx, and says "connected (0 blocks)".
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Again, this was not the most recent version.
Now, with 0.88.2 and "0 blocks", signing doesn't work. Which is no surprise, I'll check again when I have it online and connected ;-)
Thank you for hints. Tomorrow I'll try to dig a bit deeper, sorry for no log yet.
Ente
Code:
cd /opt/BitcoinArmory/
git checkout testing
git pull origin testing
make clean
make
..and am now on 0.88.2.
After scanning it says "Armory is online!", shows the balances of the wallets, shows no tx, and says "connected (0 blocks)".
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Again, this was not the most recent version.
Now, with 0.88.2 and "0 blocks", signing doesn't work. Which is no surprise, I'll check again when I have it online and connected ;-)
Thank you for hints. Tomorrow I'll try to dig a bit deeper, sorry for no log yet.
Ente
New day, freshly booted debian, now it works as expected! Connected, online, transactions, blockcount.
No idea what was going on, will dig deeper if it happens again.
Will check back on message signing after work!
Cheers!
Ente
Have you made any commits to you local repository?
Nope, nothing.
Except changing the linked python module in the makefile, several versions ago.
Ente
I just updated Armory:
..and am now on 0.88.2.
After scanning it says "Armory is online!", shows the balances of the wallets, shows no tx, and says "connected (0 blocks)".
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Again, this was not the most recent version.
Now, with 0.88.2 and "0 blocks", signing doesn't work. Which is no surprise, I'll check again when I have it online and connected ;-)
Thank you for hints. Tomorrow I'll try to dig a bit deeper, sorry for no log yet.
Ente
Code:
cd /opt/BitcoinArmory/
git checkout testing
git pull origin testing
make clean
make
..and am now on 0.88.2.
After scanning it says "Armory is online!", shows the balances of the wallets, shows no tx, and says "connected (0 blocks)".
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Again, this was not the most recent version.
Now, with 0.88.2 and "0 blocks", signing doesn't work. Which is no surprise, I'll check again when I have it online and connected ;-)
Thank you for hints. Tomorrow I'll try to dig a bit deeper, sorry for no log yet.
Ente
Have you made any commits to you local repository?
I just updated Armory:
..and am now on 0.88.2.
After scanning it says "Armory is online!", shows the balances of the wallets, shows no tx, and says "connected (0 blocks)".
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Again, this was not the most recent version.
Now, with 0.88.2 and "0 blocks", signing doesn't work. Which is no surprise, I'll check again when I have it online and connected ;-)
Thank you for hints. Tomorrow I'll try to dig a bit deeper, sorry for no log yet.
Ente
Code:
cd /opt/BitcoinArmory/
git checkout testing
git pull origin testing
make clean
make
..and am now on 0.88.2.
After scanning it says "Armory is online!", shows the balances of the wallets, shows no tx, and says "connected (0 blocks)".
On another note, I played with message signing a bit, before I updated.
It seems like I can't sign with keys in encrypted wallets (not asked for password, nothing happens). When trying with an offline wallet, Armory closes completely.
Again, this was not the most recent version.
Now, with 0.88.2 and "0 blocks", signing doesn't work. Which is no surprise, I'll check again when I have it online and connected ;-)
Thank you for hints. Tomorrow I'll try to dig a bit deeper, sorry for no log yet.
Ente
I really like the way bounties are handled at i2p project:
http://www.i2p2.de/bounties.html
Maybe a page like that would be cool. You could make a list of things that need to get done. Users like myself can donate to the bounties they are most interested in. Devs currently working on the project get listed, including collaborative projects. And once it makes it to the client the devs get paid.
Seems very efficient to me.
Some quite old bounties waiting there, it seems.
18 BTC, 50 BTC, 118 BTC.
Interesting. Interesting indeed.
Ente
The 118 BTC one is done already. It's just awaiting verification. But the other ones are still open for the taking.
I really like the way bounties are handled at i2p project:
http://www.i2p2.de/bounties.html
Maybe a page like that would be cool. You could make a list of things that need to get done. Users like myself can donate to the bounties they are most interested in. Devs currently working on the project get listed, including collaborative projects. And once it makes it to the client the devs get paid.
Seems very efficient to me.
Some quite old bounties waiting there, it seems.
18 BTC, 50 BTC, 118 BTC.
Interesting. Interesting indeed.
Ente
I also have this problem. When I send money to a wallet it never updates the confirmation count until I restart the program.
I assume you're using the latest version? That was a problem in version 0.87 that was fixed in 0.87.2 and higher.
If it's happening in the latest version... please send me a log file.
My clock is on time, May 22nd 18:57 here now.
After leaving it running for a while (and possibly receiving a new block while running?), it shows the right time for "last block received": https://i.imgur.com/XNseGXa.png
Could it be that the "last block received" timestamp is wrong if I close Armory, run bitcoind by itself for a while (receiving some blocks), then start up Armory again, and it only updates the timestamp when it itself receives new blocks?
After leaving it running for a while (and possibly receiving a new block while running?), it shows the right time for "last block received": https://i.imgur.com/XNseGXa.png
Could it be that the "last block received" timestamp is wrong if I close Armory, run bitcoind by itself for a while (receiving some blocks), then start up Armory again, and it only updates the timestamp when it itself receives new blocks?
I actually don't know what would cause that. It always goes by the timestamp on the block, which we know can't be more than 2 hours off. So 2 days would have to be... either a clock issue, or maybe somehow Armory glitched and was getting the wrong value out of "RightNow()"...?
1. Close Armory
2. Start bitcoind, let it run for a while (say 2 hours)
3. Open Armory and let it scan the block chain (no new blocks must come in while it's scanning)
4. After it's done, observe that the tooltip for the green "Connected (x blocks)" in the lower right corner is from when Armory was running last, not from the newest block
5. Wait until a new block comes in while Armory is running. When it does, the tooltip will have the timestamp for the new block that just came in
It appears to me that upon receiving a new block, while Armory is running, it will write the timestamp to the 'LastBlkRecvTime' setting:
ArmoryQt.py line 4475:
Code:
if newBlocks>0 and not TheBDM.isDirty():
[...]
self.blkReceived = RightNow()
self.writeSetting('LastBlkRecvTime', self.blkReceived)
self.writeSetting('LastBlkRecv', self.currBlockNum)
[...]
When Armory is started the next time, it will load this value from the ArmorySettings.txt file, and it won't be updated until it enters the above if-clause, and this only happens when "newBlocks > 0", which I presume isn't the case unless a new block is received while Armory is running.
But I'm not really familiar with the code. The only thing I can see is that it uses the value read from the settings file, and not from the newest block that it reads from disk.
I also have this problem. When I send money to a wallet it never updates the confirmation count until I restart the program.
Quote
Second of all, can you double click that strange transaction and you'll see why it thinks it was +0.00000010 BTC instead of the correct amount. Specifically, it should show you all the inputs and outputs, and then label which ones are part of your wallet.
The 10-Satoshi transaction is correct. I just realized that the 0.20 BTC transaction isn't in a block yet; it's unconfirmed: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJIt's apparently been sitting there for 2.5 hours without being picked up.
Even if it's unconfirmed, it shouldn't be showing the wrong value like that. Can you just check the "Transaction Details" and verify which inputs and outputs it thinks are part of your wallet?
One transaction of 0.0000001 BTC which has 28 confirmations.
One transaction of 0.2084164 BTC which is unconfirmed. Armory wasn't open when it was sent out.
Armory only displays the first transaction (of 10 satoshis), not the second one, which makes sense since the second one is not in a block, and Armory wasn't open when it was sent out.
My clock is on time, May 22nd 18:57 here now.
After leaving it running for a while (and possibly receiving a new block while running?), it shows the right time for "last block received": https://i.imgur.com/XNseGXa.png
Could it be that the "last block received" timestamp is wrong if I close Armory, run bitcoind by itself for a while (receiving some blocks), then start up Armory again, and it only updates the timestamp when it itself receives new blocks?
After leaving it running for a while (and possibly receiving a new block while running?), it shows the right time for "last block received": https://i.imgur.com/XNseGXa.png
Could it be that the "last block received" timestamp is wrong if I close Armory, run bitcoind by itself for a while (receiving some blocks), then start up Armory again, and it only updates the timestamp when it itself receives new blocks?
I actually don't know what would cause that. It always goes by the timestamp on the block, which we know can't be more than 2 hours off. So 2 days would have to be... either a clock issue, or maybe somehow Armory glitched and was getting the wrong value out of "RightNow()"...?
Quote
Second of all, can you double click that strange transaction and you'll see why it thinks it was +0.00000010 BTC instead of the correct amount. Specifically, it should show you all the inputs and outputs, and then label which ones are part of your wallet.
The 10-Satoshi transaction is correct. I just realized that the 0.20 BTC transaction isn't in a block yet; it's unconfirmed: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJIt's apparently been sitting there for 2.5 hours without being picked up.
Even if it's unconfirmed, it shouldn't be showing the wrong value like that. Can you just check the "Transaction Details" and verify which inputs and outputs it thinks are part of your wallet?
I'm having problems with Armory not picking up transactions.
Armory is up to date (shows the newest block in the lower right corner), yet it says this is 2 days old, which blockchain.info confirms that it's not.
Secondly, it's not picking up all the funds sent to the address displayed as "ASICMINER dividend". I've received 0.20 BTC to that address, but only 10 Satoshis are displayed as received: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJ
What gives?
Armory is up to date (shows the newest block in the lower right corner), yet it says this is 2 days old, which blockchain.info confirms that it's not.
Secondly, it's not picking up all the funds sent to the address displayed as "ASICMINER dividend". I've received 0.20 BTC to that address, but only 10 Satoshis are displayed as received: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJ
What gives?
Interesting.
First of all, if it says the block is 2 days old, the only way I can see that is if your clock is 2 days fast. You're right, it's definitely at the latest block. But having your clock off would interfere with a few things that Armory does.
After leaving it running for a while (and possibly receiving a new block while running?), it shows the right time for "last block received".
Could it be that the "last block received" timestamp is wrong if I close Armory, run bitcoind by itself for a while (receiving some blocks), then start up Armory again, and it only updates the timestamp when it itself receives new blocks?
Quote
Second of all, can you double click that strange transaction and you'll see why it thinks it was +0.00000010 BTC instead of the correct amount. Specifically, it should show you all the inputs and outputs, and then label which ones are part of your wallet.
The 10-Satoshi transaction is correct. I just realized that the 0.20 BTC transaction isn't in a block yet; it's unconfirmed: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJIt's apparently been sitting there for 2.5 hours without being picked up.
I'm having problems with Armory not picking up transactions.
It's up-to-date, seemingly. It has the newest block (237384), yet it says this is 2 days old, which blockchain.info confirms that it's not
Secondly, it's not picking up all the funds sent to the address displayed as "ASICMINER dividend". I've received 0.20 BTC to that address, but only 10 Satoshis are displayed as received: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJ
What gives?
It's up-to-date, seemingly. It has the newest block (237384), yet it says this is 2 days old, which blockchain.info confirms that it's not
Secondly, it's not picking up all the funds sent to the address displayed as "ASICMINER dividend". I've received 0.20 BTC to that address, but only 10 Satoshis are displayed as received: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJ
What gives?
Interesting.
First of all, if it says the block is 2 days old, the only way I can see that is if your clock is 2 days fast. You're right, it's definitely at the latest block. But having your clock off would interfere with a few things that Armory does.
Second of all, can you double click that strange transaction and you'll see why it thinks it was +0.00000010 BTC instead of the correct amount. Specifically, it should show you all the inputs and outputs, and then label which ones are part of your wallet.
I know it can be pain to restart, but I've seen something like what you are showing after a reorg, and I know there was just one in the last few hours. Have you restarted Armory since then?
I'm having problems with Armory not picking up transactions.
Armory is up to date (shows the newest block in the lower right corner), yet it says this is 2 days old, which blockchain.info confirms that it's not.
Secondly, it's not picking up all the funds sent to the address displayed as "ASICMINER dividend". I've received 0.20 BTC to that address, but only 10 Satoshis are displayed as received: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJ
What gives?
Armory is up to date (shows the newest block in the lower right corner), yet it says this is 2 days old, which blockchain.info confirms that it's not.
Secondly, it's not picking up all the funds sent to the address displayed as "ASICMINER dividend". I've received 0.20 BTC to that address, but only 10 Satoshis are displayed as received: https://blockchain.info/address/1MtH2DDbuRr8kNStJsQMDWNfhs9qwTNqAJ
What gives?
I would suggest something akin to bitcoind's gitian build process. I have experience forking that for Freicoin-Qt and Open-Transactions:
https://github.com/freicoin/freicoin/tree/master/contrib/vagrant
https://github.com/freicoin/freicoin/tree/master/contrib/vagrant
Jump to: