Armory - Discussion Thread

[goatpig]

Armory crashes for me also as soon as it gets 100% sync'd with the network.  Is there a debug log I can send the devs?

This is the win7 crash notes for what it's worth.

Are you syncing with a wallet loaded?

I get a crash on Windows 7 pretty much as soon as I try to start the program, with the testing version.

0.90-beta runs fine for me on Windows 7.

Rebuild your DB. We use a different leveldb block size in this version and that can mess up existing DBs.

[etotheipi]

Armory crashes for me also as soon as it gets 100% sync'd with the network.  Is there a debug log I can send the devs?

This is the win7 crash notes for what it's worth.

Are you syncing with a wallet loaded?

I get a crash on Windows 7 pretty much as soon as I try to start the program, with the testing version.

0.90-beta runs fine for me on Windows 7.

Rebuild your DB. We use a different leveldb block size in this version and that can mess up existing DBs.

I totally forgot about that!  Yes, we modified some DB parameters to improve performance of building and scanning, and it's necessarily incompatible with the old databases.   You will have to use "Help"->"Rebuild & Rescan Databases"

[goatpig]

https://bitcointalk.org/index.php?action=profile;u=253531

This user is spreading an Armory build in his profile. Obviously he isn't affiliated with us. Do not download this file. Make sure anything you download is served by our S3 servers and signed with etotheipi offline key.

[Winterfrost]

I totally forgot about that!  Yes, we modified some DB parameters to improve performance of building and scanning, and it's necessarily incompatible with the old databases.   You will have to use "Help"->"Rebuild & Rescan Databases"

I tried the "Rebuild & Rescan Databases", but it still crashes once it's finished syncing with the network.

[etotheipi]

I totally forgot about that!  Yes, we modified some DB parameters to improve performance of building and scanning, and it's necessarily incompatible with the old databases.   You will have to use "Help"->"Rebuild & Rescan Databases"

I tried the "Rebuild & Rescan Databases", but it still crashes once it's finished syncing with the network.

Can you send us a log file?  Or post any seemingly-relevant errors you see at the end of of armorylog.txt or armorycpplog.txt?   It's especially interesting to us if the DB build & scan used to work but doesn't with the new version (because we added stuff that was intended to catch and handle errors in blk*.dat files... maybe that code is misbehaving?)

[Winterfrost]

Can you send us a log file?  Or post any seemingly-relevant errors you see at the end of of armorylog.txt or armorycpplog.txt?   It's especially interesting to us if the DB build & scan used to work but doesn't with the new version (because we added stuff that was intended to catch and handle errors in blk*.dat files... maybe that code is misbehaving?)

This is at the end of armorycpplog.txt:

Code:

Log file opened at 1393379181: C:\Users\username\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1393379211: (..\BlockUtils.cpp:1579) Set home directory: 
-INFO  - 1393379211: (..\BlockUtils.cpp:1601) Set blkfile dir: C:\Users\username\AppData\Roaming\Bitcoin\blocks
-INFO  - 1393379211: (..\BlockUtils.cpp:1611) Set leveldb dir: C:\Users\username\AppData\Roaming\Armory\databases
-INFO  - 1393379211: (..\BlockUtils.cpp:1567) SetBtcNetworkParams
-INFO  - 1393379211: (..\BlockUtils.cpp:3628) Executing: doInitialSyncOnLoad_Rebuild
-INFO  - 1393379211: (..\BlockUtils.cpp:3653) Number of registered addr: 485
-INFO  - 1393379211: (..\leveldb_wrapper.cpp:399) Opening databases...
-WARN  - 1393379211: (..\leveldb_wrapper.cpp:303) ***LevelDB Error: IO error: C:\Users\username\AppData\Roaming\Armory\databases/leveldb_headers: Bad file descriptor
-ERROR - 1393379211: (..\leveldb_wrapper.cpp:453) Failed to open database! DB: 0

Armorylog.txt doesn't have anything that looks unusual, but I can send it to you if you need more info.

[goatpig]

This is at the end of armorycpplog.txt:

Code:

