0.96.1 testing build #4

[paranoidx]

Armory .95 stopped working for me.  Upgraded to .96.1 test 4.
Armory shows scanning transaction history for about 2-3 hours.  It then shows 1 second remaining but never actually loads.
Armory shows it is offline.  I have Bitcoin Core 14.2 running in the background.  It is fully synced.  I am running on Linux Mint 17.

https://pastebin.com/embed_js/Gi6U9k9i

[1715155504]

1715155504

[paranoidx]

Rebuilt and rescanned database, it is now showing my balance and showing that it is connected.
I now get the following error when trying to send a transaction:

"The transaction that you attempted to broadcast hast timed out."
"The RPC interface in your node is disabled..."

[paranoidx]

Okay it seems core wasnt running correctly in the background that 2nd time.  All good now. I was able to send transaction.

[creamers]

oke, will have to wait for the build to test it out.

*EDIT: since I started without the bitcoind and with bitcoin core in the foreground it runs without crashes.

Since build #4 it is running stable again with bitcoind in the background. Thank you for your effort!

[naska21]

Hi, should we upgrade bitcoin-qt to 0.14.2  version to run alongside with the latest 0.96.1 testing build #4, and if YES, will it run smoothly?

[Tmptmpbuggyguy]

Armory 0.96.0.3 is stuck and says "Building databases ... 15 Minutes".

-INFO  - 1499683142: (DatabaseBuilder.cpp:268) parsed block file #248
-INFO  - 1499683160: (DatabaseBuilder.cpp:268) parsed block file #252
-INFO  - 1499683167: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 1499683167: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 1499683167: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

Restarting Armory leads to  "Building databases ... 48 Minutes" (not stuck).

