Bitcoin Forum

Bitcoin => Armory => Topic started by: goatpig on May 01, 2017, 09:35:25 PM



Title: Armory 0.96 is out
Post by: goatpig on May 01, 2017, 09:35:25 PM
Binaries:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96

changelog

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt

Notable changes:

1) SegWit
2) RBF & CPFP
3) Translations
4) Compressed public keys
5) Reworked coin control and address tree UI
6) Fleshed out fee and privacy features

Better description on the webpage: https://btcarmory.com/0.96.0-release/

Notes:

Only putting out Windows x64 and Linux x64 builds atm. Offline bundles, RPi and OSX builds for 0.96.1, once I get rid of the twisted/openssl dependency. Eta 1-2 weeks.

Thanks:

achow101 for the support and translation PR, droark for the OSX support and the testers for helping tiddy things up.

Enjoy =)





Title: Re: Armory 0.96 is out
Post by: OtisG on May 01, 2017, 10:59:35 PM
woohoo!  Will download it now.


Title: Re: Armory 0.96 is out
Post by: OtisG on May 01, 2017, 11:52:16 PM
woohoo!  Will download it now.

And it works with BTC Core 14.0!  This is the first time in over two months my Armory wallet has completely worked.

Thanks!!!


Title: Re: Armory 0.96 is out
Post by: pf on May 02, 2017, 03:40:24 AM
Excellent work. Thank you, goatpig.

  • It looks like you're slowly getting rid of Python and moving to C++ only. Is this true?
  • How do you recommend we upgrade to the new wallet format, including for our wallet file backups? (I prefer to backup wallet files and memorize password.) Should I just launch Armory 0.96 to update it automatically and export the wallet file from there?
  • Are you expecting more wallet file updates in future versions?


Title: Re: Armory 0.96 is out
Post by: achow101 on May 02, 2017, 04:02:09 AM
  • It looks like you're slowly getting rid of Python and moving to C++ only. Is this true?
I think the plan is to have all of the backend, crypto, and computationally intensive stuff in C++ and have all of the frontend GUI stuff as python.

  • How do you recommend we upgrade to the new wallet format, including for our wallet file backups? (I prefer to backup wallet files and memorize password.) Should I just launch Armory 0.96 to update it automatically and export the wallet file from there?
Nothing needs to be done to upgrade. The current python wallet format is still the primary format. The C++ watching only wallet will be created automatically and automatically mirror the current python wallets.


  • Are you expecting more wallet file updates in future versions?
Definitely. The goal is to eventually move to the C++ wallet format which is supposed to be built from scratch so that multisig, compressed keys, BIP 32, etc. can be properly supported instead of the current format which isn't really extensible.


Title: Re: Armory 0.96 is out
Post by: bitpop on May 02, 2017, 08:12:42 AM
Thanks! Works great again!


Title: Re: Armory 0.96 is out
Post by: Stroto on May 02, 2017, 10:13:49 AM
Looks good. No issues with 0.14.1 so far.

Goatpig, Achow101, Droark and others, you should really have a donation address so that we can at least buy you a few beers for your hard work, much appreciated.


Title: Re: Armory 0.96 is out
Post by: Carlton Banks on May 02, 2017, 12:05:37 PM
Goatpig, Achow101, Droark and others, you should really have a donation address so that we can at least buy you a few beers for your hard work, much appreciated.

goatpig suggested that he might do it after this release, and he definitely deserves it, now that Armory is in such good shape. goatpig?


Title: Re: Armory 0.96 is out
Post by: johnlu on May 02, 2017, 02:40:05 PM
I update from bitcoin-core-0.14.0 and armory 0.95.1 to 0.14.1 and 0.96.

I'm getting this:
Code:
$ armory 
/home/user
(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
"sni-qt/26446" WARN  16:33:30.549 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
(WARNING) SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/user/.bitcoin/blocks" --datadir="/home/user/.armory/" --dbdir="/home/user/.armory/databases"
-ERROR - 1493735610: (SwigClient.cpp:61) can't connect socket

And it remains stuck in "Preparing Databases".

Edit:
I had to close armory gui and to kill ArmoryDB and bitcoind, I did it few times and now it seems to be working. It's scanning transaction history now...
Will it take too long?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 02, 2017, 02:49:49 PM
Quote
It's scanning transaction history now...
Will it take too long?

Depends on your hardware


Title: Re: Armory 0.96 is out
Post by: Mr.Vice on May 02, 2017, 04:36:17 PM
I update from bitcoin-core-0.14.0 and armory 0.95.1 to 0.14.1 and 0.96.

I'm getting this:
Code:
$ armory 
/home/user
(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
"sni-qt/26446" WARN  16:33:30.549 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
(WARNING) SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/user/.bitcoin/blocks" --datadir="/home/user/.armory/" --dbdir="/home/user/.armory/databases"
-ERROR - 1493735610: (SwigClient.cpp:61) can't connect socket

And it remains stuck in "Preparing Databases".

Edit:
I had to close armory gui and to kill ArmoryDB and bitcoind, I did it few times and now it seems to be working. It's scanning transaction history now...
Will it take too long?

@johnlu:
I think there is some kind of issue with the GUI when starting armory 0.96 the first time after upgrading. To solve this you actually just have to close armory normally after armorydb has fully loaded and restart it again. Afterwards everything should just work fine. ;-)

Goatpig, Achow101, Droark and others, you should really have a donation address so that we can at least buy you a few beers for your hard work, much appreciated.

goatpig suggested that he might do it after this release, and he definitely deserves it, now that Armory is in such good shape. goatpig?

@goatpig:
I have to fully agree. For that top notch software you would definatly deserve donations. I'm pretty sure a lot of users are willing to donate! :-)


Title: Re: Armory 0.96 is out
Post by: johnlu on May 02, 2017, 05:42:32 PM
It's been showing this for the last 2h30m...
http://imgur.com/a/d8FJ4
http://imgur.com/a/d8FJ4

And also repeatedly printing this in the terminal:
(python2:28385): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed


Title: Re: Armory 0.96 is out
Post by: achow101 on May 02, 2017, 09:23:56 PM
It's been showing this for the last 2h30m...
http://imgur.com/a/d8FJ4
http://imgur.com/a/d8FJ4
Try running ArmoryDB in the terminal with the arguments that you use for running ArmoryQt in the terminal. Then run ArmoryQt and it should work.

And also repeatedly printing this in the terminal:
(python2:28385): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
I'm pretty sure that error is benign.


Title: Re: Armory 0.96 is out
Post by: RoadStress on May 04, 2017, 09:54:37 PM
Thank you for the voluntarily hard work!


Title: Re: Armory 0.96 is out
Post by: neosatus on May 05, 2017, 07:05:45 AM
Hi, just updated Core and installed this version.

Getting a crash as this occurs in ArmoryDB: -INFO  - 1493967598: (..\BDM_Server.cpp:1025) unregistered bdv: 02f4bc80f1788c274f50


Thanks for any advice!


Title: Re: Armory 0.96 is out
Post by: goatpig on May 05, 2017, 10:31:25 AM
Hi, just updated Core and installed this version.

Getting a crash as this occurs in ArmoryDB: -INFO  - 1493967598: (..\BDM_Server.cpp:1025) unregistered bdv: 02f4bc80f1788c274f50


Thanks for any advice!

Post dbLog.txt


Title: Re: Armory 0.96 is out
Post by: SimonBelmond on May 06, 2017, 09:45:11 PM
Ma Armory synchronizes fine. However if I choose "receive" and then the respective wallet I get a small loading window which just doesn't resolve into anything and just stays there:

https://i.imgur.com/5bDLBXB.jpg

When I double click on the wallet and press receive in the wallet view it just doesn't react to the button. Other UI elements work fine.

Win64 0.96

Needless to say that the watch only wallet is configures as my own with security offline.

I had this already on the testing release. Never wanted to receive at times so I don't know if with both which I have tried.


Title: Re: Armory 0.96 is out
Post by: goatpig on May 06, 2017, 11:08:54 PM
Post armorylog.txt


Title: Re: Armory 0.96 is out
Post by: bvoid on May 07, 2017, 12:40:25 PM
When I try to send BTC I get "coin selection failed with targetval > value" error with "Change Address Type" set to Auto. Force to P2PKH works however.
Armory 0.96 and Bitcoin core 0.14.0


Title: Re: Armory 0.96 is out
Post by: SimonBelmond on May 07, 2017, 06:37:02 PM
Post armorylog.txt

Will do as soon as I get it back up. I computed an additional 100 addresses for one wallet and now it is always stuck at 99% of rescan of TX history with ArmoryDB has stopped working error. so I deleted the whole DB and am currently building with:
Code:
thread-count=1
db-type=DB_BARE

Will report back.


Title: Re: Armory 0.96 is out
Post by: goatpig on May 07, 2017, 08:16:23 PM
When I try to send BTC I get "coin selection failed with targetval > value" error with "Change Address Type" set to Auto. Force to P2PKH works however.
Armory 0.96 and Bitcoin core 0.14.0

What value were you trying to spend in relation to your utxo value?


Title: Re: Armory 0.96 is out
Post by: SimonBelmond on May 07, 2017, 08:36:52 PM
Code:
2017-05-07 22:31 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-07 22:31 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-07 22:31 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\Ben\\AppData\\Roaming\\Bitcoin\\', '-dbcache=2000']
2017-05-07 22:31 (INFO) -- SDM.pyc:443 - PID of bitcoind: 4316
2017-05-07 22:31 (INFO) -- SDM.pyc:444 - PID of armory:   6476
2017-05-07 22:31 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '6476', '4316']
2017-05-07 22:31 (WARNING) -- ArmoryQt.py:1804 - DB is already running
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-07 22:31 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-07 22:31 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-07 22:32 (ERROR) -- qtdialogs.pyc:5840 - Error showing TxOut
Traceback (most recent call last):
  File "qtdialogs.pyc", line 5838, in showTxOutDialog
  File "qtdialogs.pyc", line 6069, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-07 22:33 (ERROR) -- qtdialogs.pyc:5840 - Error showing TxOut
Traceback (most recent call last):
  File "qtdialogs.pyc", line 5838, in showTxOutDialog
  File "qtdialogs.pyc", line 6069, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-07 22:33 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3490, in clickReceiveCoins
  File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'ArmoryMainWindow' object has no attribute 'Warning'


I think this was added when I tried the other method:

Code:
2017-05-07 22:36 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 1541, in getNewAddress
  File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'DlgWalletDetails' object has no attribute 'Warning'


Title: Re: Armory 0.96 is out
Post by: goatpig on May 07, 2017, 08:41:07 PM
Seems like some GUI edge case, will investigate.


Title: Re: Armory 0.96 is out
Post by: SimonBelmond on May 07, 2017, 10:02:10 PM
Just found another thing. Transaction info, right clicking on the sender and choosing "copy sender address" gives me this if the sender is me:

Code:
Wallet: "Smart Cold Storage (Watch) (Watc" (1XXXXXX...)

It seems to work on the recipient section


Title: Re: Armory 0.96 is out
Post by: goatpig on May 07, 2017, 10:08:30 PM
Just found another thing. Transaction info, right clicking on the sender and choosing "copy sender address" gives me this if the sender is me:

Code:
Wallet: "Smart Cold Storage (Watch) (Watc" (1XXXXXX...)

It seems to work on the recipient section

You mean it should just be the address, not the whole verbose?


Title: Re: Armory 0.96 is out
Post by: SimonBelmond on May 08, 2017, 07:06:53 AM
Just found another thing. Transaction info, right clicking on the sender and choosing "copy sender address" gives me this if the sender is me:

Code:
Wallet: "Smart Cold Storage (Watch) (Watc" (1XXXXXX...)

It seems to work on the recipient section

You mean it should just be the address, not the whole verbose?

Yes that is at least what I would expect from a copy address feature. As I mentioned it works fine for receiver addresses that I control, only sender addresses I own afdected.


Title: Re: Armory 0.96 is out
Post by: 2NIzko on May 08, 2017, 10:26:13 AM
Ubuntu 16.04 with armory_0.96-gcc5.4_amd64.deb, after doing upgrade from 95.1 to 96, i start armory and it doesnt even start up, the icon would flash a few times and the logs wont even write anything.

When i start armory from terminal, i get this: Illegal instruction (core dumped)

Was i supposed to completely remove 95.1 ?


Title: Re: Armory 0.96 is out
Post by: 2NIzko on May 08, 2017, 11:54:08 AM
So i sorted that out by removing armory_0.96-gcc5.4_amd64.deb and installing armory_0.96-gcc4.7_amd64.deb

Then when i start armory i get:

(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
-ERROR - 1494239616: (WalletManager.cpp:78) Failed to open wallet with error:
missing main wallet entry
Illegal instruction (core dumped)


I think this is because in version 95.1 i had an unconfirmed transaction because of a low fee given, a mistake i made.  I knew that clear all unconfirmed did not work in armory 95.1, so i upgraded now to run "clear all unconfirmed" but as soon as i open armory it throws that error about the entry.  Anything i can do to get this fixed @goatpig?
I also see the wallet being locked in the folder to "_wallet.lmdb-lock"

I tried removing the wallet or moving it in a temp dir, started up armory again and i see this error message now:

(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
Illegal instruction (core dumped)

After which i went back into .armory folder and deleted databases and settings to start from scratch.  Armory then opened with welcome message etc.

It started scanning and then during 68% it got stuck so i looked in .bitcoin/debug.log and saw this error:

-INFO  - 1494241552: (DatabaseBuilder.cpp:268) parsed block file #587
-INFO  - 1494241554: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 1494241554: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 1494241554: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

So i started up armory again and it is busy scanning now but stuck at preparing databases.. looked in .armory/dbLog.txt and it still scanning but its just not showing it in the GUI anymore.  So currently im waiting for this to finish

can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background.  please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction  ???


Title: Re: Armory 0.96 is out
Post by: goatpig on May 08, 2017, 12:46:54 PM
Quote
Anything i can do to get this fixed @goatpig?

Build the code yourself. This is some issue with the autotoolized version of cryptopp that relies on more SSE than older machines can handle. I'm trying to fix this for 0.96.1. For the mean time your best bet is to build 0.96 directly on your machine.

Quote
can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background.  please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction  Huh

Import in offline mode first then sync in online mode. If you want to wipe the ZC, delete the following files in your DB folder:

Code:
zeroconf
zeroconf-lock


Title: Re: Armory 0.96 is out
Post by: 2NIzko on May 08, 2017, 02:35:16 PM
Quote
Anything i can do to get this fixed @goatpig?

Build the code yourself. This is some issue with the autotoolized version of cryptopp that relies on more SSE than older machines can handle. I'm trying to fix this for 0.96.1. For the mean time your best bet is to build 0.96 directly on your machine.

Quote
can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background.  please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction  Huh

Import in offline mode first then sync in online mode. If you want to wipe the ZC, delete the following files in your DB folder:

Code:
zeroconf
zeroconf-lock

@goatpig
I tried doing what you said above, even in offline mode i tried to import but the gui crashes and theres nothing written in the logs about that issue.
I even deleted the zeroconf-lock files.

when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

I dont know why these files are auto created?

I uninstalled armory 96.0 and reinstalled the old version, seeing everything sync up again, the entry that was unconfirmed is no longer there anymore which is a good thing.
The bad thing is that it doesnt seem like wallet importing works in 96.0.

Im going to recreate a new empty wallet from the old armory and try import that into the new armory and il get back to you on that.


Title: Re: Armory 0.96 is out
Post by: goatpig on May 08, 2017, 03:09:06 PM
when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

These are watching only copies of the python wallet for the new code to run off of. You can delete these all you want, but 0.96 will recreate them on the fly if they are missing. Earlier versions don't use these files.


Title: Re: Armory 0.96 is out
Post by: 2NIzko on May 08, 2017, 03:23:21 PM
when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

These are watching only copies of the python wallet for the new code to run off of. You can delete these all you want, but 0.96 will recreate them on the fly if they are missing. Earlier versions don't use these files.

Ok, well i created a test wallet in 95.1 and upgraded to 96.0, i open armory with test wallet files inside folder already and it will create these watch only wallets but as soon as the GUI begins to start up, it crashes.

I especially tried this with offline armory, to import digital backup or even from paper backup and as soon as i import, it crashes, i open offline armory again and the wallet didnt import, yet its still in the folder.
I checked the armorylog.txt file and it says this before the crash:
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2172 -    Wallet (35Qpf31Yj):   "Test                            "   (Encrypted)
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes

crashes just after that.

Im not sure why this is happening even with brand new wallets.  The other thing is that i tried doing a test backup on both wallets and it crashes the gui on that too.


Title: Re: Armory 0.96 is out
Post by: 2NIzko on May 08, 2017, 03:54:07 PM
I also noticed something weird (which i dont know if this might be the cause): between the two gcc armory versions, the 4.7 one was the one that ive been trying to get to work with the wallet files (which means it opens up).
However when checking why armory_0.96-gcc5.4_amd64.deb wasnt opening at all. Everytime i tried opening it, i saw in syslog this error line:

traps: python2[29095] trap invalid opcode ip:7f5a01402ec0 sp:7ffeddbf0808 error:0 in _CppBlockUtils.so[7f5a00f4d000+6a9000]

And when i do gcc -v in terminal to see my version of gcc, it prints that i have the latest 5.4:
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)

 ???


Title: Re: Armory 0.96 is out
Post by: goatpig on May 08, 2017, 05:00:02 PM
What CPU are you using? The 5.4 version is built with a lot of x86 instructions that may not be available on your hardware.


Title: Re: Armory 0.96 is out
Post by: 2NIzko on May 08, 2017, 06:14:05 PM
What CPU are you using? The 5.4 version is built with a lot of x86 instructions that may not be available on your hardware.

Im using Intel Core i7 CPU 920.

Can you tell me what do you think the issue might be when the new version of armory is preventing wallets from being opened that were created with 95.1 like i described above?  Is it a bug?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 08, 2017, 06:35:35 PM
I would have to see a full log file, both armorylog and dbLog


Title: Re: Armory 0.96 is out
Post by: shaqattaq on May 09, 2017, 03:25:51 AM
Hi Goatpig et al, thanks for all your hard work with this release.

I believe I'm experiencing the same problem as neosatus.

ArmoryQT.exe crashes after ArmoryDB.exe reports "unregistered bdv: etc..."

I have updated both Armory and Core (14.1).

Here's the dbLog for the latest crash, ArmoryDB.exe appears to continue to run.

Code:
Log file opened at 1494297575: C:\Bitcoin DBs\Armory DB/dbLog.txt
-INFO  - 1494297575: (..\main.cpp:23) Running on 2 threads
-INFO  - 1494297575: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494297575: (..\BlockUtils.cpp:907) blkfile dir: C:\Bitcoin DBs\Bitcoin Core\blocks
-INFO  - 1494297575: (..\BlockUtils.cpp:908) lmdb dir: C:\Bitcoin DBs\Armory DB\databases
-INFO  - 1494297575: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494297576: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494297577: (..\BDM_Server.cpp:996) registered bdv: 7471bf47422af7fc355a
-INFO  - 1494297593: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1494297596: (..\DatabaseBuilder.cpp:208) Found 465842 headers in db
-INFO  - 1494297601: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508411bytes
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494297602: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.968s
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465454 to #465453
-INFO  - 1494297602: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1494297602: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.019s
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:160) init db in 26.789s
-INFO  - 1494297602: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO  - 1494297604: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN  - 1494297636: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1494297685: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN  - 1494297687: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN  - 1494297715: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN  - 1494297715: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-ERROR - 1494298924: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 1494298924: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO  - 1494298926: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO  - 1494299046: (..\BDM_Server.cpp:1025) unregistered bdv: 7471bf47422af7fc355a
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 75 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 80 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 85 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 90 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 95 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 100 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 105 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 110 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 115 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 120 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 125 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 130 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 135 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 140 zc parser threads

