Armory 0.96.3 released - page 2. | Bitcointalksearch.org

Ente

legendary

Activity: 2126

Merit: 1001

Quote from: alomar on April 13, 2018, 08:09:09 PM

i also tried building from the 0.96.4 source but run into this error upon "make":

Code:

user@user-VirtualBox:~/Downloads/BitcoinArmory-0.96.4$ make
Making all in cppForSwig
make[1]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Making all in lmdb
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
Making all in fcgi
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
make[2]: *** No rule to make target 'all'.  Stop.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
Makefile:1538: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Makefile:413: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

before

Quote

sh autoconfigure.sh

do

Quote

git submodule init
git submodule update

edit: oops, didn't notice the new thread page.

Cheers,

Ente

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: alomar on April 13, 2018, 08:09:09 PM

i also tried building from the 0.96.4 source but run into this error upon "make":

Code:

git submodule init
git submodule update
sh autogen.sh
./configure
make clean
make -j8
sudo make install

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: Ente on April 13, 2018, 06:54:13 PM

Ah, neat!
I upgraded both ArmoryDB and ArmoryQt to 0.96.4, still the exact same messages and scanning never finishes..

Ente

I need to see the full Qt log.

Holliday

legendary

Activity: 1120

Merit: 1012

Quote from: Ente on April 13, 2018, 06:54:13 PM

Ah, neat!
I upgraded both ArmoryDB and ArmoryQt to 0.96.4, still the exact same messages and scanning never finishes..

Ente

Did you happen to delete the armory/databases folder after updating and try the new version from scratch?

alomar

member

Activity: 178

Merit: 10

i also tried building from the 0.96.4 source but run into this error upon "make":

Code:

user@user-VirtualBox:~/Downloads/BitcoinArmory-0.96.4$ make
Making all in cppForSwig
make[1]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Making all in lmdb
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/lmdb'
Making all in fcgi
make[2]: Entering directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
make[2]: *** No rule to make target 'all'. Stop.
make[2]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig/fcgi'
Makefile:1538: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Downloads/BitcoinArmory-0.96.4/cppForSwig'
Makefile:413: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Ente

legendary

Activity: 2126

Merit: 1001

Ah, neat!
I upgraded both ArmoryDB and ArmoryQt to 0.96.4, still the exact same messages and scanning never finishes..

Ente

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

I've tagged 0.96.4, there just aren't builds for it yet.

Ente

legendary

Activity: 2126

Merit: 1001

Quote from: goatpig on April 13, 2018, 01:58:21 AM

Quote from: Ente on April 12, 2018, 05:23:37 PM

I imported a new address in 0.96.3, scanning hangs close to finished:

Have you tried with 0.96.4?

Not yet, as it's an RC.
If you have no other suggestions, I'll upgrade and recheck.

Ente

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: Ente on April 12, 2018, 05:23:37 PM

I imported a new address in 0.96.3, scanning hangs close to finished:

Have you tried with 0.96.4?

Ente

legendary

Activity: 2126

Merit: 1001

I imported a new address in 0.96.3, scanning hangs close to finished:

ArmoryDB:

Quote

(BlockchainScanner.cpp:852) scanned from block #514744 to #515526

ArmoryQt:

Quote

-ERROR - �Q��o: (BinaryData.h:563) odd hexit count
-ERROR - �Q��o: (SwigClient.cpp:61) odd hexit count

I restarted both a few times, always the same. Around half an hour scanning, then it hangs in Qt, and wouldn't show a time estimate any more after restarting Qt.

Well, first time I have a computer problem where I literally find noone with the same problem before, yay! :-)

Ente

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on March 12, 2018, 04:45:40 PM

These are the one. The .lmdb wallets do not carry the same file ID cause the ID is built differently. You can nuke any .lmdb (and lock files) file with anything prior to 0.97 (this is to future proof this comment) as they are built on the fly WO copies of the python wallets.

ok, that killed it. thanks.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

These are the one. The .lmdb wallets do not carry the same file ID cause the ID is built differently. You can nuke any .lmdb (and lock files) file with anything prior to 0.97 (this is to future proof this comment) as they are built on the fly WO copies of the python wallets.

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on March 11, 2018, 09:26:08 PM

Quote from: alomar on March 11, 2018, 09:05:33 PM

Quote from: goatpig on March 11, 2018, 01:51:00 PM

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

no, why? what does that do?

It's a watching only copy of your wallet used to interface with the DB. This most likely still has the imported public key in it, which is why the DB returns those UTXO in coin control.

looking inside user@Ubuntu:~/.armory$ , i see these wallets:

armory_IekLiRmn_wallet.lmdb
armory_IekLiRmn_wallet.lmdb-lock

but those ID's numbers don't match the imported WO wallet ID number that has the imported private key.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: alomar on March 11, 2018, 09:05:33 PM

Quote from: goatpig on March 11, 2018, 01:51:00 PM

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

no, why? what does that do?

It's a watching only copy of your wallet used to interface with the DB. This most likely still has the imported public key in it, which is why the DB returns those UTXO in coin control.

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on March 11, 2018, 01:51:00 PM

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

no, why? what does that do?

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

What I am asking is whether you delete the .lmdb mirror wallet files in the Armory datadir at all.

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on March 10, 2018, 04:36:01 PM

Quote from: alomar on March 10, 2018, 12:12:10 PM

after signing, i always delete/remove the wallet in the GUI, nothing more.

On the online side?

same thing. deleted online wallet first before importing new restored WO wallet. Armory even labels it as a "Restored" wallet in the description. again, the bizarre thing is that when i open Wallet Properties, the imported key is NOT listed nor is the "Imported Key" key category even displayed, as i showed in that screenshot above. but i still see it in Coin Control with a balance. i can even construct a tx with it. but it won't sign on the offline wallet b/c the imported private key has been successfully deleted on that pc.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: alomar on March 10, 2018, 12:12:10 PM

after signing, i always delete/remove the wallet in the GUI, nothing more.

On the online side?

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on March 08, 2018, 04:34:44 AM

I need more detail. What was the state of your offline instance when you restored? Was this particular wallet there?

EDIT: did you cycle the .lmdb mirror wallet file?

no, Armory offline was devoid of any and all wallets prior to the restore.

after signing, i always delete/remove the wallet in the GUI, nothing more.

PhoenixFire

member

Activity: 270

Merit: 36

Quote from: alomar on March 07, 2018, 11:59:29 AM

Quote from: goatpig on March 07, 2018, 06:09:44 AM

https://imgur.com/a/v7Tlz

there must be a bug somewhere.

as you can see in the same section in my wallet, there is no Imported Addresses category nor the Remove Import Address command over on the right (which is expected if Armory isn't detecting an imported address, i guess):

https://i.imgur.com/C9mNWEs.png

yet, when i open Coin Control, i plainly see the imported address with it's balance.

using 0.96.3.992 in expert mode

~~As far as I know, the option doesn't appear for a watch only wallet. Is that the case here?~~
Scratch that, missed some info. Strange issue!

Topic: Armory 0.96.3 released - page 2. (Read 15626 times)