Log file opened at 1393379181: C:\Users\username\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1393379211: (..\BlockUtils.cpp:1579) Set home directory: 
-INFO  - 1393379211: (..\BlockUtils.cpp:1601) Set blkfile dir: C:\Users\username\AppData\Roaming\Bitcoin\blocks
-INFO  - 1393379211: (..\BlockUtils.cpp:1611) Set leveldb dir: C:\Users\username\AppData\Roaming\Armory\databases
-INFO  - 1393379211: (..\BlockUtils.cpp:1567) SetBtcNetworkParams
-INFO  - 1393379211: (..\BlockUtils.cpp:3628) Executing: doInitialSyncOnLoad_Rebuild
-INFO  - 1393379211: (..\BlockUtils.cpp:3653) Number of registered addr: 485
-INFO  - 1393379211: (..\leveldb_wrapper.cpp:399) Opening databases...
-WARN  - 1393379211: (..\leveldb_wrapper.cpp:303) ***LevelDB Error: IO error: C:\Users\username\AppData\Roaming\Armory\databases/leveldb_headers: Bad file descriptor
-ERROR - 1393379211: (..\leveldb_wrapper.cpp:453) Failed to open database! DB: 0

Armorylog.txt doesn't have anything that looks unusual, but I can send it to you if you need more info.

Delete this folder yourself: C:\Users\username\AppData\Roaming\Armory\databases

Then try again.

Edit: Found a bug related to this and fixed it. Pull the testing branch or wait for the next testing build to try it out.

[_r2h]

Armory crashes for me also as soon as it gets 100% sync'd with the network.  Is there a debug log I can send the devs?

This is the win7 crash notes for what it's worth.

Are you syncing with a wallet loaded?

I get a crash on Windows 7 pretty much as soon as I try to start the program, with the testing version.

0.90-beta runs fine for me on Windows 7.

Rebuild your DB. We use a different leveldb block size in this version and that can mess up existing DBs.

I do have one wallet loaded.

ArmoryQt.exe.log

(ERROR) ArmoryQt.py:746 - 7 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:751 - File mempool.bin does not exist. Nothing deleted.
(ERROR) ArmoryQt.py:746 - 8 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:751 - File mempool.bin does not exist. Nothing deleted.

[Winterfrost]

Delete this folder yourself: C:\Users\username\AppData\Roaming\Armory\databases

Then try again.

Edit: Found a bug related to this and fixed it. Pull the testing branch or wait for the next testing build to try it out.

Just tried that and it still crashes with the same error message. Once the next beta build comes out I'll let you know if it works.

[QuantumQrack]

I keep getting this error when I want to start Armory.  It basically forces me to restart my computer to get rid of it.  And no, Armory nor bitcoind is running.  Thank you for any assistance with this.  Also, I can tip for assistance with this.

[goatpig]

I keep getting this error when I want to start Armory.  It basically forces me to restart my computer to get rid of it.  And no, Armory nor bitcoind is running.  Thank you for any assistance with this.  Also, I can tip for assistance with this.

Make sure you kill all instances of Python before trying to rerun Armory.

[QuantumQrack]

I keep getting this error when I want to start Armory.  It basically forces me to restart my computer to get rid of it.  And no, Armory nor bitcoind is running.  Thank you for any assistance with this.  Also, I can tip for assistance with this.

Make sure you kill all instances of Python before trying to rerun Armory.

Ok, I shut down all instances of Chrome, and Armory launched normally.  Thanks.  

[bronan]

I see armory started bitcoind then after 12 hours it was 99% 0 blocks
Then 2 days nothing no movement nor changes nothing just showing 99% 0 blocks
can not open the wallet nothing moves
When i start bitcoin-qt or bitcoind direct they open nromally after the endless check they allways do
Restarting armory gives the same it shows the 99% and 0 blocks and thats it

this is showed in the log :

2014-02-25 21:02 (INFO) -- ArmoryQt.py:4647 - Starting load blockchain
2014-02-25 21:02 (INFO) -- ArmoryQt.py:1434 - loadBlockchainIfNecessary
2014-02-25 21:02 (INFO) -- ArmoryQt.py:1480 - Setting netmode: 0
2014-02-25 21:02 (INFO) -- armoryengine.pyc:12526 - Setting online mode: False (wait=False)
2014-02-25 21:02 (INFO) -- ArmoryQt.py:4982 - BDM is safe for clean shutdown
2014-02-25 21:02 (INFO) -- armoryengine.pyc:13435 - Shutdown Requested
2014-02-25 21:02 (ERROR) -- armoryengine.pyc:13216 - Resetting BDM and all wallets
2014-02-25 21:02 (INFO) -- armoryengine.pyc:13481 - BDM is shutdown.
2014-02-25 21:02 (INFO) -- armoryengine.pyc:11263 - Called stopBitcoind
2014-02-25 21:02 (WARNING) -- armoryengine.pyc:661 - Killing process pid=872
2014-02-25 21:02 (WARNING) -- armoryengine.pyc:661 - Killing process pid=6248
2014-02-25 21:02 (INFO) -- ArmoryQt.py:5010 - Attempting to close the main window!
2014-02-25 21:02 (ERROR) -- ArmoryQt.py:4339 - BitcoindNotAvailable: should not happen...
2014-02-25 21:02 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Offline"
2014-02-25 21:02 (INFO) -- ArmoryQt.py:5121 - Resetting BlockDataMgr, freeing memory

[RoadStress]

I keep getting this error when I want to start Armory.  It basically forces me to restart my computer to get rid of it.  And no, Armory nor bitcoind is running.  Thank you for any assistance with this.  Also, I can tip for assistance with this.

Make sure you kill all instances of Python before trying to rerun Armory.

How hard would it be to make it support multiple instances?

[Ente]

I keep getting this error when I want to start Armory.  It basically forces me to restart my computer to get rid of it.  And no, Armory nor bitcoind is running.  Thank you for any assistance with this.  Also, I can tip for assistance with this.

Make sure you kill all instances of Python before trying to rerun Armory.

How hard would it be to make it support multiple instances?

Try running bitcoind and armory two times, in its own folder each.
This should work.
Then you can connect one bitcoind to the other. They both have the whole blockchain, still, but only one connects to nodes outside and creates traffic.

I don't think it's possible to share the bitcoind-blockchain nor the armory-blocks between several instances.

Well, I run several "instances" in the form of several wallets in one armory. Close enough for me :-)

Ente

[etotheipi]

How hard would it be to make it support multiple instances?

It can be done, but it's made intentionally difficult, because running two instances of Armory using the same wallets is guaranteed to corrupt your wallets.  And of course, all the extra data... most of the time the user simply double-clicked to open it again, not realizing it's already open.

If you really want to do it for whatever reason, then you can open the second Armory instance using

Code:

 --datadir=/path/to/second/armory --interport=7890

Interport can be any unused port, and is only for detecting multiple instances (which is why you must change it to run multiple).  You must change both datadir and interport at the same time if you don't want to corrupt your existing wallets.

[WiiD]

Is it normal that my online wallet has to do "Scanning Transaction History" for about 2 hours every time i start Armory??? So when Bitcoin crashes i need over 2 hours to get my BTC out of Armory Wallet??

[etotheipi]

Is it normal that my online wallet has to do "Scanning Transaction History" for about 2 hours every time i start Armory??? So when Bitcoin crashes i need over 2 hours to get my BTC out of Armory Wallet??

Kind of.  There's a bug in 0.90-beta, that forces it to rescan way more often than it needs to.  This is dramatically improved in the new testing version (0.91).  It won't rescan unless you just import addresses or wallets. 

Unfortunately, if you leave Armory off for a couple weeks, it has to catch up with the latest blockchain history, which can be kind of slow (though it should only be a few minutes).  But there's not much we can do about it.

[teste]

Ok,

I created a wallet on Armory and I have a paper backup.
My question is:
1- I see web wallets that already implemented bip32 where an address that starts with (3) 3J5emZhKuLWyW292dFgDo1YhFN1MWVyV13 is created. Is it right that I can send bitcoins to this address and for each transaction will be created a new address that start with (1)?
2- When Armory implement bip32, will I need to create a new backup?

[etotheipi]

Ok,

I created a wallet on Armory and I have a paper backup.
My question is:
1- I see web wallets that already implemented bip32 where an address that starts with (3) 3J5emZhKuLWyW292dFgDo1YhFN1MWVyV13 is created. Is it right that I can send bitcoins to this address and for each transaction will be created a new address that start with (1)?
2- When Armory implement bip32, will I need to create a new backup?

The addresses that start with "3" are P2SH addresses, usually used for multisig.  Armory version 0.90 and previous did not support sending to these addreses, but the new version to be released soon (0.91) will allow it.  It's up to them to deal with their own P2SH addresses, and how to create and spend from them.  But Armory will keep using the ones that start with "1", such as creating change addresses that start with "1".  Armory has no mechanism to spend multisig txOuts, even if it has some of the private keys.

As soon as this next version is out, my number one priority is finishing the new wallet design, which will suppot BIP32, multisig, P2SH, compressed keys, and a variety of other things.  It will also allow you to migrate your existing wallet to the new format, and continue using your existing wallets.  Though you won't get the benefits of the new BIP32 stuff.