armorylog has this entry at the time of the crash:

(WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing

Thanks for any assistance.

Cheers.


Title: Re: Armory 0.96 is out
Post by: achow101 on May 09, 2017, 03:27:51 AM
Can you also post the armorylog.txt?


Title: Re: Armory 0.96 is out
Post by: shaqattaq on May 09, 2017, 03:42:53 AM
Sure thing, thanks for the reply:

Code:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1262 -    Armory Version        : 0.96
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1263 -    Armory Build:         : a3d01aa722
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1264 -    PyBtcWallet  Version  : 1.35
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1266 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1267 -    User home-directory   : C:\Users\xxx\AppData\Roaming
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1268 -    Satoshi BTC directory : C:\Users\xxx\AppData\Roaming\Bitcoin\
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1269 -    Armory home dir       : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs    :
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1271 -    Total Available RAM   : 4.00 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1272 -    CPU ID string         : Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1273 -    Number of CPU cores   : 2 cores
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1274 -    System is 64-bit      : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1275 -    Preferred Encoding    : cp1252
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1276 -    Machine Arch          : amd64
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1277 -    Available HDD (ARM)   : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1278 -    Available HDD (BTC)   : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     thread_count    : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rescan          : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     ignoreAllZC     : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rescanBalance   : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     disableModules  : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     port            : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     interport       : 8223
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     coverageOutputDir: None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     forceWalletCheck: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     regtest         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rebuild         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     nettimeout      : 2
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     datadir         : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     clearMempool    : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     offline         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     armoryDBDir     : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_port   : 9001
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiPort     : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     useTorSettings  : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     netlog          : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     keypool         : 100
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     coverageInclude : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     forceOnline     : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     redownload      : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rpcBindAddr     : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_ip     : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     multisigFile    : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     ram_usage       : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     mtdebug         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     logDisable      : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     settingsPath    : C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     language        : en
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     db_type         : DB_FULL
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     doDebug         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     enableDetSign   : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     disableConfPermis: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     testnet         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rpcport         : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiHome     : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiRpcport  : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     logFile         : C:\Bitcoin DBs\Armory DB\ArmoryQt.exe.log.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     verbosity       : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-05-09 13:19 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-09 13:19 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background. 
2017-05-09 13:19 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-09 13:19 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-09 13:19 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2172 -    Wallet (xxx):    "Primary Wallet                  "   (Encrypted)
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user.  Done!
2017-05-09 13:19 (INFO) -- ArmoryQt.py:558 - Usermode: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1682 -    From: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1690 -      To: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files (x86)\Armory
2017-05-09 13:19 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-09 13:19 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Bitcoin DBs\\Bitcoin Core']
2017-05-09 13:19 (INFO) -- SDM.pyc:443 - PID of bitcoind: 3152
2017-05-09 13:19 (INFO) -- SDM.pyc:444 - PID of armory:   4488
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '4488', '3152']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Bitcoin DBs\Bitcoin Core\blocks" --datadir="C:\Bitcoin DBs\Armory DB" --dbdir="C:\Bitcoin DBs\Armory DB\databases"
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Bitcoin DBs\\Bitcoin Core\\blocks"', u'--datadir="C:\\Bitcoin DBs\\Armory DB"', u'--dbdir="C:\\Bitcoin DBs\\Armory DB\\databases"']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode

Cheers.


Title: Re: Armory 0.96 is out
Post by: cryptoknut on May 09, 2017, 11:49:04 AM
Can you use pruning in the new version of armory? 


Title: Re: Armory 0.96 is out
Post by: achow101 on May 09, 2017, 01:44:21 PM
Hi Goatpig et al, thanks for all your hard work with this release.

I believe I'm experiencing the same problem as neosatus.

ArmoryQT.exe crashes after ArmoryDB.exe reports "unregistered bdv: etc..."
Hmm. I'm not sure what is wrong here. Try running Bitcoin Core manually then start Armory.

Can you use pruning in the new version of armory? 
No.


Title: Re: Armory 0.96 is out
Post by: alomar on May 09, 2017, 06:34:03 PM
i keep getting stuck at Scanning Transaction History @1sec.

Debian VM with Core bitcoind 0.14.1


Title: Re: Armory 0.96 is out
Post by: goatpig on May 09, 2017, 07:08:46 PM
logs


Title: Re: Armory 0.96 is out
Post by: alomar on May 09, 2017, 08:21:41 PM
logs




Log file opened at 1494352327: /home/debian/.armory/armorycpplog.txt
-INFO  - 1494353307: (SocketObject.cpp:520) POLLIN recv return 0


Log file opened at 1494353394: /home/debian/.armory/armorycpplog.txt
-ERROR - 1494354120: (SocketObject.cpp:416) poll() error in readAndWrite: 4


Title: Re: Armory 0.96 is out
Post by: goatpig on May 09, 2017, 09:05:10 PM
dbLog.txt too


Title: Re: Armory 0.96 is out
Post by: JeffZwolle on May 09, 2017, 10:26:34 PM
I just upgraded Bitcoin Core and Armory. Here are the notes I made of my first experiences after the upgrade.

Windows 7 64bit
Updated Bitcoin Core from 0.14.0 to 0.14.1
Updated Armory from 0.95.1 to 0.96

Armory crashed every time after scanning.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.

Errormesage from tray-icon after starting Armory about the connection being lost to BitcoinCore while that is not really so.
I am running BitcoinCore continuously in the background, regardless of Armory running or not.

The CMD-window is still always visible.

Problem: Saving/Backing up a wallet unencrypted to a file does not work. "Save to File"
I want to use it to backup the private keys to another encrypted medium. CTRL-C and -V would work, but that is annoying after a while.

Compressed keys:
MultiBit Classis private keys are not accepted at Private Key Import: No valid private key data was entered.
https://bitcointalk.org/index.php?topic=175389.msg14100768#msg14100768 (https://bitcointalk.org/index.php?topic=175389.msg14100768#msg14100768)

Wallet properties: Used addresses:
Addresses not visible. Unsure after which this happens.
Solved after restarting Armory.

Address Book: changed Comment, but it does not stick.
Or on the other hand: The comment for an address changed in the wallet does not display in the addressbook.

After doing one transaction, and restarting Armory:
Does not fully start.
Solved by restarting BitcoinCore before starting Armory.
dblog.txt:
Code:
Log file opened at 1494367860: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1494367860: (..\main.cpp:23) Running on 4 threads
-INFO  - 1494367860: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494367860: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO  - 1494367860: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO  - 1494367860: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494367860: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1494367862: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494367863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1494367865: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN  - 1494367865: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN  - 1494367865: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-INFO  - 1494367866: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO  - 1494367868: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494367868: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494367869: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.491s
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO  - 1494367869: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1494367869: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:160) init db in 6.281s
-INFO  - 1494367869: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads

successful start and shutdown after previous mentioned problem:
Code:
Log file opened at 1494368069: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1494368069: (..\main.cpp:23) Running on 4 threads
-INFO  - 1494368069: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494368069: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO  - 1494368069: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO  - 1494368069: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494368070: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1494368071: (..\BDM_Server.cpp:996) registered bdv: eb311f97a355b2f2dd5a
-INFO  - 1494368072: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494368073: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1494368076: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494368079: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.726s
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO  - 1494368079: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1494368079: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:160) init db in 7.121s
-INFO  - 1494368079: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1494368109: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1494368109: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO  - 1494368200: (..\BDM_Server.cpp:1025) unregistered bdv: eb311f97a355b2f2dd5a
-INFO  - 1494368200: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1494368200: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO  - 1494368200: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1494368202: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate


Title: Re: Armory 0.96 is out
Post by: goatpig on May 09, 2017, 11:11:47 PM
Armory crashed every time after scanning.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.

mmaped RAM, not allocated.

Quote
Errormesage from tray-icon after starting Armory about the connection being lost to BitcoinCore while that is not really so.
I am running BitcoinCore continuously in the background, regardless of Armory running or not.

False positive, will fix it for .1

Quote
The CMD-window is still always visible.

same

Quote
Problem: Saving/Backing up a wallet unencrypted to a file does not work. "Save to File"
I want to use it to backup the private keys to another encrypted medium. CTRL-C and -V would work, but that is annoying after a while.

Need to see armorylog.txt

Quote
Compressed keys:
MultiBit Classis private keys are not accepted at Private Key Import: No valid private key data was entered.
https://bitcointalk.org/index.php?topic=175389.msg14100768#msg14100768 (https://bitcointalk.org/index.php?topic=175389.msg14100768#msg14100768)

Compressed public keys, never said anything about compressed private keys

Quote
Wallet properties: Used addresses:
Addresses not visible. Unsure after which this happens.
Solved after restarting Armory.

What do you do to get to that?

Quote
Address Book: changed Comment, but it does not stick.
Or on the other hand: The comment for an address changed in the wallet does not display in the addressbook.

Comments are broken in address book for the moment.

Quote
After doing one transaction, and restarting Armory:
Does not fully start.
Solved by restarting BitcoinCore before starting Armory.
dblog.txt:
Code:
Log file opened at 1494367860: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1494367860: (..\main.cpp:23) Running on 4 threads
-INFO  - 1494367860: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494367860: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO  - 1494367860: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO  - 1494367860: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494367860: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1494367862: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494367863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1494367865: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN  - 1494367865: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN  - 1494367865: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-INFO  - 1494367866: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO  - 1494367868: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494367868: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494367869: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.491s
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO  - 1494367869: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1494367869: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO  - 1494367869: (..\DatabaseBuilder.cpp:160) init db in 6.281s
-INFO  - 1494367869: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1494367875: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads

successful start and shutdown after previous mentioned problem:
Code:
Log file opened at 1494368069: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1494368069: (..\main.cpp:23) Running on 4 threads
-INFO  - 1494368069: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494368069: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO  - 1494368069: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO  - 1494368069: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494368070: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1494368071: (..\BDM_Server.cpp:996) registered bdv: eb311f97a355b2f2dd5a
-INFO  - 1494368072: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494368073: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1494368076: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494368079: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.726s
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO  - 1494368079: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1494368079: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO  - 1494368079: (..\DatabaseBuilder.cpp:160) init db in 7.121s
-INFO  - 1494368079: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494368102: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1494368109: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1494368109: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN  - 1494368110: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO  - 1494368200: (..\BDM_Server.cpp:1025) unregistered bdv: eb311f97a355b2f2dd5a
-INFO  - 1494368200: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1494368200: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO  - 1494368200: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1494368202: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate


Will look into it.


Title: Re: Armory 0.96 is out
Post by: bitpop on May 10, 2017, 01:14:06 AM
Mine's working great. I sent a transaction and the comment says chained zc. Does that mean anything?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 10, 2017, 02:01:48 AM
Mine's working great. I sent a transaction and the comment says chained zc. Does that mean anything?

Means your tx is spending an unconfirmed txout.


Title: Re: Armory 0.96 is out
Post by: goodhopes on May 10, 2017, 03:37:33 PM
I upgraded from Armory 0.95.1 with Bitcoin Core 0.13.2 to Armory 0.96.0 for Ubuntu/Debian 64-bit with GCC 5.3. because I had two unconfirmed transactions (2 weeks old), which I wanted to clear.
Now, the new version of Armory doesn't finish Scanning Transaction History (1 second left)....I started Bitcoin Core with "bitcoin-qt --disablewallet" manually (this was the only possibility to get it working with Armory 95.1, therefore I just continued to do the same with the new version)
In
armorylog.txt:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1682 -    From: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1690 -      To: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 12:32 (WARNING) -- SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/andi/.bitcoin/
blocks" --datadir="/home/andi/.armory/" --dbdir="/home/andi/.armory/databases"
2017-05-10 12:32 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/andi/.
bitcoin/blocks"', '--datadir="/home/andi/.armory/"', '--dbdir="/home/andi/.armory/databases"']
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1188 - 3 attempts to load blockchain failed.  Remove mempool.bin.
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1193 - File mempool.bin does not exist. Nothing deleted.
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
...1000x
2017-05-10 12:56 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
-----------------------------------------------

Help would be very much appreciated! Should I upgrade to Bitcoin Core 0.14.1 to solve my problem?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 10, 2017, 04:07:11 PM
Show me dbLog.txt


Title: Re: Armory 0.96 is out
Post by: JeffZwolle on May 10, 2017, 06:24:34 PM
Armory crashed every time after scanning.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.

mmaped RAM, not allocated.

Every time another application is started, Windows needs to swap the memory to/from the pagefile.
It slows down my system. Even with an SSD.  ;D

Quote
Quote
Problem: Saving/Backing up a wallet unencrypted to a file does not work. "Save to File"
I want to use it to backup the private keys to another encrypted medium. CTRL-C and -V would work, but that is annoying after a while.

Need to see armorylog.txt

armorylog.txt
Just the parts that are of interest, I think.
Code:
2017-05-09 23:15 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 1117, in clickedDoIt
  File "ArmoryQt.py", line 1614, in makeWalletCopy
  File "armoryengine\Decorators.pyc", line 48, in inner
  File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found

2017-05-09 23:16 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 1117, in clickedDoIt
  File "ArmoryQt.py", line 1614, in makeWalletCopy
  File "armoryengine\Decorators.pyc", line 48, in inner
  File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found

2017-05-09 23:16 (INFO) -- ArmoryQt.py:4876 - New Block! : 465659
2017-05-09 23:16 (INFO) -- ArmoryQt.py:4884 - Current block number: 465659
2017-05-09 23:18 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 1119, in clickedDoIt
  File "ArmoryQt.py", line 1614, in makeWalletCopy
  File "armoryengine\Decorators.pyc", line 48, in inner
  File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found

2017-05-09 23:18 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 1119, in clickedDoIt
  File "ArmoryQt.py", line 1614, in makeWalletCopy
  File "armoryengine\Decorators.pyc", line 48, in inner
  File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found

2017-05-09 23:18 (ERROR) -- ArmoryUtils.pyc:3223 - Error in pybkgdthread: Incorrect passphrase for wallet
Traceback (most recent call last):
  File "armoryengine\ArmoryUtils.pyc", line 3221, in run
  File "armoryengine\ArmoryUtils.pyc", line 3158, in funcPartial
  File "qtdialogs.pyc", line 12949, in exec_async
PassphraseError: Incorrect passphrase for wallet
2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10

2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10

2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10

2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10

2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10

2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10

2017-05-09 23:22 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5092, in reject
  File "qtdialogs.pyc", line 5081, in cleanup
AttributeError: 'NoneType' object has no attribute 'binPrivKey32_Plain'

2017-05-09 23:22 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 5092, in reject
  File "qtdialogs.pyc", line 5081, in cleanup
AttributeError: 'NoneType' object has no attribute 'binPrivKey32_Plain'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

Quote
Quote
Compressed keys:
MultiBit Classis private keys are not accepted at Private Key Import: No valid private key data was entered.
https://bitcointalk.org/index.php?topic=175389.msg14100768#msg14100768 (https://bitcointalk.org/index.php?topic=175389.msg14100768#msg14100768)

Compressed public keys, never said anything about compressed private keys

Any chance that import of private keys will be supported too in the future?


Today this happened:
ArmoryQT,exe has stoppen working
dblog.txt:
Code:
Log file opened at 1494434109: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1494434109: (..\main.cpp:23) Running on 4 threads
-INFO  - 1494434109: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494434109: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO  - 1494434109: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO  - 1494434109: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494434111: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1494434111: (..\BDM_Server.cpp:996) registered bdv: eb0a1e06064ffaddef7b
-INFO  - 1494434113: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494434113: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1494434114: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN  - 1494434114: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN  - 1494434114: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1494434114: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1494434114: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494434114: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1494434114: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-INFO  - 1494434120: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO  - 1494434123: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494434123: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO  - 1494434124: (..\DatabaseBuilder.cpp:268) parsed block file #862
-INFO  - 1494434125: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494434125: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1494434125: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 2.139s
-INFO  - 1494434125: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465771
-INFO  - 1494434125: (..\BlockchainScanner.cpp:650) scanned from height #465668 to #465771
-INFO  - 1494434125: (..\BlockchainScanner.cpp:225) scanned transaction history in 0.382s
-INFO  - 1494434125: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.419s
-INFO  - 1494434125: (..\DatabaseBuilder.cpp:160) init db in 12.574s
-INFO  - 1494434125: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO  - 1494434245: (..\BDM_Server.cpp:1025) unregistered bdv: eb0a1e06064ffaddef7b

after restart:
Hung on: Preparing Databases
Unsure if it was the same error as previous start
Code:
Log file opened at 1494434426: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1494434426: (..\main.cpp:23) Running on 4 threads
-INFO  - 1494434426: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494434426: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO  - 1494434426: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO  - 1494434426: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494434427: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1494434428: (..\BDM_Server.cpp:996) registered bdv: 756b7c3b483e1b28a8b8
-WARN  - 1494434429: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN  - 1494434429: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN  - 1494434429: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1494434429: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1494434429: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494434429: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-INFO  - 1494434429: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494434430: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1494434433: (..\DatabaseBuilder.cpp:208) Found 465773 headers in db
-INFO  - 1494434436: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494434436: (..\DatabaseBuilder.cpp:477) Found next block after skipping 170595bytes
-INFO  - 1494434437: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494434437: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1494434437: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.682s
-INFO  - 1494434437: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465772 to #465771
-INFO  - 1494434437: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1494434437: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1494434437: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.014s
-INFO  - 1494434437: (..\DatabaseBuilder.cpp:160) init db in 7.691s
-INFO  - 1494434437: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN  - 1494434438: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO  - 1494434557: (..\BDM_Server.cpp:1025) unregistered bdv: 756b7c3b483e1b28a8b8

armorylog.txt
Just the part of the last start.
Some parts are censored by replacing them with ###CENSORED###
Code:
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1262 -    Armory Version        : 0.96
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1263 -    Armory Build:         : a3d01aa722
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1264 -    PyBtcWallet  Version  : 1.35
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1266 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1267 -    User home-directory   : C:\Users\jeff\AppData\Roaming
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1268 -    Satoshi BTC directory : C:\Users\jeff\AppData\Roaming\Bitcoin\
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1269 -    Armory home dir       : C:\Users\jeff\AppData\Roaming\Armory\
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs    :
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1271 -    Total Available RAM   : 15.91 GB
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1272 -    CPU ID string         : Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1273 -    Number of CPU cores   : 4 cores
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1274 -    System is 64-bit      : True
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1275 -    Preferred Encoding    : cp1252
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1276 -    Machine Arch          : amd64
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1277 -    Available HDD (ARM)   : 425 GB
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1278 -    Available HDD (BTC)   : 425 GB
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     thread_count    : -1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     rescan          : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     ignoreAllZC     : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     rescanBalance   : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     disableModules  : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     port            : None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     interport       : 8223
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     coverageOutputDir: None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     forceWalletCheck: False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     regtest         : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     rebuild         : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     nettimeout      : 2
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     datadir         : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     clearMempool    : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     offline         : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     armoryDBDir     : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_port   : 9001
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiPort     : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     useTorSettings  : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     netlog          : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     keypool         : 100
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     coverageInclude : None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     forceOnline     : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     redownload      : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     rpcBindAddr     : 127.0.0.1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_ip     : 127.0.0.1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     multisigFile    : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     ram_usage       : -1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     mtdebug         : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     logDisable      : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     settingsPath    : C:\Users\jeff\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     language        : en
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     db_type         : DB_FULL
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     doDebug         : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     enableDetSign   : True
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     disableConfPermis: False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     testnet         : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     rpcport         : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiHome     : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiRpcport  : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     logFile         : C:\Users\jeff\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 -     verbosity       : None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\jeff\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 18:40 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-05-10 18:40 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-10 18:40 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background. 
2017-05-10 18:40 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-10 18:40 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-10 18:40 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\jeff\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2129 - ***WARNING: Duplicate wallet detected, ###CENSORED###
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2140 - Second wallet is more useful than the first one...
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2141 -      Wallet 1 (skipped): C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###__WatchOnly.wallet
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2142 -      Wallet 2 (loaded):  C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###_.wallet
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2129 - ***WARNING: Duplicate wallet detected, ###CENSORED###
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2140 - Second wallet is more useful than the first one...
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2141 -      Wallet 1 (skipped): C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###__WatchOnly.wallet
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2142 -      Wallet 2 (loaded):  C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###_.wallet
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 8
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (No Encryption)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (No Encryption)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 -    Wallet ###CENSORED###"   (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1503 - URL-register action: AskUser
2017-05-10 18:40 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1682 -    From: Expert
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1690 -      To: Expert
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 18:40 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\jeff\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\jeff\AppData\Roaming\Armory\" --dbdir="C:\Users\jeff\AppData\Roaming\Armory\databases"
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\jeff\\AppData\\Roaming\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\jeff\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\jeff\\AppData\\Roaming\\Armory\\databases"']
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode

After restart: same problem
Restarting BitcoinCore before this restart did not solve it.


I re-installed 0.95.1 because rebuilding the Armory database every day is annoying.
* I had created a backup of my 0.95.1 wallets before I upgraded to 0.96
* Removing all wallet-files of 0.96
* Restoring all wallet-files of 0.95.1
* emptying %appdata%\Armory\databases
* Installing 0.95.1 over 0.96
0.95.1 is running fine now.
 ::)


Title: Re: Armory 0.96 is out
Post by: goatpig on May 10, 2017, 07:48:10 PM
Every time another application is started, Windows needs to swap the memory to/from the pagefile.
It slows down my system. Even with an SSD.  ;D

mmaped memory does not behave like swap. It's a hint for the OS to not clear cached on disk data that has already been read once, it does not push that data into a pagefile afterwards to free up memory (it's already on disk to begin with). The memory is just given up.

mmap is actually an elegant way to scale with extra RAM without hogging it from other processes.

Quote
armorylog.txt
Just the parts that are of interest, I think.

Translation patch snafu, will get it under control.

Quote
Any chance that import of private keys will be supported too in the future?

That's for the new wallets. This version still uses Python wallets. The new code does not handle private keys yet, it only creates WO copies of the python wallets to deal with the new scripts types.

Quote
Today this happened:
ArmoryQT,exe has stoppen working

Think I've got the fix for this already in testing. Would help if you try the testing builds for 0.96.1 once I push that out (this week end most likely)


Title: Re: Armory 0.96 is out
Post by: goatpig on May 10, 2017, 11:00:11 PM
Quote
Every time I start Armory it gets stuck on preparing data base without any progress.

How long does it go like this? Can you let it run for like 20min stuck and post dbLog.txt again?


Title: Re: Armory 0.96 is out
Post by: goodhopes on May 11, 2017, 05:19:43 AM
Show me dbLog.txt

Thank you very much for the quick reply and your great work!!! Before I got your reply, I tried something else and used the Option rebuild database and scan new. It finally finished overnight and shows my wallets, great!!! I tried to send some BTC with automatic fee (0.00285), but there are not yet confirmed, neither visible in blockchain.info....


Title: Re: Armory 0.96 is out
Post by: johnlu on May 11, 2017, 10:53:16 AM
I'm doing this and it works fine for my workstation.

Code:
$ ArmoryDB &; sleep 5m; armory

Sometimes armory takes some minutes until it connects to bitcoind. It works fine for me this way ;-)


EDIT1: Wow!! it's not working!!! It's no longer syncing!! It stopped at block #465294.
EDIT2: Doing a rebuild and rescan databases. Tell you later.


Title: Re: Armory 0.96 is out
Post by: Ente on May 11, 2017, 09:49:50 PM
Hi everyone,

as my v0.96 with remote ArmoryDB finally works, I imported old wallet files.
When using a wallet where I imported a compressed-key address, I get a segfault in ArmoryQT.
Earier versions worked, showed the address and balance, just couldn't spend the funds.

I have no entries in the logs whatsoever (neither in armoryDB nor armorylog.txt), just bam, segfault and gone.

Anything else I can provide? Want the wallet file to test?

Cheers,

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on May 11, 2017, 11:14:20 PM
Quote
When using a wallet where I imported a compressed-key address, I get a segfault in ArmoryQT.

The mirror wallets do not support importing compressed pubkeys atm, for I don't remember a feature ever allowing to import pub keys, let alone compressed ones.

Are you sure the issue isn't just with imports in general?


Title: Re: Armory 0.96 is out
Post by: Ente on May 12, 2017, 09:15:09 AM
Quote
When using a wallet where I imported a compressed-key address, I get a segfault in ArmoryQT.

The mirror wallets do not support importing compressed pubkeys atm, for I don't remember a feature ever allowing to import pub keys, let alone compressed ones.

Are you sure the issue isn't just with imports in general?

I didn't "import" with that feature, but copied some old wallets into my armory folder.
The compressed address I imported years ago into that wallet was created with vanitygen, afaik. I imported the private key back then into said wallet, not just a pubkey or watch-only address or the like.
I can't tell you much more any more, sorry, as it's been so long ago.

In older Armory versions, I couldn't import compressed keys from other wallets, for example from bitcoinj. What changed with regards to compressed addresses/keys in the new (c?) wallet format? I think I am mixing up different types of compression now..

Ente


Title: Re: Armory 0.96 is out
Post by: johnlu on May 12, 2017, 01:00:53 PM
I'm doing this and it works fine for my workstation.

Code:
$ ArmoryDB &; sleep 5m; armory

Sometimes armory takes some minutes until it connects to bitcoind. It works fine for me this way ;-)


EDIT1: Wow!! it's not working!!! It's no longer syncing!! It stopped at block #465294.
EDIT2: Doing a rebuild and rescan databases. Tell you later.

I did a rebuild and rescan databases and everything is okay now.


Title: Re: Armory 0.96 is out
Post by: johnlu on May 12, 2017, 01:02:52 PM
I got a question... I know that I can close bitcoind with bitcoin-cli stop command. Is there any command or any way to safely stop ArmoryDB?
Now I use pkill -9 ArmoryDB.


Title: Re: Armory 0.96 is out
Post by: achow101 on May 12, 2017, 03:31:32 PM
I got a question... I know that I can close bitcoind with bitcoin-cli stop command. Is there any command or any way to safely stop ArmoryDB?
Now I use pkill -9 ArmoryDB.
I have just been using Ctrl+C (when ArmoryDB is in the terminal) or sudo kill -9 to kill it and I have not experienced any issues. I think that is the only way to actually stop ArmoryDB when you run it yourself.


Title: Re: Armory 0.96 is out
Post by: goatpig on May 12, 2017, 06:13:36 PM
I didn't "import" with that feature, but copied some old wallets into my armory folder.

So it comes down to wallets with imports crashing Armory on startup?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 12, 2017, 06:14:26 PM
I got a question... I know that I can close bitcoind with bitcoin-cli stop command. Is there any command or any way to safely stop ArmoryDB?
Now I use pkill -9 ArmoryDB.

Not really. The client has the code for it but it's not really humanly reproducible. The DB is fine with ungraceful shutdowns, won't phase it.


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 12, 2017, 07:34:26 PM
Windows 7 64bit
Bitcoin Core 0.14.0
Armory 0.96

I upgraded to 0.96 from 0.94.1 and after several crashes (usually at the scanning transaction history stage), restarts and reboots I finally got Armory to startup normally and show transactions and balances.

Everything seemed to be fine after several days, until I did a normal transaction yesterday. I sent some bitcoin from an offline wallet using the method of a usb key to move the tx file back and forth. The transaction went through okay. It got confirmed quickly as evidenced but the receiving wallet and blockchain.info. But Armory didn't show the transaction as having any confirmations(when it really had several), and thus making a lot of the BTC in that wallet unspendable, when it should be spendable.

