Pages:
Author

Topic: Armory 0.95.1 is out - page 3. (Read 12835 times)

frx
newbie
Activity: 13
Merit: 0
February 24, 2017, 12:19:21 PM
Thanks for your reply. Sure, I will make a new vm to test the testing version. I will let you know.
legendary
Activity: 3640
Merit: 1345
Armory Developer
February 24, 2017, 12:11:46 PM
I have been using Armory for some years and recently I installed this new version. I installed it in fresh ubuntu install and I got many problems to make it work. One of the problems was Armory not being able to talk to bitcoind (RPC error in log). I saw some people had this issue and fixed it unchecking the option (Let armory execute bitcoind.....). I did this and it appears is working... but I am still not sure 100% is working.

This should improve a lot in 0.96

Quote
What happens now is. Having Armory empty (without wallets), it says is online and synced. I close armory, I open it again. It starts building databases, just a few minutes (around 5) and then starts "Organizing blockchain". Problem is... it take hours! Even having Armory synced and online, if I close it, and in order to having working again I have to wait 3h. This does not make too much sense as you have the wallet online, and suddenly if you close you have to wait 3h again.. so is this an issue? normal behavior? Just in case, I run armory in virtual machine, but I have always done this without problems like this one.

Sounds like a bug. You should participate to the 0.96 testing phase going on atm and help me debug the issue:

https://bitcointalksearch.org/topic/096-preliminary-testing-1784442
frx
newbie
Activity: 13
Merit: 0
February 24, 2017, 10:48:26 AM
Hi,

First, thanks goatpig for all your effort to keep this project alive.

I have been using Armory for some years and recently I installed this new version. I installed it in fresh ubuntu install and I got many problems to make it work. One of the problems was Armory not being able to talk to bitcoind (RPC error in log). I saw some people had this issue and fixed it unchecking the option (Let armory execute bitcoind.....). I did this and it appears is working... but I am still not sure 100% is working.

What happens now is. Having Armory empty (without wallets), it says is online and synced. I close armory, I open it again. It starts building databases, just a few minutes (around 5) and then starts "Organizing blockchain". Problem is... it take hours! Even having Armory synced and online, if I close it, and in order to having working again I have to wait 3h. This does not make too much sense as you have the wallet online, and suddenly if you close you have to wait 3h again.. so is this an issue? normal behavior? Just in case, I run armory in virtual machine, but I have always done this without problems like this one.

Thanks!
legendary
Activity: 3640
Merit: 1345
Armory Developer
February 15, 2017, 10:40:56 AM
0.92 can sign for 0.95, sure.
full member
Activity: 204
Merit: 100
February 15, 2017, 10:27:43 AM
Ok suppose it would be OK to use the newest older version that did support 32 ?
staff
Activity: 3374
Merit: 6530
Just writing some code
February 14, 2017, 04:09:05 PM
Supposer I would need a 32 version. Is there any solution, thanks?
Unfortunately we no longer support 32 bit OSes.
full member
Activity: 204
Merit: 100
February 14, 2017, 04:03:45 PM
Hi using an older computer with Ubuntu 14.04 lts

Tried installing this version:

/Downloads/armory$ sudo dpkg -i armory_0.95.1_amd64.deb

 but got:

error processing archive armory_0.95.1_amd64.deb (--install):
 package architecture (amd64) does not match system (i386)

Supposer I would need a 32 version. Is there any solution, thanks?
newbie
Activity: 7
Merit: 0
February 08, 2017, 10:49:11 AM
after this
I tried the following settings:  going to File > Settings and uncheck the box for "Let Armory run Bitcoin Core in the background". Then Stop Armory and start Bitcoin Core and Armory manually.

I get this Info

ERROR - 1486565046: (..\BlockDataMap.cpp:81)    block yields: 605dab8dc7bfc8f90128357807b0f4da269edb32d14cb5395a96792b52a6301d
-ERROR - 1486565046: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO  - 1486565046: (..\DatabaseBuilder.cpp:268) parsed block file #278
-DEBUG - 1486565047: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1486565195: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 193.087s
-INFO  - 1486565195: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1486565195: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486565195: (..\BlockDataMap.cpp:80)    header has: 74e2b0169a6fe4d8bf17c59babd5ba31871acd1c2e7437c77cae9512b945f5e2
-ERROR - 1486565195: (..\BlockDataMap.cpp:81)    block yields: 605dab8dc7bfc8f90128357807b0f4da269edb32d14cb5395a96792b52a6301d
-ERROR - 1486565195: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
newbie
Activity: 7
Merit: 0
February 08, 2017, 09:17:59 AM
Hello
I have tr< to install the new version... but I get a lot of this errors...
and the DB want to be build...
I thont know whats hapen...

can everyone helping me
thx
rog