-WARN  - 1499684451: (BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN  - 1499684451: (BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN  - 1499684451: (BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1499684451: (BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1499684468: (BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1499684468: (BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1499684468: (BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1499684468: (BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO  - 1499684482: (DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1499684482: (lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 1499684482: (DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 1499684482: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1499684487: (DatabaseBuilder.cpp:268) parsed block file #1
-INFO  - 1499684488: (DatabaseBuilder.cpp:268) parsed block file #2
-INFO  - 1499684494: (DatabaseBuilder.cpp:268) parsed block file #3

Some time later

(ERROR) ArmoryQt.py:1188 - 3 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1193 - File mempool.bin does not exist. Nothing deleted.

Restarted Armory

-INFO  - 1499691206: (DatabaseBuilder.cpp:268) parsed block file #33
-INFO  - 1499691222: (DatabaseBuilder.cpp:268) parsed block file #34
-INFO  - 1499691223: (DatabaseBuilder.cpp:268) parsed block file #35
-INFO  - 1499691223: (DatabaseBuilder.cpp:268) parsed block file #37
-INFO  - 1499691230: (DatabaseBuilder.cpp:268) parsed block file #38
-INFO  - 1499691233: (DatabaseBuilder.cpp:268) parsed block file #39

I'm able to build the 0.96.0.4 on Mac OS but the final binary lacks of some files as mentioned earlier in this thread and is not starting. I'll try again now.

In the recent time it always takes me several hours to move funds from cold storage :/ (don't have a SSD).

[Tmptmpbuggyguy]

I'm still not able to get a working build of the OS X version > Armory 0.96.0.

can't open file '/Users/user/Desktop/Armory0.9.6.0.4-testing/osxbuild/Armory.app/Contents/MacOS/py/usr/local/lib/armory/ArmoryQt.py':

I followed all suggestions from this thread and also updated the mac os version to 10.8 in the build script. I also tried the git submodule stuff.

The last provided testing build binary works not for me because it uses some CPU instructions that my hardware does not support.

[XCTfluid]

Is there change log for test builds? Just can't find it now. Anyway not big deal, just curious.

[goatpig]

Hi, should we upgrade bitcoin-qt to 0.14.2  version to run alongside with the latest 0.96.1 testing build #4, and if YES, will it run smoothly?

You can update to 0.14.2

I'm still not able to get a working build of the OS X version > Armory 0.96.0.

.

tag 0.96.0.4 is broken on OSX. That's been in testing but testing is broken atm for other reasons, so you'll have to wait.

The last provided testing build binary works not for me because it uses some CPU instructions that my hardware does not support.

That shouldn't not matter, none of these ASM optimizations are enabled on the OSX builds.

Is there change log for test builds? Just can't find it now. Anyway not big deal, just curious.

The changelog in testing, but I have not updated it in a while. Crawl the commit history comments if you want to get an idea.

[Tmptmpbuggyguy]

OK thanks goatpig. Meanwhile I try to get my 0.96 working again.

-DEBUG - 1499774917: (Blockchain.cpp:242) Organizing chain
-INFO  - 1499775031: (DatabaseBuilder.cpp:56) updated HEADERS db in 6514s
-INFO  - 1499775032: (BlockUtils.cpp:1206) Enabling zero-conf tracking

The log is already since some time like this and in "preparing database state". Does it mean armory is still working or should I restart?

Updat I checked the Armory processes with my task manager and ArmoryDB was like idle so I gave a restart a try and now it says building db

The last provided testing build binary works not for me because it uses some CPU instructions that my hardware does not support.

That shouldn't not matter, none of these ASM optimizations are enabled on the OSX builds.

I assumed that cause when I started the 0.96 osx binary it said illegal instruction but building on my own worked fine. Maybe a dependency is using such instructions !?!?

[goatpig]

I assumed that cause when I started the 0.96 osx binary it said illegal instruction but building on my own worked fine. Maybe a dependency is using such instructions !?!?

https://github.com/goatpig/BitcoinArmory/blob/testing/cppForSwig/cryptopp/Makefile.am#L15

That stuff is completely disabled on OSX. This ought to be something else. Building yourself is always preferable at any rate, autotools should make that more accessible.

[gangtraet]

Failed to build on Raspberry Pi

Hi,

I tried to build v0.96.0.4 on a Raspberry Pi (the git tag is v0.96.0.4 not v0.96.0.4-testing as for the other testing releases, right?).

After four hours, compilation fails.  It looks like it is caused by "long long unsigned int" being different from "long unsigned int", see this paste: https://pastebin.com/xckJrHte

Some version numbers:
Autoconf 2.64
Automake 1.14.1
Libtool 2.4.2
gcc/g++ 4.9.2-10
swig 2.0.12
Rasbian 8 (the newest) based on jessie.

[goatpig]

You do not build on RPi. You cross compiled from a Linux machine:

https://github.com/goatpig/BitcoinArmory/blob/master/r-pi/README.md

[gangtraet]

You do not build on RPi. You cross compiled from a Linux machine:

OK, that is undoubtedly faster

I just felt it was better that the RPi spent 8 hours compiling than I spent 4 hours figuring out how to cross compile.  But I will do that now!  Thanks

[gangtraet]

You do not build on RPi. You cross compiled from a Linux machine:

https://github.com/goatpig/BitcoinArmory/blob/master/r-pi/README.md

Unfortunately, that didn't work either.  The configure script complains about No assembler code for CPU arm, and later Make fails because there was not Makefile in cryptopp.

[creamers]

While trying to create a unsigned transaction I notice this:

https://www.screencast.com/t/2hhmT0R9o

Fee rate per node is set to 197 sat/byte and it gave me a warning, so I wanted to change this and set it to Fee/Byte (Satoshi/Byte) and wanted to set it to 200.

Now it seems that it doesnt change as soon as I go above 197 in the Fee/Byte field. (In above movie is recorded)

Is this a bug or why can't I set a higher "Fee/Byte" than the current "Fee Rate per Node" ?

http://i66.tinypic.com/23tgzzl.png

[goatpig]

I don't have Flash installed so I can't watch this video.

[creamers]

You can see it in the picture.....typed 200, but it only says 20.
As soon as I type anything <=197 is shows the correct value, otherwise like in the picture.

*edit I see that it didnt max the spendable amount cause I edited the fee. The button should be pressed automatically again when the fee is changed imo

[goatpig]

You can see it in the picture.....typed 200, but it only says 20.
As soon as I type anything <=197 is shows the correct value, otherwise like in the picture.

*edit I see that it didnt max the spendable amount cause I edited the fee. The button should be pressed automatically again when the fee is changed imo

I've replied to this already. The idea was that I wouldn't have to spend 2 days figuring this out because users could spend the extra second to press the "MAX" button once again, seeing it's a button and not a check box, therefor realizing the semantics indicate the functionality is not biding, and that it has always been this way since the MAX button was introduced.

[Mr.Vice]

Hey goatpig!

I've tested the new build "Armory 0.96.0.4-testing". I'm recalling on the address book issue - BUG #1 - (address selection via "select address" button).
There is also an major issue with Bug #2 (see beneath).
Altough the offline tx file loading bug has now been solved with this version!

------------------------------------------------------------------------------------------------------------------------------------------------
BUG #1

Select Wallet > Send > Open address book > Select address

This button is also still broken (like double-click). Addresses can only be chosen via the address book by right-click copy address and paste it into the address field in the sending dialoge.

armorylog.txt

Code:

2017-07-19 09:31:00 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 8091, in acceptAddrSelection
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 4: ordinal not in range(128)

------------------------------------------------------------------------------------------------------------------------------------------------
BUG #2

Executing ArmoryQt > The first progress bar isn't displayed (ArmoryDB takes a little bit longer to initialize) > Armory has now started ArmoryDB and grabs existing block data > Armory loaded but isn't able to connect to bitcoind

This issue occurs from time to time and the only solution is to restart the PC and then start ArmoryQt again after reboot. But after this I get very often POLLER Errors and "raw blockchain data doesn't match expected block hash" Errors. So I need to to Rebuild & Rescan. I have no AV installed and Windows Defender already has exceptions for every Program associated with Armory and Bitcoin Core. So I have no clue why this happens again.

dbLog.txt (No.1)

Code:

-INFO  - 09:21:45.047: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 09:21:45.219: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:249) Listening on port 52144
-INFO  - 09:21:45.344: (..\BlockUtils.cpp:1092) Executing: doInitialSyncOnLoad
-INFO  - 09:21:45.391: (..\DatabaseBuilder.cpp:190) Reading headers from db
-INFO  - 09:21:48.203: (..\BDM_Server.cpp:1074) registered bdv: 87a75e5d94283b58e55b
-WARN  - 09:23:13.500: (..\Blockchain.cpp:63) block id duplicate: 476093
-INFO  - 09:24:19.188: (..\DatabaseBuilder.cpp:229) Found 475996 headers in db
-INFO  - 09:24:21.438: (..\DatabaseBuilder.cpp:63) Rewinding 100 blocks
-INFO  - 09:24:21.438: (..\DatabaseBuilder.cpp:70) updating HEADERS db
-INFO  - 09:24:28.766: (..\DatabaseBuilder.cpp:272) parsed block file #937
-INFO  - 09:24:29.610: (..\DatabaseBuilder.cpp:272) parsed block file #938
-INFO  - 09:24:30.610: (..\DatabaseBuilder.cpp:482) Found next block after skipping 998205bytes
-INFO  - 09:24:31.500: (..\DatabaseBuilder.cpp:272) parsed block file #939
-INFO  - 09:24:31.500: (..\Blockchain.cpp:246) Organizing chain 
-INFO  - 09:24:31.563: (..\Blockchain.cpp:360) Organized chain in 0.062s
-INFO  - 09:24:31.719: (..\DatabaseBuilder.cpp:75) updated HEADERS db in 10.283s
-INFO  - 09:24:31.719: (..\DatabaseBuilder.cpp:1121) verifying txfilters integrity
-INFO  - 09:26:09.266: (..\DatabaseBuilder.cpp:1205) done checking txfilters
-INFO  - 09:26:09.875: (..\DatabaseBuilder.cpp:127) scanning new blocks from #475996 to #476432
-INFO  - 09:26:11.578: (..\BlockchainScanner.cpp:665) scanned from height #475996 to #476432
-INFO  - 09:26:11.703: (..\BlockchainScanner.cpp:225) scanned transaction history in 1.813s
-INFO  - 09:26:11.703: (..\BlockDataMap.cpp:313) gc count: 5
-INFO  - 09:26:11.703: (..\BlockDataMap.cpp:314) peak: 5
-INFO  - 09:26:11.703: (..\BlockDataMap.cpp:316)    file id: 935
-INFO  - 09:26:11.703: (..\BlockDataMap.cpp:316)    file id: 936
-INFO  - 09:26:11.703: (..\BlockDataMap.cpp:316)    file id: 937
-INFO  - 09:26:11.703: (..\BlockDataMap.cpp:316)    file id: 938
-INFO  - 09:26:11.703: (..\BlockDataMap.cpp:316)    file id: 939
-INFO  - 09:26:11.953: (..\DatabaseBuilder.cpp:177) scanned new blocks in 2.083s
-INFO  - 09:26:11.953: (..\DatabaseBuilder.cpp:181) init db in 266.61s
-INFO  - 09:26:11.953: (..\BDM_supportClasses.cpp:1873) Enabling zero-conf tracking
-ERROR - 09:28:12.578: (..\SocketObject.cpp:290) POLLERR error in readFromSocketThread
-ERROR - 09:28:12.672: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread

dbLog.txt (No.2)

Code:

-INFO  - 09:45:43.125: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 09:45:44.484: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:249) Listening on port 56843
-INFO  - 09:45:44.906: (..\BlockUtils.cpp:1092) Executing: doInitialSyncOnLoad
-INFO  - 09:45:44.015: (..\DatabaseBuilder.cpp:190) Reading headers from db
-INFO  - 09:45:45.953: (..\BDM_Server.cpp:1074) registered bdv: 98376ae835966ed6a09e
-WARN  - 09:46:43.343: (..\Blockchain.cpp:63) block id duplicate: 476093
-INFO  - 09:47:18.406: (..\DatabaseBuilder.cpp:229) Found 476433 headers in db
-INFO  - 09:47:20.515: (..\DatabaseBuilder.cpp:63) Rewinding 100 blocks
-INFO  - 09:47:20.515: (..\DatabaseBuilder.cpp:70) updating HEADERS db
-INFO  - 09:47:22.484: (..\DatabaseBuilder.cpp:482) Found next block after skipping 997872bytes
-INFO  - 09:47:22.546: (..\DatabaseBuilder.cpp:272) parsed block file #939
-INFO  - 09:47:23.750: (..\Blockchain.cpp:246) Organizing chain 
-INFO  - 09:47:23.796: (..\Blockchain.cpp:360) Organized chain in 0.047s
-INFO  - 09:47:23.812: (..\DatabaseBuilder.cpp:75) updated HEADERS db in 3.297s
-INFO  - 09:47:23.812: (..\DatabaseBuilder.cpp:1121) verifying txfilters integrity
-INFO  - 09:47:58.750: (..\DatabaseBuilder.cpp:1205) done checking txfilters
-INFO  - 09:47:58.078: (..\DatabaseBuilder.cpp:127) scanning new blocks from #476433 to #476441
-INFO  - 09:47:59.500: (..\BlockchainScanner.cpp:665) scanned from height #476433 to #476441
-INFO  - 09:47:59.500: (..\BlockDataMap.cpp:313) gc count: 1
-INFO  - 09:47:59.500: (..\BlockDataMap.cpp:314) peak: 1
-INFO  - 09:47:59.500: (..\BlockDataMap.cpp:316)    file id: 939
-INFO  - 09:47:59.562: (..\DatabaseBuilder.cpp:177) scanned new blocks in 0.485s
-INFO  - 09:47:59.562: (..\DatabaseBuilder.cpp:181) init db in 134.655s
-INFO  - 09:47:59.562: (..\BDM_supportClasses.cpp:1873) Enabling zero-conf tracking
-INFO  - 09:51:18.796: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 09:55:10.062: (..\DatabaseBuilder.cpp:482) Found next block after skipping 17845bytes
-INFO  - 09:58:33.625: (..\BlockchainScanner.cpp:665) scanned from height #476442 to #476442
-WARN  - 10:02:26.515: (..\BDM_supportClasses.cpp:1937) running 10 zc parser threads
-INFO  - 10:02:27.765: (..\BlockchainScanner.cpp:665) scanned from height #476443 to #476443
-INFO  - 10:04:52.937: (..\BlockchainScanner.cpp:665) scanned from height #476444 to #476446
-INFO  - 10:05:58.796: (..\BlockchainScanner.cpp:665) scanned from height #476447 to #476447
-INFO  - 10:07:01.515: (..\BlockchainScanner.cpp:665) scanned from height #476448 to #476448
-INFO  - 10:07:41.765: (..\BlockchainScanner.cpp:665) scanned from height #476449 to #476449
-INFO  - 10:08:36.890: (..\BlockchainScanner.cpp:665) scanned from height #476450 to #476450
-INFO  - 10:09:10.609: (..\BlockchainScanner.cpp:665) scanned from height #476451 to #476451
-INFO  - 10:10:00.812: (..\BlockchainScanner.cpp:665) scanned from height #476452 to #476452
-WARN  - 10:10:52.421: (..\BDM_supportClasses.cpp:1937) running 15 zc parser threads
-WARN  - 10:10:52.421: (..\BDM_supportClasses.cpp:1937) running 20 zc parser threads
-WARN  - 10:10:52.421: (..\BDM_supportClasses.cpp:1937) running 25 zc parser threads
-WARN  - 10:10:52.421: (..\BDM_supportClasses.cpp:1937) running 30 zc parser threads
-ERROR - 10:10:53.734: (..\BlockchainScanner.cpp:271) raw data does not match expected block hash

------------------------------------------------------------------------------------------------------------------------------------------------