I decided to do a 'Rescan Balance' to see if that would update the list of txs to show the proper number of confirmations instead of 0. When next I tried to start Armory it stopped working... I tried more times and either ArmoryQt would stop-working/crash or ArmoryDB would, usually at the scanning transaction history stage, or at scanning or resolving tx hashes. After each crash the dblog.txt is always empty and the end of armorylog.txt had several lines of: (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode

Next I tried to do a 'Rebuild and Rescan Databases' which didn't help after several attempts(including reboots of the computer)... still the crashes.

I next tried 'Clear All Unconfirmed' in case it was that last tx (which didn't show as confirmed in Armory but really was confirmed) was the problem.
That didn't work right away but after a reboot it seemed to startup normally again. But that transaction was not included in the list of transactions and the balance of the wallet was back to where it was before that transaction; i.e. incorrect.  

Of course I am reluctant to do any more transactions from that wallet when Armory can't even display the balance correctly.

Again I tried to do a  'Rescan Balance'...  but back to the crashing of ArmoryDB. Even when I try 'Clear All Unconfirmed' and reboot the computer again.
It gets as far as showing in the ArmoryQt client, 'Resolving Tx Hashes'... showing a small percentage but also a small number of seconds to go: e.g. 3% 5 seconds.

Still dblog is empty and armorylog ends with the line: (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode.

The ArmoryDB console, after a Windows pop-up error message "ArmoryDB.exe has stopped working", and before I choose to 'Close the program' shows several lines of incremented error messages...
The last few lines in the ArmoryDB console are:
-ERROR- 1494614491: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR- 1494614491: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR- 1494614491: (..\BlockchainScanner.cpp:1407) Skipping this block
-ERROR- 1494614492: (..\BlockchainScanner.cpp:1405) Block deser error while processing tx filters:
-ERROR- 1494614492: (..\BlockchainScanner.cpp:1406)   raw data does not match expected block hash
-ERROR- 1494614492: (..\BlockchainScanner.cpp:1407) Skipping this block

I am wondering if I should try the 'Factory Reset' option next or wait for the next update where this bug is fixed...



Title: Re: Armory 0.96 is out
Post by: goatpig on May 12, 2017, 08:32:51 PM
I am wondering if I should try the 'Factory Reset' option next or wait for the next update where this bug is fixed...

Build with DB_BARE.

Quote
Would a PPA be possible?

Don't know what that means.


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 12, 2017, 08:58:23 PM
I am wondering if I should try the 'Factory Reset' option next or wait for the next update where this bug is fixed...

Build with DB_BARE.


I don't compile myself but download the binaries.


Title: Re: Armory 0.96 is out
Post by: goatpig on May 12, 2017, 09:05:06 PM
As in build the DB with --db-type=DB_BARE


Title: Re: Armory 0.96 is out
Post by: Ente on May 12, 2017, 09:13:05 PM
I didn't "import" with that feature, but copied some old wallets into my armory folder.

So it comes down to wallets with imports crashing Armory on startup?

I have two old wallet files, both have an imported privatekey.
The first wallet file has a "regular" address imported, and works fine (that specific imported address is empty though).
The second wallet file has that compressed type privkey (I think) imported. Armory segfaults immediately on startup with that wallet in its folder.

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on May 12, 2017, 09:29:14 PM
You mean you managed to import an compressed priv key into an Armory wallet? That's damn weird. Can you try to reproduce this on testnet?


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 13, 2017, 12:12:15 AM
As in build the DB with --db-type=DB_BARE

Even before seeing this I tried something else. I shutdown as many background programs etc. as I could to give me as much RAM as possible.
I am back to where the program starts and shows the balances. I didn't have memory problems before. Does 0.96 need greater than 8 GB of RAM?
I have 9GB in total on this machine before anything loads. What would be a good amount?

But again...
That transaction still doesn't show up after all these rescans; the wallet still has the old wrong balance. 
What can be done about that Watching-Only wallet?
If I try to send any more transactions from it there will no doubt be problems won't there?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 13, 2017, 12:22:04 AM
It needs a lot of RAM during the scan phase, but maintenance is around 350MB. You have to consider Core and your OS are also running, which will eat ~3GB+ each as well.

You can tone down the RAM utilization by lowering RAM target and thread count during the build & scan. Your issue is not fixed regardless, if you didn't rebuild your DB, it is still corrupt. You want to delete your Armory /databases folder, shut down your Bitcoin node and start ArmoryDB with the following command line:

Code:
--db-type=DB_BARE --ram-usage=1 --thread-count=(whatever you want)

Once the DB is done building (says "Enabling zero conf"), you can start ArmoryQt on top of it and the DB will start scanning. Once it is done scanning, you can shut this whole thing down and go back to regular operations.


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 13, 2017, 02:21:56 AM
It needs a lot of RAM during the scan phase, but maintenance is around 350MB. You have to consider Core and your OS are also running, which will eat ~3GB+ each as well.

You can tone down the RAM utilization by lowering RAM target and thread count during the build & scan. Your issue is not fixed regardless, if you didn't rebuild your DB, it is still corrupt. You want to delete your Armory /databases folder, shut down your Bitcoin node and start ArmoryDB with the following command line:

Code:
--db-type=DB_BARE --ram-usage=1 --thread-count=(whatever you want)

Once the DB is done building (says "Enabling zero conf"), you can start ArmoryQt on top of it and the DB will start scanning. Once it is done scanning, you can shut this whole thing down and go back to regular operations.

Okay I did all that. Everything went smoothly. Everything started quickly when I went back to regular operations. Thanks for all the help.

But again...

That transaction still doesn't show up after all these rescans; the wallet still has the old wrong balance. 
What can be done about that Watching-Only wallet?
If I try to send any more transactions from it there will no doubt be problems won't there?

Did I mess up that wallet when I used 'Clear All Unconfirmed' when the transaction really wasn't unconfirmed just that Armory never recognized it as such?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 13, 2017, 10:59:54 AM
Did I mess up that wallet when I used 'Clear All Unconfirmed' when the transaction really wasn't unconfirmed just that Armory never recognized it as such?

What's your top block in the bottom right corner?


Title: Re: Armory 0.96 is out
Post by: Ente on May 13, 2017, 01:26:56 PM
You mean you managed to import an compressed priv key into an Armory wallet? That's damn weird. Can you try to reproduce this on testnet?

In fact I am not entirely sure what exactly I imported.
It certainly was a vanity-address, generated with vanitygen.
I imported the private key. I couldn't spend funds on that address with Armory. I believe I sent the funds to the vanity-address I created, but Armory showed a different address when importing the privkey. But then I did see the funds in a pre-0.96 Armory, just couldn't spend them. I am not too sure.

I remember that I could import privkeys created by bitcoinj, but couldn't see the funds there, and that bitcoinj used compressed keys back then already.

Anyway, I'll just wait for the final version of the new wallet format and check again then.
If you want I'll send you the crashing wallet to have a look by yourself.
It's all not too important for me. But maybe I found some weird cornercase that helps for finalizing the wallet format?

Cheers,

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on May 13, 2017, 01:40:46 PM
Quote
If you want I'll send you the crashing wallet to have a look by yourself.
It's all not too important for me. But maybe I found some weird cornercase that helps for finalizing the wallet format?

I'd look at a WO copy.


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 13, 2017, 05:07:14 PM
Did I mess up that wallet when I used 'Clear All Unconfirmed' when the transaction really wasn't unconfirmed just that Armory never recognized it as such?

What's your top block in the bottom right corner?

455618 ( or something close to that... I didn't write it down before I tried another restart... )

Yes it appears to be stuck there, and now when I start it up again it seems to be stalled at the scanning history stage again...

The console has this in it:
... BDM thread failed: empty pool ptr
... Starting address registration process
... running 10 zc parser threads
...


Title: Re: Armory 0.96 is out
Post by: goatpig on May 13, 2017, 06:12:32 PM
You're gonna to delete about 110 blkXXXXX.dat files worth of block data.


Title: Re: Armory 0.96 is out
Post by: HyperDesmo on May 13, 2017, 08:28:51 PM
Hi,

I'm receiving an error: "Armory failed to spawn the DB!". Could you please help me with this issue? At first I wanted install on F: cause it's my HDD disk, but after this problem appears I switched to C:, so that's why you can see F: in the log.

Code:
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1262 -    Armory Version        : 0.96
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1263 -    Armory Build:         : a3d01aa722
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1264 -    PyBtcWallet  Version  : 1.35
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1266 -    OS Variant            : 8-6.2.9200--Multiprocessor Free
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1267 -    User home-directory   : C:\Users\XXX\AppData\Roaming
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1268 -    Satoshi BTC directory : C:\Users\XXX\AppData\Roaming\Bitcoin\
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1269 -    Armory home dir       : C:\Users\XXX\AppData\Roaming\Armory\
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs    :
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1271 -    Total Available RAM   : 15.89 GB
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1272 -    CPU ID string         : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1273 -    Number of CPU cores   : 8 cores
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1274 -    System is 64-bit      : True
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1275 -    Preferred Encoding    : cp1250
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1276 -    Machine Arch          : amd64
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1277 -    Available HDD (ARM)   : 18 GB
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1278 -    Available HDD (BTC)   : 18 GB
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     thread_count    : -1
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     rescan          : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     ignoreAllZC     : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     rescanBalance   : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     disableModules  : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     port            : None
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     interport       : 8223
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     coverageOutputDir: None
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     forceWalletCheck: False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     regtest         : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     rebuild         : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     nettimeout      : 2
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     datadir         : DEFAULT
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     clearMempool    : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     offline         : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     armoryDBDir     : DEFAULT
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_port   : 9001
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiPort     : DEFAULT
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     useTorSettings  : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     netlog          : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     keypool         : 100
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     coverageInclude : None
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     forceOnline     : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     redownload      : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     rpcBindAddr     : 127.0.0.1
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_ip     : 127.0.0.1
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     multisigFile    : DEFAULT
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     ram_usage       : -1
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     mtdebug         : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     logDisable      : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     settingsPath    : C:\Users\XXX\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     language        : en
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     db_type         : DB_FULL
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     doDebug         : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     enableDetSign   : True
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     disableConfPermis: False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     testnet         : False
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     rpcport         : DEFAULT
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiHome     : DEFAULT
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiRpcport  : DEFAULT
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     logFile         : C:\Users\XXX\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1285 -     verbosity       : None
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\XXX\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-13 22:24 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-05-13 22:24 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-13 22:24 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background. 
2017-05-13 22:24 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-13 22:24 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-13 22:24 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-13 22:24 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\XXX\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-13 22:24 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-13 22:24 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-13 22:24 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-13 22:24 (INFO) -- ArmoryQt.py:2172 -    Wallet (XXX):   "Primary Wallet                  "   (Encrypted)
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user.  Done!
2017-05-13 22:24 (INFO) -- ArmoryQt.py:558 - Usermode: Advanced
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1682 -    From: Advanced
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1690 -      To: Advanced
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = F:\Program Files\Armory
2017-05-13 22:24 (ERROR) -- ArmoryQt.py:1808 - Failed to start Armory database: Invalid blockdata path
Traceback (most recent call last):
  File "ArmoryQt.py", line 1793, in startArmoryDBIfNecessary
  File "SDM.pyc", line 368, in spawnDB
BadPath: Invalid blockdata path
2017-05-13 22:24 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 0


Title: Re: Armory 0.96 is out
Post by: goatpig on May 13, 2017, 09:05:25 PM
Code:
BadPath: Invalid blockdata path

Specify your block data folder with --satoshi-datadir


Title: Re: Armory 0.96 is out
Post by: HyperDesmo on May 13, 2017, 09:43:21 PM
Thanks for help. I tried that, exactly as you wrote and how it's in https://www.bitcoinarmory.com/troubleshooting/ Command-Line Options, but error and log is the same. I tried both C: and F: and created folders myself. Will try tomorrow, maybe I did sth wrong...

Quote
2017-05-13 23:38 (ERROR) -- ArmoryQt.py:1808 - Failed to start Armory database: Invalid blockdata path
Traceback (most recent call last):
  File "ArmoryQt.py", line 1793, in startArmoryDBIfNecessary
  File "SDM.pyc", line 368, in spawnDB
BadPath: Invalid blockdata path
2017-05-13 23:38 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 0


Title: Re: Armory 0.96 is out
Post by: achow101 on May 13, 2017, 09:49:30 PM
Thanks for help. I tried that, exactly as you wrote and how it's in https://www.bitcoinarmory.com/troubleshooting/ Command-Line Options, but error and log is the same. I tried both C: and F: and created folders myself. Will try tomorrow, maybe I did sth wrong...
If you copy and pasted directly from the examples on that site, then it is wrong. There's something wrong with the quotation marks that are used there. Type it out manually, don't copy and paste.

Also, bitcoinarmory.com is not our website. The website is https://btcarmory.com/


Title: Re: Armory 0.96 is out
Post by: Ente on May 13, 2017, 10:03:06 PM
Also, bitcoinarmory.com is not our website. The website is https://btcarmory.com/

..seems like ATI is gone for good now. Maybe they'll give us the domain? Maybe a small fundraiser would help. Or they shall shut it down, link to the new one or similar? I guess they would have a small, vague interest to help the current development, if they still hope to gain anything from their involvement back then?

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on May 13, 2017, 10:13:22 PM
Thanks for help. I tried that, exactly as you wrote and how it's in https://www.bitcoinarmory.com/troubleshooting/ Command-Line Options, but error and log is the same. I tried both C: and F: and created folders myself. Will try tomorrow, maybe I did sth wrong...

Where is your bitcoin datadir located?


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 14, 2017, 12:50:00 AM
You're gonna to delete about 110 blkXXXXX.dat files worth of block data.

Did that and then started bitcoin core... (to redownload those blocks?)
Deleted the database subdirectory again and ran armorydb again with those parameters you mentioned.
It only got up to 461207 this time... do I need to let bitcoin core run longer?

 :(


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 14, 2017, 01:08:25 AM
You're gonna to delete about 110 blkXXXXX.dat files worth of block data.

Did that and then started bitcoin core... (to redownload those blocks?)
Deleted the database subdirectory again and ran armorydb again with those parameters you mentioned.
It only got up to 461207 this time... do I need to let bitcoin core run longer?

 :(

Note: Bitcoin core was sync'd up to the latest block. It is perhaps rebuilding those blk...dat files in the background?

edit/ I mean shouldn't those blk...dat files be regenerated by bitcoin core?


Title: Re: Armory 0.96 is out
Post by: Stroto on May 14, 2017, 10:22:06 AM
Just a short simple question.

Would it be possible to make in 0.96.1 in wallet properties when I click on balances, comments, tx count or addresses and so it would order them (highest, alphabetical, etc)? It doesn't seem to work right now and i'm searching my ass off when i look for a particular address or balance.

Thank You for considering


Title: Re: Armory 0.96 is out
Post by: HyperDesmo on May 14, 2017, 11:14:44 AM
Where is your bitcoin datadir located?

I used:
Code:
%APPDATA%\Bitcoin
And received:
C:\Users\XXX\AppData\Roaming\Bitcoin
This folder exists, but it's empty


Title: Re: Armory 0.96 is out
Post by: goatpig on May 14, 2017, 01:14:10 PM
edit/ I mean shouldn't those blk...dat files be regenerated by bitcoin core?

They should have been. Let me look at dbLog.txt. Also, are you building the db with DB_BARE?


Title: Re: Armory 0.96 is out
Post by: goatpig on May 14, 2017, 01:15:37 PM
Just a short simple question.

Would it be possible to make in 0.96.1 in wallet properties when I click on balances, comments, tx count or addresses and so it would order them (highest, alphabetical, etc)? It doesn't seem to work right now and i'm searching my ass off when i look for a particular address or balance.

Thank You for considering

Will think about it.

Quote
This folder exists, but it's empty

Why is it empty? Do you not run your node against that folder?


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 14, 2017, 03:55:53 PM
You're gonna to delete about 110 blkXXXXX.dat files worth of block data.

I tried something else...

I got into settings and turned on the option to let Armory run Bitcoin Core in the background.
I put into the 'Bitcoin Home Dir' field the location of another Bitcoin installation on an external drive (HD).
The default installation I have on my C: drive is a SSD drive.

I still run Bitcoin Core manually before starting Armory and everything starts normally it seems.
Everything is sync'd up to the latest block. That missing tx shows now with the correct number of confirmations.
It looks like Armory is continuing to stay in sync as more blocks come in.
It showed 466380 in the bottom right when I first started it and right now it shows 466381.

/edit: The only thing seemingly not normal is that when I shutdown Armory, ArmoryDB stays open and I need to shut it down manually.


Title: Re: Armory 0.96 is out
Post by: goatpig on May 14, 2017, 04:00:11 PM
I put into the 'Bitcoin Home Dir' field the location of another Bitcoin installation on an external drive (HD).

So you have 2 copies of the chain to begin with?


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 14, 2017, 04:14:08 PM
I put into the 'Bitcoin Home Dir' field the location of another Bitcoin installation on an external drive (HD).

So you have 2 copies of the chain to begin with?

Yes.


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 14, 2017, 04:38:32 PM
I put into the 'Bitcoin Home Dir' field the location of another Bitcoin installation on an external drive (HD).

So you have 2 copies of the chain to begin with?

It's on an external drive that can be plugged into other computers. I don't run multiple instances of Bitcoin Core at the same time.
I don't see it having anything to do with the problem I had. 


Title: Re: Armory 0.96 is out
Post by: Portnoy on May 14, 2017, 05:02:02 PM
I put into the 'Bitcoin Home Dir' field the location of another Bitcoin installation on an external drive (HD).

So you have 2 copies of the chain to begin with?

It's on an external drive that can be plugged into other computers. I don't run multiple instances of Bitcoin Core at the same time.
I don't see it having anything to do with the problem I had. 

Oh damn!  I looked at the shortcut for my original installation of Bitcoin Core and I see that I have pointed it to yet another chain (my C: drive was getting full ).
When I point armory there everything works with that installation now as well...

Sorry for wasting your time.  :-[



Title: Re: Armory 0.96 is out
Post by: Ente on May 15, 2017, 11:48:02 AM
I'll try to give more details:

- I empty the entire .armory folder
- I copy that old 01.wallet
- I start Armory
- a "mirroring" popup shows for some seconds , the following files are created:

Quote
01_backup.wallet
armory_2bXSMWfMy_wallet.lmdb
armory_2bXSMWfMy_wallet.lmdb-lock
armorycpplog.txt
armorylog.txt
ArmorySettings.txt
databases

- the licence agreement shows, I accept it
- a short flash of GUI is seen, file "multipliers" is created,  new entries into armorylog (last one: "Dashboard switched to "Scanning" mode")
- segfault with no entries into any logfiles or on the terminal that I can see

My Armory is pulled from Git, checkout v0.96, regular installation procedure with no edits to any files.
Started with regular
Quote
python ArmoryQt.py --armorydb-ip=192.168.1.1 --armorydb-port=9001
And as I hinted, if this is a local problem here on my side, I don't even need this fixed.

I hope anything is of help here?

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on May 15, 2017, 12:33:46 PM
Build 0.96.1 and try again.


Title: Re: Armory 0.96 is out
Post by: Ente on May 15, 2017, 04:17:02 PM
Build 0.96.1 and try again.

All the same segfault with v0.96.0.1-testing.

Ente


Title: Re: Armory 0.96 is out
Post by: HyperDesmo on May 15, 2017, 04:26:22 PM
Why is it empty? Do you not run your node against that folder?

I did not! That was the issue the whole time. Thanks for help!


Title: Re: Armory 0.96 is out
Post by: goatpig on May 15, 2017, 04:35:07 PM
Build 0.96.1 and try again.

All the same segfault with v0.96.0.1-testing.

Ente

You mean the invalid instruction issue?


Title: Re: Armory 0.96 is out
Post by: Ente on May 15, 2017, 06:18:32 PM
Build 0.96.1 and try again.

All the same segfault with v0.96.0.1-testing.

Ente

You mean the invalid instruction issue?

It still does the same instant segfault crashing when trying to load the GUI (apparently), like in v0.96.
I don't know about "invalig instruction", I never saw any logentries or the like considering the segfault.
To me, it looks like the same (crashing) behavior as before.

I didn't upgrade the remote ArmoryDB though, only the local ArmoryQT.

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on May 15, 2017, 07:10:49 PM
Build the client yourself and try with that.


Title: Re: Armory 0.96 is out
Post by: naska21 on May 16, 2017, 11:48:06 AM
hi,

I am still using 0.93.3 version for both online and offline wallets of Armory  in conjuction with bitcoin core 0.11.2 and would appreciate any recomendations for smooth migration from 0.93.3 to 0.96 on Win 10 machine


Title: Re: Armory 0.96 is out
Post by: achow101 on May 16, 2017, 03:00:07 PM
hi,

I am still using 0.93.3 version for both online and offline wallets of Armory  in conjuction with bitcoin core 0.11.2 and would appreciate any recomendations for smooth migration from 0.93.3 to 0.96 on Win 10 machine
On you online machine, upgrade to Bitcoin Core 0.14.1 and Armory 0.96.0.1-testing. To install, just download and run the installers, you don't need to do anything else. Once both are installed, go to the Armory datadir and delete the folder named databases. Your offline machine does not need to be upgraded as long as you only use the p2pkh address type.


Title: Re: Armory 0.96 is out
Post by: naska21 on May 16, 2017, 03:19:23 PM
hi,

I am still using 0.93.3 version for both online and offline wallets of Armory  in conjuction with bitcoin core 0.11.2 and would appreciate any recomendations for smooth migration from 0.93.3 to 0.96 on Win 10 machine
On you online machine, upgrade to Bitcoin Core 0.14.1 and Armory 0.96.0.1-testing. To install, just download and run the installers, you don't need to do anything else. Once both are installed, go to the Armory datadir and delete the folder named databases. Your offline machine does not need to be upgraded as long as you only use the p2pkh address type.

why 0.96.0.1-testing but not just 0.96? I do not like the word testing. And one more Q. Is it mandatory for me to migrate or I can continue to enjoy bitcoin with 0.93.3 ?


Title: Re: Armory 0.96 is out
Post by: achow101 on May 16, 2017, 03:34:26 PM
why 0.96.0.1-testing but not just 0.96? I do not like the word testing.
0.96 has some weirdness that has been fixed for 0.96.1 but 0.96.1 is still in the testing phase.

And one more Q. Is it mandatory for me to migrate or I can continue to enjoy bitcoin with 0.93.3 ?
You can still use Bitcoin with 0.93.3. However you will be missing all of the improvements to the database, performance, coin selection, fee control, etc. that have been made since.


Title: Re: Armory 0.96 is out
Post by: naska21 on May 16, 2017, 04:02:39 PM
why 0.96.0.1-testing but not just 0.96? I do not like the word testing.
0.96 has some weirdness that has been fixed for 0.96.1 but 0.96.1 is still in the testing phase.

And one more Q. Is it mandatory for me to migrate or I can continue to enjoy bitcoin with 0.93.3 ?
You can still use Bitcoin with 0.93.3. However you will be missing all of the improvements to the database, performance, coin selection, fee control, etc. that have been made since.

Does it mean that that DB in v > 0.93.3 is much smaller in size? 0.93.3 runs very smoothly for me but its DB is very huge/


Title: Re: Armory 0.96 is out
Post by: achow101 on May 16, 2017, 04:04:20 PM
Does it mean that that DB in v > 0.93.3 is much smaller in size? 0.93.3 runs very smoothly for me but its DB is very huge/
Yes. The DB has been significantly reduced in size. On my computer, it is ~1 GB.


Title: Re: Armory 0.96 is out
Post by: naska21 on May 16, 2017, 04:06:56 PM
Does it mean that that DB in v > 0.93.3 is much smaller in size? 0.93.3 runs very smoothly for me but its DB is very huge/
Yes. The DB has been significantly reduced in size. On my computer, it is ~1 GB.

Great. On mine it is about 100 G/ Definitely will migrate. Thanks for your time


Title: Re: Armory 0.96 is out
Post by: Ente on May 16, 2017, 04:10:26 PM
Build the client yourself and try with that.

I did pull the sources from git and compiled myself, from the v0.96.0.1-testing tag. The regular way with
Quote
sh autogen.sh
./configure
make
I am unsure what you mean with "build yourself", something different than what I did?

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on May 16, 2017, 04:13:18 PM
I am unsure what you mean with "build yourself", something different than what I did?

0.96 could not build on old CPUs cause of the broken cryptopp makefile. I assumed you were using builds instead of building from source because of that.


Title: Re: Armory 0.96 is out
Post by: naska21 on May 16, 2017, 08:05:09 PM
Does it mean that that DB in v > 0.93.3 is much smaller in size? 0.93.3 runs very smoothly for me but its DB is very huge/
Yes. The DB has been significantly reduced in size. On my computer, it is ~1 GB.

Great. On mine it is about 100 G/ Definitely will migrate. Thanks for your time

migrated to 0.96.0.1  and noticed some bug when trying to fill the  Fee/Byte (Satoshi/byte)field in Select Fee Type subwindow when constructing the offline transactio. It works correct if the number put into this field is 50 or less. But if it is > than 50 the final fee is not correct. For example I put 200 but it shows only 20 sat/B . If I put 100 it shows 10 Sat/B  if I put 80  it shows 8 sat/B/ Moreover when i was trying to preview transactions with such weird numbers it always resulted in Coin Selection failed with error:targetVal>value  


Title: Re: Armory 0.96 is out
Post by: goatpig on May 16, 2017, 08:21:49 PM
Your mix of fee and spend value is more than what you can actually spend. Are you using the coin control feature or are you spending very low amounts?


Title: Re: Armory 0.96 is out
Post by: naska21 on May 16, 2017, 08:49:10 PM
Your mix of fee and spend value is more than what you can actually spend. Are you using the coin control feature or are you spending very low amounts?

using the coin control feature and it seems I found why such an error. The number u put into field above must not exceed that one put into Manual fee/byte in File=>Settings=>Fee and Address Types. So in my oppinion the option   that allows to change the fee in Select Fee Type subwindow is missleading

And one more view. 0.93.3 was allowing to see all addresses available and the fund on each of them. It was very convinient. It seems that  0.96 does not allow this and all addresses are hidden as u must to double click to make visible at least one of them but not all in bunch . i.e Wallet Properties window in 0.96.0.1 does not show all addresses available. It is not convinient


Title: Re: Armory 0.96 is out
Post by: goatpig on May 16, 2017, 09:37:18 PM
using the coin control feature and it seems I found why such an error.

Describe it step by step.

Quote
The number u put into field above must not exceed that one put into Manual fee/byte in File=>Settings=>Fee and Address Types. So in my oppinion the option   that allows to change the fee in Select Fee Type subwindow is missleading

Defaults do not override user inputs. You need elaborate on what you are doing or I cannot figure out what the issue is.

Quote
And one more view. 0.93.3 was allowing to see all addresses available and the fund on each of them. It was very convinient. It seems that  0.96 does not allow this and all addresses are hidden as u must to double click to make visible at least one of them but not all in bunch . i.e Wallet Properties window in 0.96.0.1 does not show all addresses available. It is not convinient

You have to widen the first column.


Title: Re: Armory 0.96 is out
Post by: naska21 on May 17, 2017, 07:09:34 AM


You have to widen the first column.

OK, did it, the addresses was hidden by Comment column. Now seems to be nice




Describe it step by step.


Ok, step-by-step

v 0.96.0.1

1) File > Settings >Fee and Address Types > Manual fee/byte   set 50 (for example) > x
2)Offline Transaction >Create New Offline Transaction> Coin Control>  and I choose onle single p2pkh address with only one input that has 0.02049708 btc > Accept
3) Check Use an existing address for charge > check Specify a change address > click book icon > and I choose address  xxxxxxxxxxxxx from number of options > Select Adress : xxxxxxxxxx
4)Enter Recipients Window click icon book  and I choose address AAAAAAAAA > Select Address:AAAAAAAAAA
5)Amount > Max it shows 0.02038508  from 0.02049708 available by step 2
11
6) have Size: 259B, Fee : 0.000112 BTC (50.00 sat/B - according defalt I set in step 1)
7) I decided to increese the fee and clicked on the field "Size: 259B, Fee : 0.000112 BTC" The window Select Fee Type pop up
8)I put in that window 100 instead of default 50 choosen in step 1 and have: Size: 259B, Fee : 0.000259 BTC (10.00sat/B - this is a bug - must be 100 sat/B)  >Close
9)Preview Transaction > Window Coin Selection Failure poping upshowng targetVal> value

As I got it the  amount to send was not automaticaly  fit to the new fee choosen.



Title: Re: Armory 0.96 is out
Post by: gangtraet on May 17, 2017, 07:39:48 AM
As I got it the  amount to send was not automaticaly  fit to the new fee choosen.

I am pretty sure that if you change the fee, you have to press the Max button again to recalculate the amount you are sending.  The Max button does not set a flag stating you want to send everything, instead it calculates what "everything" is, and fills the amount for you.  But if you do something to change that calculation, you have to redo it (i.e. click Max again).


Title: Re: Armory 0.96 is out
Post by: naska21 on May 17, 2017, 09:27:01 AM
As I got it the  amount to send was not automaticaly  fit to the new fee choosen.

I am pretty sure that if you change the fee, you have to press the Max button again to recalculate the amount you are sending.  The Max button does not set a flag stating you want to send everything, instead it calculates what "everything" is, and fills the amount for you.  But if you do something to change that calculation, you have to redo it (i.e. click Max again).



Indeed it did a trick, thanks


Title: Re: Armory 0.96 is out
Post by: goatpig on May 17, 2017, 03:30:56 PM
I see what the issue is. You want a "Max" button that's binding basically?


Title: Re: Armory 0.96 is out
Post by: Carlton Banks on May 17, 2017, 06:23:20 PM
I see what the issue is. You want a "Max" button that's binding basically?

Would make sense as a checkbox, with some kind of other visual feedback as to what's happening and why. Although I'm alright with the simple button based way we have right now


Title: Re: Armory 0.96 is out
Post by: goatpig on May 17, 2017, 07:36:59 PM
I see what the issue is. You want a "Max" button that's binding basically?

Would make sense as a checkbox, with some kind of other visual feedback as to what's happening and why. Although I'm alright with the simple button based way we have right now

It's much simpler to implement it as is. This is one of those cases where the demand does not justify the implementation cost.


Title: Re: Armory 0.96 is out
Post by: naska21 on May 18, 2017, 05:57:30 AM
I see what the issue is. You want a "Max" button that's binding basically?

Would make sense as a checkbox, with some kind of other visual feedback as to what's happening and why. Although I'm alright with the simple button based way we have right now

It's much simpler to implement it as is. This is one of those cases where the demand does not justify the implementation cost.

Now when I got all logics behind the scene  everytning is OK with me. leave as it is and thanks for the nice product with a lot of improvements compared to 0.93


Title: Re: Armory 0.96 is out
Post by: Stroto on May 18, 2017, 08:29:19 AM
Just a short simple question.

Would it be possible to make in 0.96.1 in wallet properties when I click on balances, comments, tx count or addresses and so it would order them (highest, alphabetical, etc)? It doesn't seem to work right now and i'm searching my ass off when i look for a particular address or balance.

Thank You for considering

Will think about it.


In case someone else was searching for a particular address or so...

I found a way around it for now. When opening "Send Bitcoins" > "Address book" I can organize on tx, addresses, comments and balances.


Title: Re: Armory 0.96 is out
Post by: Stroto on May 18, 2017, 09:00:34 AM
Different question.

Can someone ELI5 me on how to use RBF in armory?

I tried to make a tx with RBF enabled, that worked.
It shows the tx with the comment *Right click to bump fee*. 0 conf
When I right click it a pop up appears but when i press "bump fee" in that nothing happens.

When opening "send bitcoins" again and RBF control enabled (it shows description: *RBF subset*) and recreate the same amount to the same address just with a higher fee I get the message "Coin selection failed with error: "Invalid spend value"

 ???

Code:
2017-05-18 11:11 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3340, in showContextMenuLedger
  File "ArmoryQt.py", line 5891, in bumpFee
  File "ui\TxFrames.pyc", line 1295, in prefillFromBatch
  File "ui\TxFrames.pyc", line 1342, in prefill
KeyError: 'change'



Title: Re: Armory 0.96 is out
Post by: achow101 on May 18, 2017, 02:58:14 PM
Different question.

Can someone ELI5 me on how to use RBF in armory?

I tried to make a tx with RBF enabled, that worked.
It shows the tx with the comment *Right click to bump fee*. 0 conf
When I right click it a pop up appears but when i press "bump fee" in that nothing happens.

When opening "send bitcoins" again and RBF control enabled (it shows description: *RBF subset*) and recreate the same amount to the same address just with a higher fee I get the message "Coin selection failed with error: "Invalid spend value"

 ???

Code:
2017-05-18 11:11 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3340, in showContextMenuLedger
  File "ArmoryQt.py", line 5891, in bumpFee
  File "ui\TxFrames.pyc", line 1295, in prefillFromBatch
  File "ui\TxFrames.pyc", line 1342, in prefill
KeyError: 'change'


Apparently RBF was broken in 0.96 and we didn't notice. Try using 0.96.1-testing build. It should be fixed there.


Title: Re: Armory 0.96 is out
Post by: Stroto on May 18, 2017, 05:33:40 PM
Apparently RBF was broken in 0.96 and we didn't notice. Try using 0.96.1-testing build. It should be fixed there.

I will check that next couple of days,
Thanks


Title: Re: Armory 0.96 is out
Post by: Ente on May 18, 2017, 09:24:59 PM
Two small UI notes:

- when clicking a wallet, I get four categories (used, unused, change, imported), and inside of those again three categories (p2pkh etc). Only then I actually get to see the individual addresses. I liked it more as it was earlier, with one large list as soon as I open the wallet. Back then, "imported" was a field in the long list, for example. It's not too bad yet, as I only have coins in the "used - p2pkh" category.

- in coin control, I don't see the comment I wrote to an address. This would make coin control close to useless for me. My workaround is to click through the wallet the regular way, mentally choose the inputs I would want to use, and choose the corresponding bitcoin-amount-address in coin control.

Both aren't that tragic, but maybe it's easy to change, as it only changed recently afaik.

Cheers,

Ente



Title: Re: Armory 0.96 is out
Post by: goatpig on May 18, 2017, 09:45:10 PM
- when clicking a wallet, I get four categories (used, unused, change, imported), and inside of those again three categories (p2pkh etc). Only then I actually get to see the individual addresses. I liked it more as it was earlier, with one large list as soon as I open the wallet. Back then, "imported" was a field in the long list, for example. It's not too bad yet, as I only have coins in the "used - p2pkh" category.

I'm not sure what you want to see changed there. Maybe pre-expending a section?

Quote
- in coin control, I don't see the comment I wrote to an address. This would make coin control close to useless for me. My workaround is to click through the wallet the regular way, mentally choose the inputs I would want to use, and choose the corresponding bitcoin-amount-address in coin control.

That's a miss on my part, will add for .1


Title: Re: Armory 0.96 is out
Post by: Ente on May 18, 2017, 10:09:59 PM
- when clicking a wallet, I get four categories (used, unused, change, imported), and inside of those again three categories (p2pkh etc). Only then I actually get to see the individual addresses. I liked it more as it was earlier, with one large list as soon as I open the wallet. Back then, "imported" was a field in the long list, for example. It's not too bad yet, as I only have coins in the "used - p2pkh" category.
I'm not sure what you want to see changed there. Maybe pre-expending a section?
Me neither :-)
Maybe merging all four categories and three subcategories into one large list, with sortable fields? It was more like that when there were only "regular" and "imported" addresses. Of course it wouldn't make sense to have 12 more rows though.

Quote
Quote
- in coin control, I don't see the comment I wrote to an address. This would make coin control close to useless for me. My workaround is to click through the wallet the regular way, mentally choose the inputs I would want to use, and choose the corresponding bitcoin-amount-address in coin control.
That's a miss on my part, will add for .1
Nice! That is, for me, the much more helping change of the two. I'm happy :-)

Cheers,

Ente


Title: Problem restoring from fragmented paper backup
Post by: Quazzmo on May 21, 2017, 10:50:52 PM
Binaries:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96

changelog

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt

Notable changes:

1) SegWit
2) RBF & CPFP
3) Translations
4) Compressed public keys
5) Reworked coin control and address tree UI
6) Fleshed out fee and privacy features

Better description on the webpage: https://btcarmory.com/0.96.0-release/

Notes:

Only putting out Windows x64 and Linux x64 builds atm. Offline bundles, RPi and OSX builds for 0.96.1, once I get rid of the twisted/openssl dependency. Eta 1-2 weeks.

Thanks:

achow101 for the support and translation PR, droark for the OSX support and the testers for helping tiddy things up.

Enjoy =)





Happy to see Armory still moving forward, efforts are much appreciated here!
Has anyone successfully restored from a fragmented two of three paper backup with 0.96?
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!
I'm trying to restore from a 2 of 3 fragmented paper backup, wallet version 1.35c with a SecurePrint code.
I type in my two fragments, but the "Restore from fragments" button remains disabled bottom right.
Am I doing something wrong, or is this a bug with a workaround perhaps?
Getting a little nervous as now running low on options for accessing my funds... A Windows update destroyed the PC holding my bitcoins!

Thanks for any help :-)


Title: Re: Armory 0.96 is out
Post by: goatpig on May 22, 2017, 12:56:12 AM
Quote
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!

There is no such thing. Offline mode is basically what you should be using to restore backups. If you're having issues, post your logs. Use pastebin.


Title: Re: Armory 0.96 is out
Post by: Quazzmo on May 22, 2017, 07:36:52 AM
Quote
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!

There is no such thing. Offline mode is basically what you should be using to restore backups. If you're having issues, post your logs. Use pastebin.

Thanks goatpig, here's the partial armorylog.txt at the time of my first attempt to restore from the fragmented paper backup,
during which the "Restore from fragments" button remained greyed so I couldn't click it after typing in the codes:


2017-05-21 21:54 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-21 21:54 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-21 22:13 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 0
2017-05-21 22:13 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:16 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:16 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:25 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 0
2017-05-21 22:25 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:27 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:28 (INFO) -- ArmoryQt.py:4876 - New Block! : 467495
2017-05-21 22:28 (INFO) -- ArmoryQt.py:4884 - Current block number: 467495
2017-05-21 22:29 (INFO) -- ArmoryQt.py:4876 - New Block! : 467496
2017-05-21 22:29 (INFO) -- ArmoryQt.py:4884 - Current block number: 467496
2017-05-21 22:31 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:31 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:33 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2017-05-21 22:33 (INFO) -- SDM.pyc:457 - Called stopBitcoind
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5414 - Attempting to close the main window!
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2017-05-21 22:33 (INFO) -- SDM.pyc:457 - Called stopBitcoind
2017-05-21 22:33 (INFO) -- SDM.pyc:463 - ...but bitcoind is not running, to be able to stop
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5414 - Attempting to close the main window!
2017-05-21 22:33 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 5328, in closeEvent
  File "ArmoryQt.py", line 5415, in closeForReal
  File "twisted\internet\base.pyc", line 580, in stop
ReactorNotRunning: Can't stop reactor that isn't running.

2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe


Thanks for any suggestions!


Title: Re: Armory 0.96 is out
Post by: goatpig on May 22, 2017, 01:32:34 PM
Botched translation patch changes, easy fix on my end. Wait for the next testing build, sometimes this week.


Title: Re: Armory 0.96 is out
Post by: GodHatesFigs on May 24, 2017, 03:37:17 AM
I'm having trouble verifying the PGP Signature of the 0.96 hash with the Offline Signing Key. I've imported the Offline Signing Key from the Armory website (0x98832223) into Kleopatra , but when I try to verify the signature, I get the message:

"Signed on 2017-04-30 20:20 with unknown certificate 0x8C5211764922589A.
The signature is invalid: No public certificate to verify the signature"

The hash of the installer matches the one provided on the Armory website for the win64.exe file
(fce84bd0964a43a677b1be689e321c562c10a202a35fd052975f3c3536055dd7)

What am I doing wrong?



Title: Re: Armory 0.96 is out
Post by: goatpig on May 24, 2017, 03:45:07 AM
https://btcarmory.com/docs/verify

Using etotheipi key instead of mine.


Title: Re: Armory 0.96 is out
Post by: GodHatesFigs on May 24, 2017, 03:46:19 AM
Thanks!


Title: Re: Armory 0.96 is out
Post by: Brangdon on May 28, 2017, 10:37:46 AM
I am still using 0.93.3 version for both online and offline wallets of Armory  in conjuction with bitcoin core 0.11.2 and would appreciate any recomendations for smooth migration from 0.93.3 to 0.96 on Win 10 machine
I am also a returning user upgrading from 0.93.3. My version of bitcoin core was of a similar vintage. I updated both. When I ran Armory it ran bitcoin-qt for me, but that process quit and Armory didn't seem to notice. From the core logs I found I had to run bitcoin-qt directly and tell it to re-index the database. I'm currently doing this, and it seems to be going OK, but I thought you might want to know the process wasn't as smooth and automatic as one might wish and required this manual intervention.

Also, bitcoinarmory.com is not our website. The website is https://btcarmory.com/
Eeek. Bitcoinarmory.com is what a Google search found for me. This post is what made me realise it was old.

Still, I'm very pleased to learn Armory is back under active development. I was actually Googling "Armory replacement" and expecting to have to find a new wallet to spend my coins. In other good news, my offline computer still boots.


Title: Re: Armory 0.96 is out
Post by: bitbitcoincoin on June 07, 2017, 02:34:04 PM
Mine's working great. I sent a transaction and the comment says chained zc. Does that mean anything?

Means your tx is spending an unconfirmed txout.


I don't see any further replies on this issue.  I just had the same comment on my transaction and it's still showing unconfirmed after 12 hours when the previous transaction only took about 1 hour.  Do I need to do anything to have this transaction work or do I just wait for it to confirm>

Thanks. 


Title: Re: Armory 0.96 is out
Post by: goatpig on June 07, 2017, 02:47:30 PM
Chances are you didn't push a proper fee.


Title: Re: Armory 0.96 is out
Post by: bitbitcoincoin on June 07, 2017, 02:59:09 PM
Chances are you didn't push a proper fee.

Clicked send max, reading now there is a potential bug where Armory puts too small a fee when using the Max button?

Can I just clear unconfirmed and try again or am I risking a double spend and more issues?

Thanks for the quick reply.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 07, 2017, 04:28:02 PM
If there's change, you should CPFP. Otherwise clear unconfirmed and push again.


Title: Re: Armory 0.96 is out
Post by: bitbitcoincoin on June 07, 2017, 04:54:53 PM
If there's change, you should CPFP. Otherwise clear unconfirmed and push again.

It showed as the only transaction, no returning change.

I cleared unconfirmed and am trying again but now getting the "tx timeout" error, guessing I need to rebuild and rescan now?


Title: Re: Armory 0.96 is out
Post by: goatpig on June 07, 2017, 05:02:15 PM
No, use the testing build for 0.96.1


Title: Re: Armory 0.96 is out
Post by: bitbitcoincoin on June 07, 2017, 05:23:19 PM
No, use the testing build for 0.96.1

Just loaded it, clicked send with a higher fee this time and nothing happened after the passphrase window closed. Armory behaving as if I never tried to send any BTC, never had this happen before and it's kinda scary...


Title: Re: Armory 0.96 is out
Post by: goatpig on June 07, 2017, 06:00:33 PM
post armorylog.txt


Title: Re: Armory 0.96 is out
Post by: bitbitcoincoin on June 07, 2017, 09:58:17 PM
quite a lot to it, going through it looks like this is where Im getting an error when I try to send after updating to the beta edition

2017-06-07 10:21:52 (INFO) -- ArmoryQt.py:3099 - Sending Tx, 7fc06e76fa56988078b52575391fb98472fbdcd6796567399df6728d739f9d36
2017-06-07 10:21:58 (ERROR) -- Traceback (most recent call last):
  File "ui\QtExecuteSignal.pyc", line 31, in methodSlot
  File "ArmoryQt.py", line 5036, in handleCppNotification
  File "ArmoryQt.py", line 3114, in zcBroadcastError
  File "CppBlockUtils.pyc", line 3012, in broadcastThroughRPC
DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x000000000375CF30> >

Let me know if you need more info, I can post all of today but it's a ton of text.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 07, 2017, 11:00:20 PM
Turn on your node RPC.


Title: Re: Armory 0.96 is out
Post by: bitbitcoincoin on June 08, 2017, 04:38:40 PM
Turn on your node RPC.

After some research apparently this is bitcoind?  I remembered I had a error message pop up during the beta install which may have caused bitcoind to not run properly.

Anyways I just did what I did when I had a similar issue last week, reinstalled the non beta edition and now everything is working fine. Coins are now showing as confirmed on both ends, thanks for the help.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 09, 2017, 08:56:54 AM
After some research apparently this is bitcoind?  I remembered I had a error message pop up during the beta install which may have caused bitcoind to not run properly.

No, that's automating the node.

RPC is the other interface your node provides the is used in Armory to gather fee estimates and error status on transactions broadcast failure (if you use the latest testing version). This would give you an idea what's going on with your transaction.


Title: Re: Armory 0.96 is out
Post by: naska21 on June 09, 2017, 09:40:33 AM
Hi, Armory 0.96.0.1 stuck on  block 466853. The database is loading but after its building armory status always states Connected (466853 blocks)  :'( What should I do?

P.S. Did rebuild database. Now the status is Connected 470 510 blocks/ The blocks number corresponds to current one. Will see  if it changes with blocks found

P.P.S It follows the current block!


Title: Re: Problem restoring from fragmented paper backup
Post by: bjernvig on June 09, 2017, 06:36:32 PM
Binaries:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96

changelog

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt

Notable changes:

1) SegWit
2) RBF & CPFP
3) Translations
4) Compressed public keys
5) Reworked coin control and address tree UI
6) Fleshed out fee and privacy features

Better description on the webpage: https://btcarmory.com/0.96.0-release/

Notes:

Only putting out Windows x64 and Linux x64 builds atm. Offline bundles, RPi and OSX builds for 0.96.1, once I get rid of the twisted/openssl dependency. Eta 1-2 weeks.

Thanks:

achow101 for the support and translation PR, droark for the OSX support and the testers for helping tiddy things up.

Enjoy =)





Happy to see Armory still moving forward, efforts are much appreciated here!
Has anyone successfully restored from a fragmented two of three paper backup with 0.96?
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!
I'm trying to restore from a 2 of 3 fragmented paper backup, wallet version 1.35c with a SecurePrint code.
I type in my two fragments, but the "Restore from fragments" button remains disabled bottom right.
Am I doing something wrong, or is this a bug with a workaround perhaps?
Getting a little nervous as now running low on options for accessing my funds... A Windows update destroyed the PC holding my bitcoins!

Thanks for any help :-)

Hi I am having the same paper backup issue on my Windows 10 computer. I have also downloading the Armory 0.96.2 test version from githut and the"restore wallet" is then not disabled anymore, but nothing happens when clicking the button. Has this restore wallet issue been fixed in another build that I could maybe use?

Thanks for all your support on this one :)


Title: Re: Armory 0.96 is out
Post by: goatpig on June 09, 2017, 09:44:32 PM
It's most likely fixed in the code but not built for yet. Post your armorylog.txt for the good measure. Use pastebin.


Title: Re: Armory 0.96 is out
Post by: bjernvig on June 10, 2017, 11:49:05 AM
It's most likely fixed in the code but not built for yet. Post your armorylog.txt for the good measure. Use pastebin.

I have put the content of the log file here:
https://pastebin.com/ubxdjVWu

As you can see I have clicked the "Restore wallet" button a couple of times:-)

Thanks for the quick response by the way ;D


Title: Re: Armory 0.96 is out
Post by: goatpig on June 10, 2017, 01:01:55 PM
This is fixed in code already.


Title: Re: Armory 0.96 is out
Post by: bjernvig on June 10, 2017, 08:23:28 PM
Great!

Do you have an estimated date for when the release with the issue fixed will be made available?


Title: Re: Armory 0.96 is out
Post by: goatpig on June 10, 2017, 10:16:41 PM
Early next week


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 08:22:42 AM
Hey guys, I'm stuck here https://github.com/goatpig/BitcoinArmory/blob/master/osxbuild/OSX_build_notes.md "7. Compile Armory.

cd osxbuild
python build-app.py > /dev/null

No such file or directory


Title: Re: Armory 0.96 is out
Post by: gangtraet on June 13, 2017, 09:17:35 AM
That seems weird.  Have you checked that the file is there?  Have you spelled it correctly on the command line (perhaps using TAB completion).


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 09:52:27 AM
Did you git submodule?


Title: Re: Armory 0.96 is out
Post by: naska21 on June 13, 2017, 10:07:35 AM
Hi, noticed some issue with 0.96.0.1. After closing the list of available addresses the main window results in Not Responding state when trying to close it . Checked it several times.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 10:39:53 AM
Try with 0.96.0.2 and post armorylog.txt as well. Use pastebin.


Title: Re: Armory 0.96 is out
Post by: naska21 on June 13, 2017, 11:36:35 AM
Try with 0.96.0.2 and post armorylog.txt as well. Use pastebin.

did it with 0.96.0.2 . First time ater the same procedure Armory DB Sopped working error. The second time everything went smoothly. Just for the case  here is https://pastebin.com/raw/wHcM0mTU   some last part of my armorylog. BTW, how to clear armory's log?


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 11:48:33 AM
BTW, how to clear armory's log?
Quote

Delete armorylog.txt and dbLog.txt in your Armory datadir.



Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 12:03:34 PM
I restarted the computer, now I'm back in the terminal. the command 7. osxbuild doesn't work.

What git submodule command???


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 12:07:39 PM
https://bitcointalk.org/index.php?topic=1964192.msg19524492#msg19524492


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 12:10:04 PM
fatal: Not a git repository (or any of the parent directories): .git

From which repository I have to enter this command? whatever?


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 12:35:13 PM
How are you trying to build from source without setting up the git to get the source?


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 12:46:45 PM
I'm following the notes. What's the command? Thanks for your help!


Title: Re: Armory 0.96 is out
Post by: gangtraet on June 13, 2017, 12:52:17 PM
How are you trying to build from source without setting up the git to get the source?
You publish the source code together with the binaries on your release pages. 
(Could it be that the submodules are missing there?)


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 12:59:04 PM
How are you trying to build from source without setting up the git to get the source?
You publish the source code together with the binaries on your release pages. 
(Could it be that the submodules are missing there?)

I don't publish that, git does it automatically. Maybe that's the issue...

How are you trying to build from source without setting up the git to get the source?

Pick a top folder for the repo then do the following:

Quote
git clone https://github.com/goatpig/BitcoinArmory.git
cd BitcoinArmory
git submodule init
git submodule update

Then follow the build instructions from within that folder.


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 01:15:11 PM
Thanks again


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 02:31:24 PM
Armory failed to spawn the DB!


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 03:29:09 PM
Make sure there isn't an instance of ArmoryDB running. Then start the DB yourself with your command line arg.


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 03:53:31 PM
https://btcarmory.com/docs/faq

Can't find the command. And as well, can I retrieve a Multibit 18 words bip32 seed with this wallet?


Title: Re: Armory 0.96 is out; problem running 0.96; errors 1497371640 & 1497371641
Post by: Tim R on June 13, 2017, 05:50:44 PM
Don't see this posted yet. Windows 7 Pro new install 64 bit, plenty of HD space. Installed Bitcoin Core 14.1, fully synched chain; installed Armory 0.96. Run Armory in Admin mode, starts building database. Gets however far, errors out during "parsed block file #XXX). Most recent:
ERROR – 14973716-40..\SocketObject.cpp:134: (..\SocketObject.cpp) :285) POLLERR in writeToSocket
-ERROR – 1497371641: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR – 1497371641: (..\BitcoinidP2P.cppL1027( caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO  - 1497371641: (..\BitcoindP2P.cpp969) Disconnected from Bitcoin node
Appears to keep losing connection with Bicoin Core database. I reset Armory to factory settings deleting Armory database and settings but keeping Bitcoin Core database, restart Armory. Keeps getting error at different level of database build. Directory paths are correct. Is there another option besides deleting the entire Bitcoin Core database, uninstalling both programs, deleting all appdata for both programs and starting the blockchain build all over in Bitcoin Core and burning another 10 days? I previously also tried building the chain with only Armory 0.96 installed without Bitcoin Core and it would not even start the database build.


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 06:54:35 PM
I launched it with this command: open -a Armory

Still the same.

Edit: Resolved, I manually launched ArmoryDB.

Now, I need to change the "Path" that is wrong apparently!


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 08:47:50 PM
https://btcarmory.com/docs/faq

Can't find the command. And as well, can I retrieve a Multibit 18 words bip32 seed with this wallet?

That's for 0.97

Now, I need to change the "Path" that is wrong apparently!

Which path? You can set the blockchain path with --satoshi-datadir, the db path with --dbdir. You can create armorydb.conf in your datadir's folder and set the args there if you don't want to bother with them every run.


Title: Re: Armory 0.96 is out; problem running 0.96; errors 1497371640 & 1497371641
Post by: goatpig on June 13, 2017, 08:48:09 PM
Don't see this posted yet. Windows 7 Pro new install 64 bit, plenty of HD space. Installed Bitcoin Core 14.1, fully synched chain; installed Armory 0.96. Run Armory in Admin mode, starts building database. Gets however far, errors out during "parsed block file #XXX). Most recent:
ERROR – 14973716-40..\SocketObject.cpp:134: (..\SocketObject.cpp) :285) POLLERR in writeToSocket
-ERROR – 1497371641: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR – 1497371641: (..\BitcoinidP2P.cppL1027( caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO  - 1497371641: (..\BitcoindP2P.cpp969) Disconnected from Bitcoin node
Appears to keep losing connection with Bicoin Core database. I reset Armory to factory settings deleting Armory database and settings but keeping Bitcoin Core database, restart Armory. Keeps getting error at different level of database build. Directory paths are correct. Is there another option besides deleting the entire Bitcoin Core database, uninstalling both programs, deleting all appdata for both programs and starting the blockchain build all over in Bitcoin Core and burning another 10 days? I previously also tried building the chain with only Armory 0.96 installed without Bitcoin Core and it would not even start the database build.

This is fixed in the testing builds.


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 09:17:38 PM
Do I have to run a full node? Got 5gb left.

I'm trying to retrieve a seed from a multibit HD wallet that I've been using since 2 years... Dunno what happened, but the password doesn't work.

Anyway just money ey!


Title: Re: Armory 0.96 is out
Post by: Tim R on June 13, 2017, 09:30:33 PM
Reply to goatpig: Are the testing builds in the currently available download? If not, do you know when they be released?
UPDATE: Found a solution (or got lucky). I found helpful threads elsewhere that I did not find before and tried many variations. Sharing here to hopefully help someone else. Closed Bitcoin Core and Armory. Restarted computer. Opened only Armory in Admin user from shortcut menu. Ran offline, so skipped loading wallet. In Armory Help, reset to factory default and chose middle option to delete Armory database and settings but retained Bitcoin Core database. Closed Armory and restarted computer. Only opened Armory again in Admin user. Let it run and it fully populated the database. Never opened Bitcoin Core in this sequence. I had tried many of these options together but not in this sequence.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 09:55:50 PM
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.2-testing

or wait a couple days for the next build.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 13, 2017, 09:56:52 PM
Do I have to run a full node? Got 5gb left.

I'm trying to retrieve a seed from a multibit HD wallet that I've been using since 2 years... Dunno what happened, but the password doesn't work.

Anyway just money ey!

Armory can't make sense of that seed. From what I'm being told, no other wallet currently can besides Multibit itself. And yes, Armory requires a full node.


Title: Re: Armory 0.96 is out
Post by: Alexoz on June 13, 2017, 11:46:32 PM
I'm trying that way to retrieve my funds. Got to scan all the addresses! https://iancoleman.github.io/bip39/

Just a question. Can a run a node on an external hard drive with the installation as is? And is it safe to store my bit coins before the first of August?

Actually I heard a lot of stuff, but it's not as bad as people think right?! No need for a Trezor wallet...

What are you thoughts Goatpig?


Title: Re: Armory 0.96 is out
Post by: goatpig on June 14, 2017, 12:05:22 AM
A proper cold storage setup is preferable to a HW wallet. These are better suited for daily spending purposes.

You can't import your Multibit seed in Armory as is. If you want to migrate your funds to Armory, should create a wallet in Armory, grab a recipient address and send your coins to that from Multibit. You can also reveal the private keys in Multibit and sweep them in Armory, but that's a whole let more prone to error.

You can run the blockchain data in an external drive. If you have another machine, you can set the node + database on that machine and run the client on your regular PC if you feel so inclined. Your biggest limitation is bootstrapping the node, which demands a lot of bandwidth and disk space.

As for August 1st, all pre fork coins will be present on both side of the fork. Anything you spend past that point can and will be mimicked on both sides, unless you taint your coins to be valid on only a given side. If you are dead set on which side you want to be in, you can go down that path. Otherwise you are better off just sitting it out.


Title: Re: Armory 0.96 is out
Post by: Ente on June 14, 2017, 07:52:42 PM
Quote
git submodule init
git submodule update

This did confuse a lot of people, and it will be many more.
I'd suggest to print a clear errormessage if submodules are missing, and ask the use if the above was done?

Ente


Title: Re: Armory 0.96 is out
Post by: goatpig on June 14, 2017, 09:51:16 PM
Will have to figure it out with autotools. yey....


Title: Re: Armory 0.96 is out
Post by: naska21 on June 15, 2017, 09:08:24 AM
You can set the blockchain path with --satoshi-datadir, the db path with --dbdir. You can create armorydb.conf in your datadir's folder and set the args there if you don't want to bother with them every run.

Could you specify this dir more presicely, is it this ....Roaming/Armory/databaseses ?

And what exactly should be put into armorydb.conf ?  Please,  give an example

Today did transaction (with 0.96.0.2) that succeed but some error window has poped up
http://i63.tinypic.com/f2litf.png

what is this?

In fact I has put a bit lower fee than suggested one (200 Sat/B instead of suggested 400 Sat/B). However it was included into the 1st following block , but such error was a bit  distracting to me


Title: Re: Armory 0.96 is out
Post by: goatpig on June 15, 2017, 03:41:18 PM
what is this?

In fact I has put a bit lower fee than suggested one (200 Sat/B instead of suggested 400 Sat/B). However it was included into the 1st following block , but such error was a bit  distracting to me

Means your node has bad connectivity/is overloaded. Update to 0.96.0.3 for better verbose.

Quote
Could you specify this dir more presicely, is it this ....Roaming/Armory/databaseses ?

https://btcarmory.com/docs/pathing


Title: Re: Armory 0.96 is out
Post by: Brangdon on June 19, 2017, 03:59:31 PM
I tried to send transaction 8f124355f16f6df69aa3985d464b817bcfa4190a95bedb96ecff6090dc29d2af back on 4th June, and it got zero confirmations. I figured my fee was too low and it would eventually either confirm or disappear, but it still shows as 0 confirmations now, with Armory claiming "Connected" and "(469262 blocks)". I checked on Blockchain Info (https://blockchain.info/tx/8f124355f16f6df69aa3985d464b817bcfa4190a95bedb96ecff6090dc29d2af) which says is confirmed after 9 minutes. Why is Armory still saying it is unconfirmed?

I am using Armory 0.96.0.2 and Bitcoin Core v0.14.1. I recently updated both after a long period of not using Bitcoin, but my wallets and older transactions show up fine.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 19, 2017, 06:34:35 PM
(469262 blocks)

You're trailing over 1000 blocks.


Title: Re: Armory 0.96 with Bitcoin Core 14.1 unconfirmed transaction
Post by: Tim R on June 19, 2017, 11:11:44 PM
I installed Armory 0.96 and Bitcoin Core 14.1 onto a new computer. Got wallets set up in Armory. Blockchain fully synced. Moved part of balance from Armory to Coinbase to test and Coinbase shows balance available to use, so was node processed. Went to send rest of Armory balance to Coinbase and remaining Armory balance shows unconfirmed. Closed Armory. Deleted mempool.dat, then restarted Armory. Synced. Still shows unconfirmed. The remaining balance is not actually a received transaction awaiting node processing, rather just the total of my wallet balances. How do I get my Armory wallet balances confirmed when there was no transaction sending the remaining balance there? I was going to try running Armory with "-rescan" but don't know how to do that - if that is a potential solution.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 19, 2017, 11:46:24 PM
Post your logs.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 20, 2017, 10:13:18 PM
TimR: use pastebin!


Title: Re: Armory 0.96 is out
Post by: Tim R on June 20, 2017, 10:47:03 PM
Just saw your pastebin comment after sending last one. My apologies.
https://pastebin.com/usdT2f8Q


Title: Re: Armory 0.96 is out
Post by: goatpig on June 20, 2017, 11:03:05 PM
So your tx still appears as unconfirmed in Armory?


Title: Re: Armory 0.96 is out
Post by: Tim R on June 20, 2017, 11:05:32 PM
yes, still unconfirmed. FYI I am on the 6 minute gap for posting due to newbie to site.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 20, 2017, 11:08:26 PM
After log file inspection, you will have to wait for new testing build to get the fix.


Title: Re: Armory 0.96 is out
Post by: Tim R on June 20, 2017, 11:12:50 PM
Any guess on timing? Had planned to utilize for upcoming ICO. What actions would I need to do once testing build is online, or will tx automatically just become confirmed?


Title: Re: Armory 0.96 is out
Post by: Tim R on June 20, 2017, 11:43:15 PM
goatpig:  Many thanks for checking it out!


Title: Re: Armory 0.96 is out
Post by: goatpig on June 21, 2017, 12:10:42 AM
You can try to build the testing branch if you want to use the fix right now. Otherwise, sometimes this weekend.


Title: Re: Armory 0.96 is out
Post by: Tim R on June 21, 2017, 04:01:01 PM
Okay, great! Will wait for your post where to download that build fix. Thanks again.


Title: Re: Armory 0.96 is out
Post by: visdude on June 25, 2017, 07:56:20 PM

1. I still have 0.92.3 as my cold/offline wallet on a Windows 7 32-bit machine. Can I simply just install 0.96 (or future releases from here on for that matter) over 0.92.3 to update and bring it up to speed?

2. Will an option in Settings to define an explicit Armory data directory location be included in the next release? There is already such option to point Armory to an explicit Bitcoin Core data directory so providing one for the Armory data directory as well would be very helpful...and makes sense. At this point, one still has to do some CLI arg gymnastics to effectuate such a setting. It's not fun and quite stressful for us who suffer from CLI phobia especially in Linux (Mint) wherein I still have to edit the executable with "sudo vi /usr/share/applications/armory.desktop" (credit to Carlton Banks for the instruction/guide) which I currently couldn't get it to work anymore. I guess I am requesting such a feature.



Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 12:58:57 AM
1. I still have 0.92.3 as my cold/offline wallet on a Windows 7 32-bit machine. Can I simply just install 0.96 (or future releases from here on for that matter) over 0.92.3 to update and bring it up to speed?

If/When I put out 32bit builds for 0.96.1, sure.

Quote
2. Will an option in Settings to define an explicit Armory data directory location be included in the next release? There is already such option to point Armory to an explicit Bitcoin Core data directory so providing one for the Armory data directory as well would be very helpful...and makes sense. At this point, one still has to do some CLI arg gymnastics to effectuate such a setting. It's not fun and quite stressful for us who suffer from CLI phobia especially in Linux (Mint) wherein I still have to edit the executable with "sudo vi /usr/share/applications/armory.desktop" (credit to Carlton Banks for the instruction/guide) which I currently couldn't get it to work anymore. I guess I am requesting such a feature.

The datadir is where your wallets and setting/log files go.The blockchain and db folder have their own independant cli arg. If your goal is manage space allocation, you can avoid the CLI magic by putting your custom dbdir and satoshi-datadir folders in armoryqt.conf (this is a new thing in 0.96):

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L111


Title: Re: Armory 0.96 is out
Post by: visdude on June 26, 2017, 06:52:39 AM
1. I still have 0.92.3 as my cold/offline wallet on a Windows 7 32-bit machine. Can I simply just install 0.96 (or future releases from here on for that matter) over 0.92.3 to update and bring it up to speed?

If/When I put out 32bit builds for 0.96.1, sure.

Quote
2. Will an option in Settings to define an explicit Armory data directory location be included in the next release? There is already such option to point Armory to an explicit Bitcoin Core data directory so providing one for the Armory data directory as well would be very helpful...and makes sense. At this point, one still has to do some CLI arg gymnastics to effectuate such a setting. It's not fun and quite stressful for us who suffer from CLI phobia especially in Linux (Mint) wherein I still have to edit the executable with "sudo vi /usr/share/applications/armory.desktop" (credit to Carlton Banks for the instruction/guide) which I currently couldn't get it to work anymore. I guess I am requesting such a feature.

The datadir is where your wallets and setting/log files go.The blockchain and db folder have their own independant cli arg. If your goal is manage space allocation, you can avoid the CLI magic by putting your custom dbdir and satoshi-datadir folders in armoryqt.conf (this is a new thing in 0.96):

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L111

1. Otherwise, 0.96 is good to use as a cold/offline wallet on a 64-bit machine then?

2. Such procedure is even more complicated than it already is. I don't even know where to look for those config files to begin with let alone tinkering with them involving more command line arguments which I am trying to avoid in the first place. I'm just thinking that since Armory has a GUI, why not incorporate such a feature in it. There's already one for specifying an explicit Bitcoin Core data directory location in Settings, so why not for Armory's too? I thought that's what GUIs are for -- to make things easy and simple so that even gramps can do it without screwing up. It would be a foolproof method for regular Joes like me. Not everyone involved in cryptos is an astute techie; and I'm a fine example of that.

BTW, on a W7 x64 machine running 0.96 with explicit Armory data directory using a shortcut arg (--satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"), the "databases" folder, wallets, settings and log files are together in the "Armory" folder and ths setup has been working for a while now through several updates. So your explanation above about the "datadir" being separate from "blockchain and db folder" has confused the heck out of me even further.

If it's too complicated to include such a feature in GUI (for us regular folks) such that it would jeopardize the existing working code and possibly break it, then forget I mentioned it. But thanks just the same for your time replying to my query.



Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 07:05:14 AM
1. Otherwise, 0.96 is good to use as a cold/offline wallet on a 64-bit machine then?

Yes

Quote
2. Such procedure is even more complicated than it already is. I don't even know where to look for those config files to begin with let alone tinkering with them involving more command line arguments which I am trying to avoid in the first place. I'm just thinking that since Armory has a GUI, why not incorporate such a feature in it. There's already one for specifying an explicit Bitcoin Core data directory location in Settings, so why not for Armory's too? I thought that's what GUIs are for -- to make things easy and simple so that even gramps can do it without screwing up. It would be a foolproof method for regular Joes like me. Not everyone involved in cryptos is an astute techie; and I'm a fine example of that.

BTW, on a W7 x64 machine running 0.96 with explicit Armory data directory using a shortcut arg (--satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"), the "databases" folder, wallets, settings and log files are together in the "Armory" folder and ths setup has been working for a while now through several updates. So your explanation above about the "datadir" being separate from "blockchain and db folder" has confused the heck out of me even further.

https://btcarmory.com/docs/pathing

I wrote a tutorial explaining what paths Armory uses and how to set them up in the config files. This is simpler than you are imagining it.

Quote
If it's too complicated to include such a feature in GUI (for us regular folks) such that it would jeopardize the existing working code and possibly break it, then forget I mentioned it. But thanks just the same for your time replying to my query.

GUI development is very time consuming, and GUI features such as pathing end up conflicting with the existing code which was never written with the intent to allow for modularity. On top of that, it is all in Python, which is particularly indisposed to the maintenance of expensive GUI code, so all in all, I put in the config setup cause it's the solution down the middle. When I have time and the appetite for it, I improve UX where I can. I do not often have that appetite.

TLDR: technical debt.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 08:48:22 AM
Hello everyone,

First gratz for the developers for another Armory release.

I'm writting to ask for some help here since it's the 1st time I'm attempting to use it (as it was highly recomendated). The issue here is that I'm stuck into preparing databases for ages and, a bit bored, of waiting for the spiining wheel to end (which looks that it never will).

My system runs in Windows 10 x64 and seems to be unable to sync with BTC network.

Please help.

Running as Admin with

"F:\Utils\Crypto Miners\Armory\ArmoryQt.exe" --datadir="F:\Utils\Crypto\Armory" --satoshi-datadir="F:\Utils\Crypto\Bitcoin"

armorycpplog
Code:
Log file opened at 1498466465: F:\Utils\Crypto\Armory\armorycpplog.txt
-ERROR - 1498466477: (..\SocketObject.cpp:440) POLLERR error in readAndWrite

armorylog
Code:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1255 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1256 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1257 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: F:\Crypto Miners\Armory\ArmoryQt.exe --datadir=F:\Utils\Crypto\Armory --satoshi-datadir=F:\Utils\Crypto\Bitcoin
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1262 -    Armory Version        : 0.96
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1263 -    Armory Build:         : a3d01aa722
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1264 -    PyBtcWallet  Version  : 1.35
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1266 -    OS Variant            : 8-6.2.9200--Multiprocessor Free
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1267 -    User home-directory   : C:\Users\Joao Rocha\AppData\Roaming
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1268 -    Satoshi BTC directory : F:\Utils\Crypto\Bitcoin
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1269 -    Armory home dir       : F:\Utils\Crypto\Armory
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs    :
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1271 -    Total Available RAM   : 15.87 GB
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1272 -    CPU ID string         : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1273 -    Number of CPU cores   : 8 cores
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1274 -    System is 64-bit      : True
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1275 -    Preferred Encoding    : cp1252
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1276 -    Machine Arch          : amd64
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1277 -    Available HDD (ARM)   : 439 GB
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1278 -    Available HDD (BTC)   : 439 GB
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1279 -
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     thread_count    : -1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rescan          : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     ignoreAllZC     : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rescanBalance   : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     disableModules  : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     port            : None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     interport       : 8223
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     coverageOutputDir: None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     forceWalletCheck: False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     regtest         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rebuild         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     nettimeout      : 2
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     datadir         : F:\Utils\Crypto\Armory
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     clearMempool    : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     offline         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     armoryDBDir     : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_port   : 9001
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiPort     : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     useTorSettings  : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     netlog          : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     keypool         : 100
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     coverageInclude : None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     forceOnline     : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     redownload      : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rpcBindAddr     : 127.0.0.1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_ip     : 127.0.0.1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     multisigFile    : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     ram_usage       : -1
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     mtdebug         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     logDisable      : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     settingsPath    : F:\Utils\Crypto\Armory\ArmorySettings.txt
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     language        : en
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     db_type         : DB_FULL
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     doDebug         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     enableDetSign   : True
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     disableConfPermis: False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     testnet         : False
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     rpcport         : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiHome     : F:\Utils\Crypto\Bitcoin
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiRpcport  : DEFAULT
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     logFile         : F:\Utils\Crypto\Armory\ArmoryQt.exe.log.txt
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1285 -     verbosity       : None
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: F:\Utils\Crypto\Armory\ArmorySettings.txt
2017-06-26 09:41 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-06-26 09:41 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-06-26 09:41 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.  
2017-06-26 09:41 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-06-26 09:41 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-06-26 09:41 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: F:\Utils\Crypto\Armory\ArmorySettings.txt
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 3
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2172 -    Wallet (24htVgvZM):   "Family Wallet                   "   (Encrypted)
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2172 -    Wallet (6k1eP47y):    "Venture BTC                     "   (Encrypted)
2017-06-26 09:41 (INFO) -- ArmoryQt.py:2172 -    Wallet (2E5wFWu5Z):   "Personal Wallet                 "   (Encrypted)
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user.  Done!
2017-06-26 09:41 (INFO) -- ArmoryQt.py:558 - Usermode: Advanced
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1682 -    From: Advanced
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1690 -      To: Advanced
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-06-26 09:41 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: F:\Crypto Miners\Armory
2017-06-26 09:41 (ERROR) -- ArmoryQt.py:1840 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1835, in startBitcoindIfNecessary
  File "SDM.pyc", line 188, in setupSDM
BitcoindError: bitcoind not found
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 0
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-06-26 09:41 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="F:\Utils\Crypto\Bitcoin\blocks" --datadir="F:\Utils\Crypto\Armory" --dbdir="F:\Utils\Crypto\Armory\databases"
2017-06-26 09:41 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="F:\\Utils\\Crypto\\Bitcoin\\blocks"', u'--datadir="F:\\Utils\\Crypto\\Armory"', u'--dbdir="F:\\Utils\\Crypto\\Armory\\databases"']
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-06-26 09:41 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-06-26 09:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-06-26 09:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode

Code:
Log file opened at 1498466472: F:\Utils\Crypto\Armory/dbLog.txt
-INFO  - 1498466472: (..\main.cpp:23) Running on 8 threads
-INFO  - 1498466472: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1498466472: (..\BlockUtils.cpp:907) blkfile dir: F:\Utils\Crypto\Bitcoin\blocks
-INFO  - 1498466472: (..\BlockUtils.cpp:908) lmdb dir: F:\Utils\Crypto\Armory\databases
-INFO  - 1498466472: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1498466474: (..\BDM_Server.cpp:996) registered bdv: 5c3bc8b519cfc5ff0d90
-INFO  - 1498466475: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1498466475: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-DEBUG - 1498466475: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1498466475: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.003s
-INFO  - 1498466475: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO  - 1498466475: (..\BDM_supportClasses.cpp:366) Starting address registration process
-ERROR - 1498466475: (..\lmdb_wrapper.cpp:1435) Headers DB has no block at height: 0
-ERROR - 1498466475: (..\lmdb_wrapper.cpp:1415) No headers at height 0


ArmorySettings
Code:
ManageSatoshi                        | True
LastDirectory                        | F:\Utils\Crypto\Armory
Agreed_to_EULA                       | True
UseTorSettings                       | False
DNAA_UnlockTimeout                   | False
First_Load_Date                      | 1498466466
NotifyIgnore                         |
DNAA_IntroDialog                     | False
AdvFeature_UseCt                     | 0
UnlockTimeout                        | 10
Wallet_6k1eP47y_LedgerShow           | True
FailedLoadCount                      | 1
User_Mode                            | Advanced
SkipOnlineCheck                      | False
MinimizeOnOpen                       | False
First_Load                           | False
Wallet_2E5wFWu5Z_LedgerShow          | True
LastFilterState                      | 0
Wallet_24htVgvZM_LedgerShow          | True
IgnoreAlerts                         |
DNAA_DeleteLevelDB                   | False
Load_Count                           | 1
LastVersionLoad                      | v0.96


Title: Re: Armory 0.96 is out
Post by: naska21 on June 26, 2017, 09:04:20 AM
Hello everyone,

First gratz for the developers for another Armory release.

I'm writting to ask for some help here since it's the 1st time I'm attempting to use it (as it was highly recomendated). The issue here is that I'm stuck into preparing databases for ages and, a bit bored, of waiting for the spiining wheel to end (which looks that it never will).







I had such issue a few days ago. The system has changed F:/ to H:/ somehow so there was no connectivity to DB. When I put the correct letter  for drive, closed mannualy ArmoryDB.exe via Task Manager and lanched Armory again everything went smoothly


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 09:07:01 AM
Hello everyone,

First gratz for the developers for another Armory release.

I'm writting to ask for some help here since it's the 1st time I'm attempting to use it (as it was highly recomendated). The issue here is that I'm stuck into preparing databases for ages and, a bit bored, of waiting for the spiining wheel to end (which looks that it never will).


I had such issue a few days ago. The system has changed F:/ to H:/ somehow so there was no connectivity to DB. When I put the correct letter  for drive, closed mannualy ArmoryDB.exe via Task Manager and lanched Armory again everything went smoothly

Hi Thanks for the reply. I do believe it's not such matter since it's a brand new install and I'm running the script with the correct letter (F).

"F:\Utils\Crypto Miners\Armory\ArmoryQt.exe" --datadir="F:\Utils\Crypto\Armory" --satoshi-datadir="F:\Utils\Crypto\Bitcoin"

I've even tried to change directories and it returns "cannot spawn db". Is there a way to solve that as well? :/


Title: Re: Armory 0.96 is out
Post by: naska21 on June 26, 2017, 09:17:05 AM
Hello everyone,

First gratz for the developers for another Armory release.

I'm writting to ask for some help here since it's the 1st time I'm attempting to use it (as it was highly recomendated). The issue here is that I'm stuck into preparing databases for ages and, a bit bored, of waiting for the spiining wheel to end (which looks that it never will).


I had such issue a few days ago. The system has changed F:/ to H:/ somehow so there was no connectivity to DB. When I put the correct letter  for drive, closed mannualy ArmoryDB.exe via Task Manager and lanched Armory again everything went smoothly

Hi Thanks for the reply. I do believe it's not such matter since it's a brand new install and I'm running the script with the correct letter (F).

"F:\Utils\Crypto Miners\Armory\ArmoryQt.exe" --datadir="F:\Utils\Crypto\Armory" --satoshi-datadir="F:\Utils\Crypto\Bitcoin"

I've even tried to change directories and it returns "cannot spawn db". Is there a way to solve that as well? :/

Look at Task Manager if Bitcoinqt.exe is running. If not try to close Armory and all related processes via Task manager (especially ArmoryDB.exe) and launch Armory again. Bitcoinqt.exe must be running when Armory builts DB


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 09:25:49 AM
Quote
Bitcoinqt.exe must be running when Armory builts DB

This is not a prerequisite to bootstrap the DB since 0.95. As a matter of fact, turning off your node while bootstrapping is a good way ease things up on slow PCs.

Quote
Hi Thanks for the reply. I do believe it's not such matter since it's a brand new install and I'm running the script with the correct letter (F).

"F:\Utils\Crypto Miners\Armory\ArmoryQt.exe" --datadir="F:\Utils\Crypto\Armory" --satoshi-datadir="F:\Utils\Crypto\Bitcoin"

I've even tried to change directories and it returns "cannot spawn db". Is there a way to solve that as well? :/

Post your logs, use pastebin.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 09:27:45 AM
It's not running since it says it cant spawn the db..

Changed a few things to test this out.

Running Program with shortcut target:

F:\Crypto\Armory\ArmoryQt.exe --datadir="F:\Crypto\Armory\user" --satoshi-datadir="F:\Crypto\Armory\core"

When I run, it replies, Armory faield to Spawn the DB! Continues in offline, and all this because I dont have space into C drive.


https://pastebin.com/GgBFjXD4

https://pastebin.com/TkJEKYz6

https://pastebin.com/sbS2G6ET

Why's this invalid data path?!


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 09:33:55 AM
Code:
BadPath: Invalid blockdata path

It means the the satoshi-datadir either does no exists or your user does not have read access to that folder.

At any rate, consider updating to this:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 09:41:19 AM
Updated for the version you suggested and it's now loading properly (without that db spawn error).

Used this command:
F:\Crypto\Armory\ArmoryQt.exe --datadir="F:\Crypto\Armory\user" --satoshi-datadir="F:\Crypto\Armory\core"

dbLog:
Log file opened at 10:37:20.000: F:\Crypto\Armory\user/dbLog.txt
-INFO  - 10:37:20.000: (..\main.cpp:29) Running on 8 threads
-INFO  - 10:37:20.000: (..\main.cpp:30) Ram usage level: 4
-INFO  - 10:37:20.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:248) Listening on port 9001

armoryLog
2017-06-26 10:37:18 (ERROR) -- ArmoryQt.py:1846 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1841, in startBitcoindIfNecessary
  File "SDM.pyc", line 188, in setupSDM
BitcoindError: bitcoind not found
2017-06-26 10:37:18 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 0
2017-06-26 10:37:20 (INFO) -- ArmoryQt.py:1856 - setSatoshiPaths
2017-06-26 10:37:20 (WARNING) -- SDM.pyc:395 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --datadir="F:\Crypto\Armory\user" --dbdir="F:\Crypto\Armory\user\databases"
2017-06-26 10:37:20 (INFO) -- ArmoryUtils.pyc:664 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', '--datadir="F:\\Crypto\\Armory\\user"', u'--dbdir="F:\\Crypto\\Armory\\user\\databases"']
2017-06-26 10:37:21 (INFO) -- ArmoryQt.py:1808 - Connecting on port 9001
2017-06-26 10:37:21 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 1
2017-06-26 10:37:21 (ERROR) -- BDM.pyc:200 - DB error: C:\Users\me\AppData\Roaming/Bitcoin/blocks is not a valid path

How can I change that last path to another drive? I believe that's the error, no?

Also, how do I keep track of that progress into the filesystem?

Thanks.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 09:44:48 AM
Quote
u'--dbdir="F:\\Crypto\\Armory\\user\\databases"'

Somehow the path is in unicode, for whatever reason. I have no idea why, first time I see this. Maybe your local is doing weird things to the path?

Read this tutorial and set your paths in the config files instead of the shortcut target:

https://btcarmory.com/docs/pathing



Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 09:48:09 AM
It opened well now using this command line.

Code:
F:\Crypto\Armory\ArmoryQt.exe --datadir="F:\Crypto\Armory\user" --satoshi-datadir="F:\Crypto\Armory\core" --dbdir="F:\Crypto\Armory\user\databases"

That's now preparing the DB. How can I know it's actually doing this in order to avoid waiting without it being doing nothing. Thanks.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 09:55:06 AM
It seems it's not :(

2017-06-26 10:54:01 (ERROR) -- BDM.pyc:200 - DB error: C:\Users\me\AppData\Roaming/Bitcoin/blocks is not a valid path

I'm starting the software with the link in the previous reply :(


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 09:57:27 AM
Quote
--satoshi-datadir="F:\Crypto\Armory\core"

This should be --satoshi-datadir="F:\Crypto\Armory\core\blocks" btw, assuming Core gets F:\Crypto\Armory\core\ as its datadir.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 10:01:33 AM
Quote
--satoshi-datadir="F:\Crypto\Armory\core"

This should be --satoshi-datadir="F:\Crypto\Armory\core\blocks" btw, assuming Core gets F:\Crypto\Armory\core\ as its datadir.

I had fixed that as well but problem persists.

Shortcut Link: F:\Crypto\Armory\ArmoryQt.exe --datadir="F:\Crypto\Armory\user" --satoshi-datadir="F:\Crypto\Armory\core\blocks" --dbdir="F:\Crypto\Armory\user\databases"

2017-06-26 10:59:05 (ERROR) -- ArmoryQt.py:1846 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 1841, in startBitcoindIfNecessary
  File "SDM.pyc", line 188, in setupSDM
BitcoindError: bitcoind not found
2017-06-26 10:59:05 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 0
2017-06-26 10:59:05 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 1
2017-06-26 10:59:05 (ERROR) -- BDM.pyc:200 - DB error: C:\Users\Joao Rocha\AppData\Roaming/Bitcoin/blocks is not a valid path
2017-06-26 10:59:05 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 0
2017-06-26 10:59:05 (INFO) -- ArmoryQt.py:1890 - loadBlockchainIfNecessary
2017-06-26 10:59:05 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-26 10:59:05 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode

 ??? ???


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 10:08:34 AM
Then just start the DB on its own. From the command prompt:

Code:
cd F:\Crypto\Armory\
ArmoryDB.exe --datadir="F:\Crypto\Armory\user" --satoshi-datadir="F:\Crypto\Armory\core\blocks"

You can start the client after the DB is spawned.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 10:14:13 AM
F:\Crypto\Armory>ArmoryDB.exe --datadir="F:\Crypto\Armory\user" --satoshi-datadir="F:\Crypto\Armory\core\blocks"
logging in F:\Crypto\Armory\user/dbLog.txt
-INFO  - 11:12:31.000: (..\main.cpp:29) Running on 8 threads
-INFO  - 11:12:31.000: (..\main.cpp:30) Ram usage level: 4
-INFO  - 11:12:31.000: (..\BlockUtils.cpp:907) blkfile dir: F:\Crypto\Armory\core\blocks
-INFO  - 11:12:31.000: (..\BlockUtils.cpp:908) lmdb dir: F:\Crypto\Armory\user/databases
-INFO  - 11:12:31.000: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 11:12:31.016: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:248) Listening on port 9001
-INFO  - 11:12:34.016: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 11:12:34.016: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 11:12:34.031: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 11:12:34.031: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 11:12:34.031: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-DEBUG - 11:12:34.031: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 11:12:34.031: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.003s
-INFO  - 11:12:34.031: (..\BDM_supportClasses.cpp:1841) Enabling zero-conf tracking

user/databases has 84KB files.
core/blocks/ remains empty.


Now let it sit for a while? It says something so I know when to open Armory?

Thanks a lot!


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 10:28:31 AM
This is off, it's not finding any block data. Double check your paths and make sure your user has read access to the satoshi-datadir.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 10:34:08 AM
This is off, it's not finding any block data. Double check your paths and make sure your user has read access to the satoshi-datadir.

Using running cmd with admin rights. This is just odd.

Ran Armory Software and this came out

http://puu.sh/wuBCd/41f6f5a266.png


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 10:39:17 AM
Ran Armory Software and this came out

http://puu.sh/wuBCd/41f6f5a266.png

False positive, ignore it.

Quote
core/blocks/ remains empty.

Wait what? You're supposed to download the chain there before running Armory.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 26, 2017, 10:43:03 AM
Ran Armory Software and this came out

http://puu.sh/wuBCd/41f6f5a266.png

False positive, ignore it.

Quote
core/blocks/ remains empty.

Wait what? You're supposed to download the chain there before running Armory.

That's my error then :)

Downloading @ https://bitcoin.org/bin/bitcoin-core-0.14.0/ and https://bitcoin.org/bin/block-chain/


Title: Re: Armory 0.96 is out
Post by: Brangdon on June 26, 2017, 11:14:05 AM
(469262 blocks)

You're trailing over 1000 blocks.
How do I change that? BitcoinQT says it is up to date, and Armory says it is connected, but the blocks number doesn't change. A recent log is here: https://pastebin.com/y4RHwDLZ. It has "blkfile dir: D:\Users\Admin\AppData\Roaming\Bitcoin\blocks", which is what I have set Bitcoin-qt.exe to use, and when I go to that folder I can see files with recent timestamps, so I think Armory is using the same folder as Bitcoin.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 26, 2017, 11:33:28 AM
Delete this folder and rebuild the DB from scratch:

D:\Users\Admin\AppData\Roaming\Armory\databases


Title: Re: Armory 0.96 is out
Post by: Brangdon on June 26, 2017, 01:03:17 PM
Thanks, that worked.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 27, 2017, 06:40:01 AM
@goatpig: It seems Armory got online after download the core :). One final question about the wallet, I've created the wallet before have done all this and sent some BTC into it which, according to the blockchain was transfered correctly (https://live.blockcypher.com/btc/tx/51d076069272807494c625af601db21a2fb698069a1579d8e5642bab9db1a35e/). Now, after the backup restore, the sum isnt showing up. Any ideas? Thanks.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 27, 2017, 06:43:37 AM
Post your logs.


Title: Re: Armory 0.96 is out
Post by: goldstrk on June 27, 2017, 07:45:31 AM
Post your logs.

ArmoryLog
https://pastebin.com/0a46hhbp

dbLog
https://pastebin.com/6U696KGN


I've also rechecked if the address where I sent the amount was correct, in Armory, and it was.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 27, 2017, 08:22:33 AM
Quote
-INFO  - 08:24:05.281: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 08:24:05.578: (..\DatabaseBuilder.cpp:268) parsed block file #0
-DEBUG - 08:24:05.578: (..\Blockchain.cpp:242) Organizing chain

Your block data folder has very little data in it, basically nothing.

Quote
ArmorySettings
https://pastebin.com/yEduLeEP

The settings file is not a log.


Title: Re: Armory 0.96 is out
Post by: Tim R on June 27, 2017, 03:13:50 PM
You can try to build the testing branch if you want to use the fix right now. Otherwise, sometimes this weekend.
goatpig: Is there a link to the testing branch fix for the stuck unconfirmed balance?


Title: Re: Armory 0.96 is out
Post by: truebits on June 28, 2017, 12:56:56 PM
I upgraded to Armory .96 and now my Armory wallet never goes "online". it always says "offline"

I uploaded Bitcoin core (.14) and sync'd it as well. I tried opening Bitcoin core and still nothing?

Ideas?
 


Title: Re: Armory 0.96 is out
Post by: Casimir1904 on June 28, 2017, 02:34:43 PM
I upgraded to Armory .96 and now my Armory wallet never goes "online". it always says "offline"

I uploaded Bitcoin core (.14) and sync'd it as well. I tried opening Bitcoin core and still nothing?

Ideas?
 

Without logs no one could help you.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 28, 2017, 03:30:28 PM
You can try to build the testing branch if you want to use the fix right now. Otherwise, sometimes this weekend.
goatpig: Is there a link to the testing branch fix for the stuck unconfirmed balance?

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing


Title: Re: Armory 0.96 is out
Post by: Tim R on June 29, 2017, 02:40:42 AM
goatpig:  I installed the the testing branch from the link with Armory closed. Reopened as admin. Once at Parsing Tx Hashes, no progress after hours. Deleted the mempool.dat. Restarted PC. Opened Armory as admin. It quickly Initialized Bitcoin Engine and Build Databases. Parsing Tx Hashes has gone for hours again with no progress. Not sure if it is of significance but the cmd window no longer displays during this process. No window popping up showing Bitcoin Core not connected, so think it is. Thoughts? Thank you.


Title: Re: Armory 0.96 is out
Post by: goatpig on June 29, 2017, 03:31:25 AM
Without logs no one could help you.


Title: Re: Armory 0.96 is out
Post by: rains on June 29, 2017, 10:02:38 AM
I have updated to the new Armory wallet. But need some help. Goatpig, I have sent you a pm. could you please help thanks


Title: Re: Armory 0.96 is out
Post by: Tim R on June 29, 2017, 03:04:50 PM
Update: Finally got it all to load. All of balance still unconfirmed. https://pastebin.com/CjgS6HJM
Much appreciated.


Title: Re: Armory 0.96 is out
Post by: Casimir1904 on June 29, 2017, 03:51:21 PM
Update: Finally got it all to load. All of balance still unconfirmed. https://pastebin.com/CjgS6HJM
Much appreciated.

Code:
scanning new blocks from #471213 to #471212

Current block height = 473392


Title: Re: Armory 0.96 is out
Post by: Tim R on June 29, 2017, 05:27:18 PM
I checked and Bitcoin Core is running in the background, which I thought meant it would keep the block height current. Is there a specific sequence to force it to the full block height - thought that happened automatically with Armory left running and Bitcoin Core referenced in the background. Just tried closing Armory and opened Bitcoin Core and it is full synched. Then opened Armory and it is stuck at "Loading 100%".


Title: Re: Armory 0.96 is out
Post by: Tim R on June 29, 2017, 05:50:25 PM
No progress so closed both Armory and Bitcoin Core and restarted only Armory as usual with Bitcoin Core called up to run in the background. Will see if I get full block height this time when done - unless you or goatpig offer a alternate thought in the interim. If still not to full block height when done I will post logs in pastebin link again. Thanks.


Title: Re: Armory 0.96 is out
Post by: Tim R on June 30, 2017, 03:02:16 AM
goatpig:  Still no progress for Armory 0.96.0.3 Parsing Tx Hashes after hours. When I can get Armory fully loaded the block height was still lower than current so balance was unconfirmed. Have tried various methods to try to get Armory to load full block hoping the balance would get confirmed with 0.96.0.3 loaded. Latest pastebin error log https://pastebin.com/7j7su0Au


Title: Re: Armory 0.96 is out
Post by: goatpig on June 30, 2017, 03:54:50 AM
You want to build the current state of testing, has a fix for this.


Title: Re: Armory 0.96 is out
Post by: truebits on July 03, 2017, 01:53:02 AM
I upgraded to Armory .96 and now my Armory wallet never goes "online". it always says "offline"

I uploaded Bitcoin core (.14) and sync'd it as well. I tried opening Bitcoin core and still nothing?

Ideas?
 

Without logs no one could help you.

Ok, fair enough how do I retrieve my log? (i am a complete newbie to this).



Title: Re: Armory 0.96 is out
Post by: naska21 on July 03, 2017, 07:36:21 AM
I upgraded to Armory .96 and now my Armory wallet never goes "online". it always says "offline"

I uploaded Bitcoin core (.14) and sync'd it as well. I tried opening Bitcoin core and still nothing?

Ideas?
 

Without logs no one could help you.

Ok, fair enough how do I retrieve my log? (i am a complete newbie to this).



look at C:/Users/your_user_name/AppData/Roaming/Armory   folder. It is over there. Use pastebin online service to present log content here


Title: Re: Armory 0.96 is out
Post by: Muhammed Zakir on July 03, 2017, 07:44:00 AM
I upgraded to Armory .96 and now my Armory wallet never goes "online". it always says "offline"

I uploaded Bitcoin core (.14) and sync'd it as well. I tried opening Bitcoin core and still nothing?

Ideas?
 

Without logs no one could help you.

Ok, fair enough how do I retrieve my log? (i am a complete newbie to this).



look at C:/Users/your_user_name/AppData/Roaming/Armory   folder. It is over there. Use pastebin online service to present log content here

Alternative: Open Armory, click 'File' -> 'Export Log File'.

* it is still there, right?


Title: Re: Armory 0.96 is out
Post by: goatpig on July 03, 2017, 08:28:18 AM
* it is still there, right?

It's still there, but posting the individual files is better, as the export option, while more accessible to the user, compounds both client and db logs together which makes it a bit harder on those who read through it. More often than not, only one of the logs is actually relevant to a given issue.


Title: Re: Armory 0.96 is out
Post by: Tim R on July 10, 2017, 05:40:31 PM
You want to build the current state of testing, has a fix for this.
goatpig: Installed latest test build #4 and all worked great and balance all confirmed. Test transaction pending and should be good. Thanks for your assistance!


Title: Re: Armory 0.96 is out
Post by: visdude on July 11, 2017, 12:32:07 AM
I tried installing "armory_0.96-gcc5.4_amd64.deb" as an offline wallet but it required downloading a couple of files. Obviously, I am not about to compromise my offline machine by exposing it to the interweb just to download said files. Will the next release be self-contained (i.e. not requiring to go online to download some files in order to complete its installation)?



Title: Re: Armory 0.96 is out
Post by: visdude on July 11, 2017, 05:49:48 AM

https://btcarmory.com/docs/pathing

I wrote a tutorial explaining what paths Armory uses and how to set them up in the config files. This is simpler than you are imagining it.


Thank you for this thorough tutorial. It helped a lot.



Title: Re: Armory 0.96 is out
Post by: goatpig on July 11, 2017, 09:34:20 AM
I tried installing "armory_0.96-gcc5.4_amd64.deb" as an offline wallet but it required downloading a couple of files. Obviously, I am not about to compromise my offline machine by exposing it to the interweb just to download said files. Will the next release be self-contained (i.e. not requiring to go online to download some files in order to complete its installation)?

I do plan on pushing out an offline package for 0.96.1 if it's what you are referring to.


Title: Re: Armory 0.96 is out
Post by: visdude on July 11, 2017, 10:32:16 AM
I tried installing "armory_0.96-gcc5.4_amd64.deb" as an offline wallet but it required downloading a couple of files. Obviously, I am not about to compromise my offline machine by exposing it to the interweb just to download said files. Will the next release be self-contained (i.e. not requiring to go online to download some files in order to complete its installation)?

I do plan on pushing out an offline package for 0.96.1 if it's what you are referring to.

I suppose so. Thanks.



Title: Re: Armory 0.96 is out
Post by: alomar on July 22, 2017, 01:34:06 AM
is there any general reason why both 0.95.1 and 0.96 *.deb in VM would both show Connected status bottom right but be stuck at 470751?  everything else appears ok.

getblockcount shows correct height.


Title: Re: Armory 0.96 is out
Post by: RustyRussell on September 26, 2017, 04:43:29 AM
0.96.3 gcc 5.7 ubuntu deb.  Three issues I've found (was on 0.93.3).

- I get a flashed-up-then-gone dialog on startup.  Finally caught it on video, it's "Mirroring Wallets".  Is this something I should be able to click on?

- Bump fee via right-click fails (see error below).  This is my imported vanity addr 1RustyR...

Code:
(ERROR) Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 3409, in showContextMenuLedger
    self.bumpFee(wltID, txHash)
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5913, in bumpFee
    addrComment = wlt.getCommentForAddress(h160)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 1818, in getCommentForAddress
    hashList = self.cppWallet.getScriptHashVectorForIndex(assetIndex)
  File "/usr/lib/armory/CppBlockUtils.py", line 4083, in getScriptHashVectorForIndex
    return _CppBlockUtils.WalletContainer_getScriptHashVectorForIndex(self, arg2)
RuntimeError: invalid asset index

Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 3409, in showContextMenuLedger
    self.bumpFee(wltID, txHash)
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5913, in bumpFee
    addrComment = wlt.getCommentForAddress(h160)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 1818, in getCommentForAddress
    hashList = self.cppWallet.getScriptHashVectorForIndex(assetIndex)
  File "/usr/lib/armory/CppBlockUtils.py", line 4083, in getScriptHashVectorForIndex
    return _CppBlockUtils.WalletContainer_getScriptHashVectorForIndex(self, arg2)
RuntimeError: invalid asset index
- You told a previous user to use the RBF control dialog, hitting that gives this error (and no effect):
Code:
(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ui/WalletFrames.py", line 289, in doRBF
    RBFDlg(self, self.main, wlt)
  File "/usr/lib/armory/ui/CoinControlUI.py", line 140, in __init__
    self.rbfTreeModel = RBFTreeModel(self, wlt)
  File "/usr/lib/armory/ui/TreeViewGUI.py", line 998, in __init__
    self.treeStruct = TreeStructure_RBF(self.wlt)
  File "/usr/lib/armory/ui/TreeViewGUI.py", line 708, in __init__
    self.setup()
  File "/usr/lib/armory/ui/TreeViewGUI.py", line 714, in setup
    rbfList = self.wallet.getRBFTxOutList()
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 59, in inner
    return func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 512, in getRBFTxOutList
    utxos = self.cppWallet.getRBFTxOutList()
  File "/usr/lib/armory/CppBlockUtils.py", line 4005, in getRBFTxOutList
    return _CppBlockUtils.WalletContainer_getRBFTxOutList(self)
DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7fafaba49600> >

Traceback (most recent call last):
  File "/usr/lib/armory/ui/WalletFrames.py", line 289, in doRBF
    RBFDlg(self, self.main, wlt)     
  File "/usr/lib/armory/ui/CoinControlUI.py", line 140, in __init__
    self.rbfTreeModel = RBFTreeModel(self, wlt)
  File "/usr/lib/armory/ui/TreeViewGUI.py", line 998, in __init__
    self.treeStruct = TreeStructure_RBF(self.wlt)
  File "/usr/lib/armory/ui/TreeViewGUI.py", line 708, in __init__
    self.setup()
  File "/usr/lib/armory/ui/TreeViewGUI.py", line 714, in setup
    rbfList = self.wallet.getRBFTxOutList()
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 59, in inner
    return func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 512, in getRBFTxOutList
    utxos = self.cppWallet.getRBFTxOutList()
  File "/usr/lib/armory/CppBlockUtils.py", line 4005, in getRBFTxOutList
    return _CppBlockUtils.WalletContainer_getRBFTxOutList(self)
<class 'CppBlockUtils.DbErrorMsg'>: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7fafaba49600> >
Hope that helps track something!  Meanwhile I'll wait for my 2sat/byte TX :)

Thanks!
Rusty.


Title: Re: Armory 0.96 is out
Post by: goatpig on September 26, 2017, 05:14:10 AM
- I get a flashed-up-then-gone dialog on startup.  Finally caught it on video, it's "Mirroring Wallets".  Is this something I should be able to click on?

To allow for the use of segwit and compressed key in p2sh scripts, I developed a whole new wallet code. This stuff is in C++ and operates as companion code to the python stuff. The goal was to no disrupt the existing, time tested code, while providing new features for those willing to run new code.

This flashing dialog is for the operation the mirrors the python wallet containers into their new, C++ implemented counterparts. These wallets are WO only, as they only need the data necessary to register the scripts with the DB and construct unsigned transactions. And no, there's nothing to click on, it is just there for report progress on the mirroring, and closes on its own. I figured I'd rather let people see something progress than silently mirror wallets, which can take up to a couple minutes on large wallets.

You will see that dialog every run because you use an imported address, and the mirroring code goes through every import each run, since there is no deterministic way to verify the mirrored wallet is still in sync with the python counterpart.

I'm not sure where to take that part of the GUI atm (if letting the dialog flash is ok, or requiring user interaction to close it is gonna piss off people real quick).

Quote
- Bump fee via right-click fails (see error below).  This is my imported vanity addr 1RustyR...

Yep, I borked that when I fixed comments resolution in the main ledger.

Quote
- You told a previous user to use the RBF control dialog, hitting that gives this error (and no effect):

And apparently I borked that too... fml.

Thanks for the reports, will go over that stuff .4


Title: Re: Armory 0.96 is out
Post by: gangtraet on September 26, 2017, 07:23:55 AM
I'm not sure where to take that part of the GUI atm (if letting the dialog flash is ok, or requiring user interaction to close it is gonna piss off people real quick).

It is a common problem: Do you want to display a progress box, if you don't know how long the operation is going to take?  Some programs delay popping up the dialog until a few seconds have passed.  It can still pop up a fraction of a second before it closes, but now it is a lot less likely.

Or you could put a 1-sec delay on closing it.  But please don't require an extra click :)


Title: Re: Armory 0.96 is out
Post by: Legar on November 25, 2017, 03:31:31 PM
Hi,

 I just installed the wallet but can't launch it:

Code:
(ERROR) ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
(ERROR) Traceback (most recent call last):
  File "ArmoryQt.py", line 5929, in <module>
  File "ArmoryQt.py", line 244, in __init__
  File "ArmoryQt.py", line 2190, in loadWalletsAndSettings
  File "ArmoryQt.py", line 2196, in loadCppWallets
UnicodeEncodeError: 'ascii' codec can't encode character u'\xd6' in position 16: ordinal not in range(128)


Title: Re: Armory 0.96 is out
Post by: droark on November 25, 2017, 07:39:26 PM
Hi,

 I just installed the wallet but can't launch it:

Code:
(ERROR) ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
(ERROR) Traceback (most recent call last):
  File "ArmoryQt.py", line 5929, in <module>
  File "ArmoryQt.py", line 244, in __init__
  File "ArmoryQt.py", line 2190, in loadWalletsAndSettings
  File "ArmoryQt.py", line 2196, in loadCppWallets
UnicodeEncodeError: 'ascii' codec can't encode character u'\xd6' in position 16: ordinal not in range(128)

You have a Unicode character (Ö) somewhere in your path. Armory can't handle Unicode. You'll have to make the entire path ASCII-only.


Title: Re: Armory 0.96 is out
Post by: RustyRussell on November 26, 2017, 11:51:54 PM
- I get a flashed-up-then-gone dialog on startup.  Finally caught it on video, it's "Mirroring Wallets".  Is this something I should be able to click on?

To allow for the use of segwit and compressed key in p2sh scripts, I developed a whole new wallet code. This stuff is in C++ and operates as companion code to the python stuff. The goal was to no disrupt the existing, time tested code, while providing new features for those willing to run new code.

This flashing dialog is for the operation the mirrors the python wallet containers into their new, C++ implemented counterparts. These wallets are WO only, as they only need the data necessary to register the scripts with the DB and construct unsigned transactions. And no, there's nothing to click on, it is just there for report progress on the mirroring, and closes on its own. I figured I'd rather let people see something progress than silently mirror wallets, which can take up to a couple minutes on large wallets.

You will see that dialog every run because you use an imported address, and the mirroring code goes through every import each run, since there is no deterministic way to verify the mirrored wallet is still in sync with the python counterpart.

I'm not sure where to take that part of the GUI atm (if letting the dialog flash is ok, or requiring user interaction to close it is gonna piss off people real quick).

Quote
- Bump fee via right-click fails (see error below).  This is my imported vanity addr 1RustyR...

Yep, I borked that when I fixed comments resolution in the main ledger.

Quote
- You told a previous user to use the RBF control dialog, hitting that gives this error (and no effect):

And apparently I borked that too... fml.

Thanks for the reports, will go over that stuff .4

Well, my tx didn't need bumping in the end.  But Armory (0.96.3) seems can't detect its own txs; I think I'm going to run out of outputs soon :)

http://ozlabs.org/~rusty/Screenshot%20from%202017-11-27%2010-15-55.png

Re-importing the wallet didn't help; I was hoping there was a way to invoke rescanning?  And trying to do a Wallet Consistency check gave a backtrace and an empty
Perform Wallet Consistency Check with both buttons greyed out:
(ERROR) ArmoryUtils.py:3192 - Error in pybkgdthread: 'unicode' object has no attribute 'walletPath'
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3190, in run
    self.output = self.func()
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3127, in funcPartial
    return thefunc(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1848, in ParseWallet
    Progress=Progress)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc
    return func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1695, in FixWallet
    frt = fixer.ProcessWallet(wltPath, wlt, Passphrase, mode, Progress=Progress)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc
    return func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 400, in ProcessWallet
    WalletPath = Wallet.walletPath
AttributeError: 'unicode' object has no attribute 'walletPath'


Thanks!
Rusty.


Title: Re: Armory 0.96 is out
Post by: goatpig on November 27, 2017, 12:12:43 AM
Quote
Well, my tx didn't need bumping in the end.  But Armory (0.96.3) seems can't detect its own txs; I think I'm going to run out of outputs soon

I fixed all of the known RBF issues just an hour ago. The fixes are in the testing branch if you'd like to try them out, otherwise I'll put out a new RC once I have the BTG signer done.

Quote
Re-importing the wallet didn't help; I was hoping there was a way to invoke rescanning?

That won't trigger rescans anymore, as the DB keeps track of all addresses it sees now. You can flag the DB for a rescan from the help menu. Any rescan or rebuild action won't carry over the ZC state, so you'll lose the entries in the ledger.

Quote
And trying to do a Wallet Consistency check gave a backtrace and an empty

I'll look into that.


Title: Re: Armory 0.96 is out
Post by: Gangat on December 13, 2017, 01:12:14 AM
This message is to goatpig.
Recently I installed armory 0.96 on a windows 10 machine.
Unfortunately every time I open it I get the error message  " armory_failed_to_spawn_the_db/ "
And Armory is offline.
Would you be kind enough to tell me how to fix the problem?

Thanking you in advance,

Gangat


Title: Re: Armory 0.96 is out
Post by: goatpig on December 13, 2017, 01:49:41 AM
This message is to goatpig.
Recently I installed armory 0.96 on a windows 10 machine.
Unfortunately every time I open it I get the error message  " armory_failed_to_spawn_the_db/ "
And Armory is offline.
Would you be kind enough to tell me how to fix the problem?

Thanking you in advance,

Gangat


No.


Title: Re: Armory 0.96 is out
Post by: goatpig on December 13, 2017, 01:53:10 AM
j/k

Grab the latest version from the stickies, you're using dated stuff. Also delete your databases folder. If you're still having trouble, make a thread and post your logs.


Title: Re: Armory 0.96 is out
Post by: Gangat on December 13, 2017, 11:53:48 PM
With all due respect sir,

I downloaded armory_0.96_win64.exe  from  https://www.bitcoinarmory.com/download/ .

Why isn't that the latest version?

Where else am I supposed to get it?

Thanks


Title: Re: Armory 0.96 is out
Post by: goatpig on December 14, 2017, 12:19:06 AM
Grab the latest version from the stickies


Title: Re: Armory 0.96 is out
Post by: HCP on December 14, 2017, 02:59:22 AM
I downloaded armory_0.96_win64.exe  from  https://www.bitcoinarmory.com/download/ .
Why isn't that the latest version?
Where else am I supposed to get it?
Because that hasn't been the official download location for a long time now... the original bitcoin armory "company" essentially folded (https://bitcointalk.org/index.php?topic=1351792.0)... goatpig took over development.

The NEW website is: https://btcarmory.com/
The very latest code is available on goatpig's GitHub: https://github.com/goatpig/BitcoinArmory/releases

You should read the "sticky" posts stuck to the top of the board like this one: https://bitcointalk.org/index.php?topic=2227856.0

Unfortunately, for whatever reason, the original Bitcoin Armory people have left their website up and running... :-\ which seems to confuse the hell out of everyone... even more so than Armory itself and it's requirement to have a full Bitcoin Core node running behind it! :P