ValueError: No JSON object could be decoded
2017-02-08 13:49 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
  File "SDM.pyc", line 765, in __backgroundRequestTopBlock
  File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
  File "json\__init__.pyc", line 351, in loads
  File "json\decoder.pyc", line 366, in decode
  File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
newbie
Activity: 24
Merit: 3
February 04, 2017, 11:17:44 PM
Armory devs have typically refrained from commenting on non technical aspects of consensus debates. I do not intend to break that pattern.

Voting with code is more sensible in this space, and my dev branch currently hosts a fully fleshed SegWit feature set.
Thats good for me Smiley))
legendary
Activity: 3640
Merit: 1345
Armory Developer
February 03, 2017, 01:31:53 PM
Armory devs have typically refrained from commenting on non technical aspects of consensus debates. I do not intend to break that pattern.

Voting with code is more sensible in this space, and my dev branch currently hosts a fully fleshed SegWit feature set.
staff
Activity: 3374
Merit: 6530
Just writing some code
February 03, 2017, 11:54:11 AM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
He is in favor of segwit. The next version of Armory will have segwit support.
Doesn't have to mean the same. I also follow every rule of law even if i do not like them...
He has explicitly expressed support for Segwit on the IRC channel. Furthermore, Segwit is not a law, nor is it required for every wallet to use segwit. If he did not like segwit, then he does not have to implement it.
newbie
Activity: 24
Merit: 3
February 03, 2017, 11:11:36 AM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
He is in favor of segwit. The next version of Armory will have segwit support.
Doesn't have to mean the same. I also follow every rule of law even if i do not like them...
staff
Activity: 3374
Merit: 6530
Just writing some code
February 03, 2017, 10:58:39 AM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
He is in favor of segwit. The next version of Armory will have segwit support.
newbie
Activity: 24
Merit: 3
February 03, 2017, 10:38:25 AM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
staff
Activity: 3374
Merit: 6530
Just writing some code
January 31, 2017, 10:37:12 PM
Yes, 0.93.3 still works. It is recommended that you upgrade so that you can benefit from the reduced database size and better performance.

Sweet, thanks. On a similar note, if I update Armory to 0.95.1 to my online computer, but keep my offline computer at 0.93.3, will I be able to still use multi-sig across both versions (online at 0.95.1 multi-signing with offline 0.93.3 armory)?
Yes.
newbie
Activity: 6
Merit: 0
January 31, 2017, 09:58:30 PM
Yes, 0.93.3 still works. It is recommended that you upgrade so that you can benefit from the reduced database size and better performance.

Sweet, thanks. On a similar note, if I update Armory to 0.95.1 to my online computer, but keep my offline computer at 0.93.3, will I be able to still use multi-sig across both versions (online at 0.95.1 multi-signing with offline 0.93.3 armory)?
staff
Activity: 3374
Merit: 6530
Just writing some code
January 31, 2017, 09:47:27 AM
Apologies if this has been asked, I searched around but didn't find.

I updated Bitcoin core to v0.13.99.0-d2c9e4d, but am still on armory 0.93.3.
Getting ready to upgrade to 0.95.1, but after loading up Armory, I still see all my wallets/offline lockboxes/multi-signature wallets and balances are correct.

Can I still use Armory 0.93.3 to sign transactions (with core 0.13 running), and create multi-sig (requires offline signing) transactions? Any danger in at least trying this to see if it works? Thanks!
Yes, 0.93.3 still works. It is recommended that you upgrade so that you can benefit from the reduced database size and better performance.
newbie
Activity: 15
Merit: 0
January 31, 2017, 08:19:54 AM
Multiple possibilities. Could be bad block data, unstable CPU, running out of RAM, some unknown bug.

You should create your own thread and post armorylog.txt and dbLog.txt. This thread is too long to track this issue here.

The problem got solved.  While armory was stuck at some percentage everytime (from deleting the DB completely from armory folder), what i did was, killed the armory process and ArmoryDB as well. Restarted it and it started syncing properly with bitcoind.

So the above problem only happens when deleting the database folder in armory folder and starting it from scratch, it will reach a certain percentage and freeze at scanning transaction history.

The other problem is that i cannot let armory open bitcoind itself, otherwise i get RPC username and password errors.  Currently i am running them separately.

I really hope that the newer version runs bitcoind on its own by using cookie like you mentioned in your posts.

Thanks
newbie
Activity: 6
Merit: 0
January 31, 2017, 02:42:10 AM
Apologies if this has been asked, I searched around but didn't find.

I updated Bitcoin core to v0.13.99.0-d2c9e4d, but am still on armory 0.93.3.
Getting ready to upgrade to 0.95.1, but after loading up Armory, I still see all my wallets/offline lockboxes/multi-signature wallets and balances are correct.

Can I still use Armory 0.93.3 to sign transactions (with core 0.13 running), and create multi-sig (requires offline signing) transactions? Any danger in at least trying this to see if it works? Thanks!
Pages:
Jump to: