Title: Armory 0.95.1 is out
Post by: goatpig on November 04, 2016, 02:48:46 AM
Just a few fixes, listed in the changelog: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.95.1 v0.95.1
== Added ==
- Pass client datadir to auto spawned DB
== Fixed ==
- Fixed coin control GUI
- Fixed base58 decode edge case
- Fixed db version detection
- Fixed db error message reporting in GUI
- Fixed explicit db port overwrite in testnet
Title: Re: Armory 0.95.1 is out
Post by: johnlu on November 04, 2016, 04:06:25 PM
It is not working at all. I backed up my .armory directory, then I deleted it and launched armory. It always complains about: The DB has returned the following error:
DB version mismatch. Use another dbdir!
Armory will now shutdown. I'm using armory_0.95.1_amd64.deb install. Armory 0.94.1 was working perfectly. Bitcoin Core 0.13.1
Title: Re: Armory 0.95.1 is out
Post by: achow101 on November 04, 2016, 04:07:52 PM
It is not working at all. I backed up my .armory directory, then I deleted it and launched armory. It always complains about: The DB has returned the following error:
DB version mismatch. Use another dbdir!
Armory will now shutdown. Log files please. Are you sure you are deleting the right folder? Are you sure that is the folder that Armory is actually using as its datadir? Deleting the databases folder inside of the datadir should do the trick.
Title: Re: Armory 0.95.1 is out
Post by: johnlu on November 04, 2016, 04:10:29 PM
Log files please.
Are you sure you are deleting the right folder? Are you sure that is the folder that Armory is actually using as its datadir? Deleting the databases folder inside of the datadir should do the trick.
rm /home/user/.armory/* -rf Pretty sure, that is a clean armory first run, it even asks me about to accept the license.
Title: Re: Armory 0.95.1 is out
Post by: johnlu on November 04, 2016, 04:13:08 PM
Here is the armorylog.txt:
http://pastebin.com/UnsJTgWu
Title: Re: Armory 0.95.1 is out
Post by: johnlu on November 04, 2016, 04:20:39 PM
It seems to be working now, the problem was ArmoryDB didn't close after armory was closed...
Title: Re: Armory 0.95.1 is out
Post by: segeln on November 06, 2016, 10:13:35 AM
It is not working at all. I backed up my .armory directory, then I deleted it and launched armory. It always complains about: The DB has returned the following error:
DB version mismatch. Use another dbdir!
Armory will now shutdown. I'm using armory_0.95.1_amd64.deb install. Armory 0.94.1 was working perfectly. Bitcoin Core 0.13.1 I just got the same problem ,same message and switched back to armory0.93.3,which works fine. But how to install the version 0.95.1 proper? Please a simple answer,because I am not very It- tech firm. Thanks
Title: Re: Armory 0.95.1 is out
Post by: segeln on November 06, 2016, 10:14:31 AM
It seems to be working now, the problem was ArmoryDB didn't close after armory was closed...
How did you fix that?
Title: Re: Armory 0.95.1 is out
Post by: segeln on November 06, 2016, 01:28:14 PM
I have had succes.Armory 0.95.1 works!
To be honest,I do not know exactly what steps I took to get the new version running
Title: Re: Armory 0.95.1 is out
Post by: johnlu on November 06, 2016, 04:01:24 PM
It seems to be working now, the problem was ArmoryDB didn't close after armory was closed...
How did you fix that? Killed ArmoryDB process
Title: Re: Armory 0.95.1 is out
Post by: ARXANGEL on November 07, 2016, 05:34:40 PM
For me not work. ArmoryDB shoutdown. Bitcoind and ArmoryQT work normal (but sometimes ArmoryQT freeze). http://s010.radikal.ru/i313/1611/63/25896ba94129.jpgLog: Log file opened at 1478532351: R:\Bitcoin\Armory\Data/dbLog.txt
-INFO - 1478532351: (..\main.cpp:23) Running on 2 threads
-INFO - 1478532351: (..\main.cpp:24) Ram usage level: 4
-INFO - 1478532351: (..\BlockUtils.cpp:1338) blkfile dir: R:\Bitcoin\Data\blocks
-INFO - 1478532351: (..\BlockUtils.cpp:1339) lmdb dir: R:\Bitcoin\Armory\Data\databases
-INFO - 1478532351: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1478532352: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1478532352: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1478532352: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1478532352: (..\BDM_Server.cpp:797) registered bdv: dde425edf43ef6be5bfa
-INFO - 1478532394: (..\DatabaseBuilder.cpp:208) Found 437708 headers in db
-INFO - 1478532399: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1478532400: (..\DatabaseBuilder.cpp:477) Found next block after skipping 688407bytes
-INFO - 1478532400: (..\DatabaseBuilder.cpp:268) parsed block file #672
-DEBUG - 1478532403: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1478532404: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 5.281s
-INFO - 1478532404: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-INFO - 1478532405: (..\BDM_supportClasses.cpp:366) Starting address registration process
-INFO - 1478532492: (..\BlockchainScanner.cpp:650) scanned from height #0 to #142518
-INFO - 1478532783: (..\BlockchainScanner.cpp:650) scanned from height #142519 to #163679
-INFO - 1478532821: (..\BlockchainScanner.cpp:650) scanned from height #163680 to #179799
-INFO - 1478532837: (..\BlockchainScanner.cpp:650) scanned from height #179800 to #184367
-INFO - 1478532862: (..\BlockchainScanner.cpp:650) scanned from height #184368 to #188884
-INFO - 1478532880: (..\BlockchainScanner.cpp:650) scanned from height #188885 to #193618
-INFO - 1478532904: (..\BlockchainScanner.cpp:650) scanned from height #193619 to #197561
-INFO - 1478532937: (..\BlockchainScanner.cpp:650) scanned from height #197562 to #202226
-INFO - 1478532959: (..\BlockchainScanner.cpp:650) scanned from height #202227 to #207989
-INFO - 1478532972: (..\BlockchainScanner.cpp:650) scanned from height #207990 to #211738
-INFO - 1478532983: (..\BlockchainScanner.cpp:650) scanned from height #211739 to #214864
-INFO - 1478532993: (..\BlockchainScanner.cpp:650) scanned from height #214865 to #217567
-INFO - 1478533006: (..\BlockchainScanner.cpp:650) scanned from height #217568 to #220141
-INFO - 1478533020: (..\BlockchainScanner.cpp:650) scanned from height #220142 to #222771
-INFO - 1478533032: (..\BlockchainScanner.cpp:650) scanned from height #222772 to #225055
-INFO - 1478533041: (..\BlockchainScanner.cpp:650) scanned from height #225056 to #228002
-INFO - 1478533059: (..\BlockchainScanner.cpp:650) scanned from height #228003 to #230231
-INFO - 1478533069: (..\BlockchainScanner.cpp:650) scanned from height #230232 to #232697
-INFO - 1478533108: (..\BlockchainScanner.cpp:650) scanned from height #232698 to #235139
-INFO - 1478533138: (..\BlockchainScanner.cpp:650) scanned from height #235140 to #237233
-INFO - 1478533214: (..\BlockchainScanner.cpp:650) scanned from height #237234 to #240031
-INFO - 1478533265: (..\BlockchainScanner.cpp:650) scanned from height #240032 to #243363
-INFO - 1478533283: (..\BlockchainScanner.cpp:650) scanned from height #243364 to #247174
-INFO - 1478533309: (..\BlockchainScanner.cpp:650) scanned from height #247175 to #250677
-INFO - 1478533350: (..\BlockchainScanner.cpp:650) scanned from height #250678 to #253678
-INFO - 1478533378: (..\BlockchainScanner.cpp:650) scanned from height #253679 to #256633
-INFO - 1478533388: (..\BlockchainScanner.cpp:650) scanned from height #256634 to #259826
-INFO - 1478533403: (..\BlockchainScanner.cpp:650) scanned from height #259827 to #262871
-INFO - 1478533413: (..\BlockchainScanner.cpp:650) scanned from height #262872 to #266052
-INFO - 1478533427: (..\BlockchainScanner.cpp:650) scanned from height #266053 to #268842
-INFO - 1478533447: (..\BlockchainScanner.cpp:650) scanned from height #268843 to #270791
-INFO - 1478533463: (..\BlockchainScanner.cpp:650) scanned from height #270792 to #272659
-INFO - 1478533478: (..\BlockchainScanner.cpp:650) scanned from height #272660 to #274880
-INFO - 1478533498: (..\BlockchainScanner.cpp:650) scanned from height #274881 to #277185
-INFO - 1478533515: (..\BlockchainScanner.cpp:650) scanned from height #277186 to #279646
-INFO - 1478533531: (..\BlockchainScanner.cpp:650) scanned from height #279647 to #282116
-INFO - 1478533649: (..\BlockchainScanner.cpp:650) scanned from height #282117 to #284930
-INFO - 1478533665: (..\BlockchainScanner.cpp:650) scanned from height #284931 to #287397
-ERROR - 1478533676: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1478533677: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478533680: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1478533690: (..\BlockchainScanner.cpp:650) scanned from height #287398 to #288980
-INFO - 1478533708: (..\BlockchainScanner.cpp:650) scanned from height #288981 to #290734
-INFO - 1478533730: (..\BlockchainScanner.cpp:650) scanned from height #290735 to #292594
-INFO - 1478533747: (..\BlockchainScanner.cpp:650) scanned from height #292595 to #294598
-INFO - 1478533772: (..\BlockchainScanner.cpp:650) scanned from height #294599 to #296152
-INFO - 1478533791: (..\BlockchainScanner.cpp:650) scanned from height #296153 to #297523
-INFO - 1478533920: (..\BlockchainScanner.cpp:650) scanned from height #297524 to #299260
-INFO - 1478533939: (..\BlockchainScanner.cpp:650) scanned from height #299261 to #301745
-INFO - 1478533976: (..\BlockchainScanner.cpp:650) scanned from height #301746 to #303358
-INFO - 1478534000: (..\BlockchainScanner.cpp:650) scanned from height #303359 to #305208
-INFO - 1478534073: (..\BlockchainScanner.cpp:650) scanned from height #305209 to #306985
-INFO - 1478534106: (..\BlockchainScanner.cpp:650) scanned from height #306986 to #308998
-INFO - 1478534123: (..\BlockchainScanner.cpp:650) scanned from height #308999 to #311234
-INFO - 1478534135: (..\BlockchainScanner.cpp:650) scanned from height #311235 to #312705
-INFO - 1478534161: (..\BlockchainScanner.cpp:650) scanned from height #312706 to #314565
-INFO - 1478534172: (..\BlockchainScanner.cpp:650) scanned from height #314566 to #316104
-INFO - 1478534201: (..\BlockchainScanner.cpp:650) scanned from height #316105 to #318384
-INFO - 1478534219: (..\BlockchainScanner.cpp:650) scanned from height #318385 to #319756
-INFO - 1478534252: (..\BlockchainScanner.cpp:650) scanned from height #319757 to #321089
-INFO - 1478534297: (..\BlockchainScanner.cpp:650) scanned from height #321090 to #323073
-INFO - 1478534400: (..\BlockchainScanner.cpp:650) scanned from height #323074 to #324835
-INFO - 1478534444: (..\BlockchainScanner.cpp:650) scanned from height #324836 to #326600
-INFO - 1478534466: (..\BlockchainScanner.cpp:650) scanned from height #326601 to #328037
-INFO - 1478534504: (..\BlockchainScanner.cpp:650) scanned from height #328038 to #329542
-INFO - 1478534531: (..\BlockchainScanner.cpp:650) scanned from height #329543 to #330584
-INFO - 1478534579: (..\BlockchainScanner.cpp:650) scanned from height #330585 to #332844
-INFO - 1478534591: (..\BlockchainScanner.cpp:650) scanned from height #332845 to #334383
-INFO - 1478534603: (..\BlockchainScanner.cpp:650) scanned from height #334384 to #334733
-INFO - 1478534649: (..\BlockchainScanner.cpp:650) scanned from height #334734 to #335987
-INFO - 1478534659: (..\BlockchainScanner.cpp:650) scanned from height #335988 to #337671
-INFO - 1478534685: (..\BlockchainScanner.cpp:650) scanned from height #337672 to #339091
-INFO - 1478534702: (..\BlockchainScanner.cpp:650) scanned from height #339092 to #340133
-INFO - 1478534724: (..\BlockchainScanner.cpp:650) scanned from height #340134 to #341194
-INFO - 1478534742: (..\BlockchainScanner.cpp:650) scanned from height #341195 to #342481
-INFO - 1478534768: (..\BlockchainScanner.cpp:650) scanned from height #342482 to #343670
-INFO - 1478534817: (..\BlockchainScanner.cpp:650) scanned from height #343671 to #344839
-INFO - 1478534833: (..\BlockchainScanner.cpp:650) scanned from height #344840 to #345617
-INFO - 1478534834: (..\BlockchainScanner.cpp:650) scanned from height #345618 to #345624
-INFO - 1478534853: (..\BlockchainScanner.cpp:650) scanned from height #345625 to #347894
-INFO - 1478534870: (..\BlockchainScanner.cpp:650) scanned from height #347895 to #349336
-INFO - 1478534888: (..\BlockchainScanner.cpp:650) scanned from height #349337 to #350335
-INFO - 1478534896: (..\BlockchainScanner.cpp:650) scanned from height #350336 to #351377
-INFO - 1478534904: (..\BlockchainScanner.cpp:650) scanned from height #351378 to #351627
-INFO - 1478534962: (..\BlockchainScanner.cpp:650) scanned from height #351628 to #353471
-INFO - 1478534969: (..\BlockchainScanner.cpp:650) scanned from height #353472 to #354132
-INFO - 1478535010: (..\BlockchainScanner.cpp:650) scanned from height #354133 to #355733
-INFO - 1478535018: (..\BlockchainScanner.cpp:650) scanned from height #355734 to #356739
-INFO - 1478535037: (..\BlockchainScanner.cpp:650) scanned from height #356740 to #357866
-INFO - 1478535055: (..\BlockchainScanner.cpp:650) scanned from height #357867 to #359078
-INFO - 1478535072: (..\BlockchainScanner.cpp:650) scanned from height #359079 to #359929
-INFO - 1478535087: (..\BlockchainScanner.cpp:650) scanned from height #359930 to #360899
-INFO - 1478535120: (..\BlockchainScanner.cpp:650) scanned from height #360900 to #361686
-INFO - 1478535144: (..\BlockchainScanner.cpp:650) scanned from height #361687 to #362628
-INFO - 1478535175: (..\BlockchainScanner.cpp:650) scanned from height #362629 to #363379
-INFO - 1478535207: (..\BlockchainScanner.cpp:650) scanned from height #363380 to #364362
-INFO - 1478535229: (..\BlockchainScanner.cpp:650) scanned from height #364363 to #365053
-INFO - 1478535270: (..\BlockchainScanner.cpp:650) scanned from height #365054 to #365879
-INFO - 1478535340: (..\BlockchainScanner.cpp:650) scanned from height #365880 to #367176
-INFO - 1478535348: (..\BlockchainScanner.cpp:650) scanned from height #367177 to #367528
-INFO - 1478535372: (..\BlockchainScanner.cpp:650) scanned from height #367529 to #368399
-INFO - 1478535390: (..\BlockchainScanner.cpp:650) scanned from height #368400 to #369017
-INFO - 1478535399: (..\BlockchainScanner.cpp:650) scanned from height #369018 to #369823
-INFO - 1478535431: (..\BlockchainScanner.cpp:650) scanned from height #369824 to #370832
-INFO - 1478535544: (..\BlockchainScanner.cpp:650) scanned from height #370833 to #371951
-INFO - 1478535561: (..\BlockchainScanner.cpp:650) scanned from height #371952 to #372774
-INFO - 1478535598: (..\BlockchainScanner.cpp:650) scanned from height #372775 to #373648
-INFO - 1478535622: (..\BlockchainScanner.cpp:650) scanned from height #373649 to #374121
-INFO - 1478535636: (..\BlockchainScanner.cpp:650) scanned from height #374122 to #374507
-INFO - 1478535674: (..\BlockchainScanner.cpp:650) scanned from height #374508 to #375658
-INFO - 1478535686: (..\BlockchainScanner.cpp:650) scanned from height #375659 to #376531
-INFO - 1478535698: (..\BlockchainScanner.cpp:650) scanned from height #376532 to #377202
-INFO - 1478535746: (..\BlockchainScanner.cpp:650) scanned from height #377203 to #378285
-INFO - 1478535812: (..\BlockchainScanner.cpp:650) scanned from height #378286 to #379440
-ERROR - 1478535885: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1478535885: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1478535885: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478535886: (..\BlockchainScanner.cpp:650) scanned from height #379441 to #380375
-INFO - 1478535894: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1478537681: (..\SocketObject.cpp:133) POLLERR in writeToSocket
-ERROR - 1478537681: (..\SocketObject.cpp:133) POLLERR in writeToSocket
-ERROR - 1478537681: (..\SocketObject.cpp:133) POLLERR in writeToSocket
-ERROR - 1478537681: (..\SocketObject.cpp:133) POLLERR in writeToSocket
-ERROR - 1478537682: (..\BitcoinP2P.cpp:851) caught SocketError exception in processDataStackThread: recv error: 10054
-INFO - 1478537682: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478537683: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node It's second run. At first run this: Log file opened at 1478524470: R:\Bitcoin\Armory\Data/dbLog.txt
-INFO - 1478524470: (..\main.cpp:23) Running on 2 threads
-INFO - 1478524470: (..\main.cpp:24) Ram usage level: 4
-INFO - 1478524470: (..\BlockUtils.cpp:1338) blkfile dir: R:\Bitcoin\Data\blocks
-INFO - 1478524470: (..\BlockUtils.cpp:1339) lmdb dir: R:\Bitcoin\Armory\Data\databases
-INFO - 1478524470: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1478524472: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1478524472: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1478524472: (..\BDM_Server.cpp:797) registered bdv: c15155df90911e1623e1
-INFO - 1478524502: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1478524530: (..\DatabaseBuilder.cpp:208) Found 437691 headers in db
-INFO - 1478524534: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1478524536: (..\DatabaseBuilder.cpp:477) Found next block after skipping 511263bytes
-INFO - 1478524539: (..\DatabaseBuilder.cpp:268) parsed block file #671
-DEBUG - 1478524539: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1478524540: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 5.977s
-INFO - 1478524540: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-INFO - 1478524541: (..\BDM_supportClasses.cpp:366) Starting address registration process
-INFO - 1478524819: (..\BlockchainScanner.cpp:650) scanned from height #0 to #142518
-INFO - 1478524844: (..\BlockchainScanner.cpp:650) scanned from height #142519 to #163679
-INFO - 1478524869: (..\BlockchainScanner.cpp:650) scanned from height #163680 to #179799
-INFO - 1478524891: (..\BlockchainScanner.cpp:650) scanned from height #179800 to #184367
-INFO - 1478524914: (..\BlockchainScanner.cpp:650) scanned from height #184368 to #188884
-INFO - 1478524959: (..\BlockchainScanner.cpp:650) scanned from height #188885 to #193618
-INFO - 1478524970: (..\BlockchainScanner.cpp:650) scanned from height #193619 to #197561
-INFO - 1478524988: (..\BlockchainScanner.cpp:650) scanned from height #197562 to #202226
-INFO - 1478525009: (..\BlockchainScanner.cpp:650) scanned from height #202227 to #207989
-INFO - 1478525033: (..\BlockchainScanner.cpp:650) scanned from height #207990 to #211738
-INFO - 1478525044: (..\BlockchainScanner.cpp:650) scanned from height #211739 to #214864
-INFO - 1478525057: (..\BlockchainScanner.cpp:650) scanned from height #214865 to #217567
-INFO - 1478525066: (..\BlockchainScanner.cpp:650) scanned from height #217568 to #220141
-INFO - 1478525089: (..\BlockchainScanner.cpp:650) scanned from height #220142 to #222771
-INFO - 1478525099: (..\BlockchainScanner.cpp:650) scanned from height #222772 to #225055
-INFO - 1478525110: (..\BlockchainScanner.cpp:650) scanned from height #225056 to #228002
-INFO - 1478525120: (..\BlockchainScanner.cpp:650) scanned from height #228003 to #230231
-INFO - 1478525130: (..\BlockchainScanner.cpp:650) scanned from height #230232 to #232697
-INFO - 1478525139: (..\BlockchainScanner.cpp:650) scanned from height #232698 to #235139
-INFO - 1478525148: (..\BlockchainScanner.cpp:650) scanned from height #235140 to #237233
-INFO - 1478525163: (..\BlockchainScanner.cpp:650) scanned from height #237234 to #240031
-INFO - 1478525227: (..\BlockchainScanner.cpp:650) scanned from height #240032 to #243363
-INFO - 1478525243: (..\BlockchainScanner.cpp:650) scanned from height #243364 to #247174
-INFO - 1478525271: (..\BlockchainScanner.cpp:650) scanned from height #247175 to #250677
-INFO - 1478525284: (..\BlockchainScanner.cpp:650) scanned from height #250678 to #253678
-INFO - 1478525294: (..\BlockchainScanner.cpp:650) scanned from height #253679 to #256633
-INFO - 1478525308: (..\BlockchainScanner.cpp:650) scanned from height #256634 to #259826
-INFO - 1478525318: (..\BlockchainScanner.cpp:650) scanned from height #259827 to #262871
-INFO - 1478525324: (..\BlockchainScanner.cpp:650) scanned from height #262872 to #266052
-INFO - 1478525358: (..\BlockchainScanner.cpp:650) scanned from height #266053 to #268842
-INFO - 1478525377: (..\BlockchainScanner.cpp:650) scanned from height #268843 to #270791
-INFO - 1478525497: (..\BlockchainScanner.cpp:650) scanned from height #270792 to #272659
-INFO - 1478525519: (..\BlockchainScanner.cpp:650) scanned from height #272660 to #274880
-INFO - 1478525559: (..\BlockchainScanner.cpp:650) scanned from height #274881 to #277185
-INFO - 1478525567: (..\BlockchainScanner.cpp:650) scanned from height #277186 to #279646
-INFO - 1478525588: (..\BlockchainScanner.cpp:650) scanned from height #279647 to #282116
-INFO - 1478525617: (..\BlockchainScanner.cpp:650) scanned from height #282117 to #284930
-INFO - 1478525677: (..\BlockchainScanner.cpp:650) scanned from height #284931 to #287397
-INFO - 1478525685: (..\BlockchainScanner.cpp:650) scanned from height #287398 to #288980
-INFO - 1478525781: (..\BlockchainScanner.cpp:650) scanned from height #288981 to #290734
-INFO - 1478525799: (..\BlockchainScanner.cpp:650) scanned from height #290735 to #292594
-INFO - 1478525812: (..\BlockchainScanner.cpp:650) scanned from height #292595 to #294598
-ERROR - 1478525827: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1478525827: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478525830: (..\BlockchainScanner.cpp:650) scanned from height #294599 to #296152
-INFO - 1478525841: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1478525969: (..\BlockchainScanner.cpp:650) scanned from height #296153 to #297523
-INFO - 1478526000: (..\BlockchainScanner.cpp:650) scanned from height #297524 to #299260
-INFO - 1478526041: (..\BlockchainScanner.cpp:650) scanned from height #299261 to #301745
-INFO - 1478526073: (..\BlockchainScanner.cpp:650) scanned from height #301746 to #303358
-INFO - 1478526081: (..\BlockchainScanner.cpp:650) scanned from height #303359 to #305208
-INFO - 1478526101: (..\BlockchainScanner.cpp:650) scanned from height #305209 to #306985
-INFO - 1478526115: (..\BlockchainScanner.cpp:650) scanned from height #306986 to #308998
-INFO - 1478526127: (..\BlockchainScanner.cpp:650) scanned from height #308999 to #311234
-INFO - 1478526139: (..\BlockchainScanner.cpp:650) scanned from height #311235 to #312705
-INFO - 1478526229: (..\BlockchainScanner.cpp:650) scanned from height #312706 to #314565
-INFO - 1478526246: (..\BlockchainScanner.cpp:650) scanned from height #314566 to #316104
-INFO - 1478526271: (..\BlockchainScanner.cpp:650) scanned from height #316105 to #318384
-INFO - 1478526281: (..\BlockchainScanner.cpp:650) scanned from height #318385 to #319756
-INFO - 1478526303: (..\BlockchainScanner.cpp:650) scanned from height #319757 to #321089
-INFO - 1478526329: (..\BlockchainScanner.cpp:650) scanned from height #321090 to #323073
-INFO - 1478526357: (..\BlockchainScanner.cpp:650) scanned from height #323074 to #324835
-INFO - 1478526404: (..\BlockchainScanner.cpp:650) scanned from height #324836 to #326600
-INFO - 1478526413: (..\BlockchainScanner.cpp:650) scanned from height #326601 to #328037
-INFO - 1478526446: (..\BlockchainScanner.cpp:650) scanned from height #328038 to #329542
-INFO - 1478526514: (..\BlockchainScanner.cpp:650) scanned from height #329543 to #330584
-INFO - 1478526577: (..\BlockchainScanner.cpp:650) scanned from height #330585 to #332844
-INFO - 1478526588: (..\BlockchainScanner.cpp:650) scanned from height #332845 to #334383
-INFO - 1478526606: (..\BlockchainScanner.cpp:650) scanned from height #334384 to #334733
-INFO - 1478526643: (..\BlockchainScanner.cpp:650) scanned from height #334734 to #335987
-INFO - 1478526786: (..\BlockchainScanner.cpp:650) scanned from height #335988 to #337671
-INFO - 1478526802: (..\BlockchainScanner.cpp:650) scanned from height #337672 to #339091
-INFO - 1478526810: (..\BlockchainScanner.cpp:650) scanned from height #339092 to #340133
-INFO - 1478526841: (..\BlockchainScanner.cpp:650) scanned from height #340134 to #341194
-INFO - 1478526851: (..\BlockchainScanner.cpp:650) scanned from height #341195 to #342481
-INFO - 1478526887: (..\BlockchainScanner.cpp:650) scanned from height #342482 to #343670
-INFO - 1478526915: (..\BlockchainScanner.cpp:650) scanned from height #343671 to #344839
-INFO - 1478526927: (..\BlockchainScanner.cpp:650) scanned from height #344840 to #345617
-INFO - 1478526928: (..\BlockchainScanner.cpp:650) scanned from height #345618 to #345624
-INFO - 1478527007: (..\BlockchainScanner.cpp:650) scanned from height #345625 to #347894
-INFO - 1478527026: (..\BlockchainScanner.cpp:650) scanned from height #347895 to #349336
-INFO - 1478527036: (..\BlockchainScanner.cpp:650) scanned from height #349337 to #350335
-INFO - 1478527045: (..\BlockchainScanner.cpp:650) scanned from height #350336 to #351377
-INFO - 1478527049: (..\BlockchainScanner.cpp:650) scanned from height #351378 to #351627
-INFO - 1478527105: (..\BlockchainScanner.cpp:650) scanned from height #351628 to #353471
-INFO - 1478527119: (..\BlockchainScanner.cpp:650) scanned from height #353472 to #354132
-INFO - 1478527142: (..\BlockchainScanner.cpp:650) scanned from height #354133 to #355733
-INFO - 1478527151: (..\BlockchainScanner.cpp:650) scanned from height #355734 to #356739
-ERROR - 1478527162: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1478527162: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478527164: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1478527169: (..\BlockchainScanner.cpp:650) scanned from height #356740 to #357866
-INFO - 1478527179: (..\BlockchainScanner.cpp:650) scanned from height #357867 to #359078
-INFO - 1478527193: (..\BlockchainScanner.cpp:650) scanned from height #359079 to #359929
-INFO - 1478527264: (..\BlockchainScanner.cpp:650) scanned from height #359930 to #360899
-INFO - 1478527284: (..\BlockchainScanner.cpp:650) scanned from height #360900 to #361686
-INFO - 1478527305: (..\BlockchainScanner.cpp:650) scanned from height #361687 to #362628
-INFO - 1478527331: (..\BlockchainScanner.cpp:650) scanned from height #362629 to #363379
-INFO - 1478527376: (..\BlockchainScanner.cpp:650) scanned from height #363380 to #364362
-INFO - 1478527433: (..\BlockchainScanner.cpp:650) scanned from height #364363 to #365053
-INFO - 1478527486: (..\BlockchainScanner.cpp:650) scanned from height #365054 to #365879
-INFO - 1478527538: (..\BlockchainScanner.cpp:650) scanned from height #365880 to #367176
-INFO - 1478527550: (..\BlockchainScanner.cpp:650) scanned from height #367177 to #367528
-INFO - 1478527614: (..\BlockchainScanner.cpp:650) scanned from height #367529 to #368399
-INFO - 1478527621: (..\BlockchainScanner.cpp:650) scanned from height #368400 to #369017
-INFO - 1478527665: (..\BlockchainScanner.cpp:650) scanned from height #369018 to #369823
-INFO - 1478527697: (..\BlockchainScanner.cpp:650) scanned from height #369824 to #370832
-INFO - 1478527714: (..\BlockchainScanner.cpp:650) scanned from height #370833 to #371951
-INFO - 1478527769: (..\BlockchainScanner.cpp:650) scanned from height #371952 to #372774
-INFO - 1478527793: (..\BlockchainScanner.cpp:650) scanned from height #372775 to #373648
-INFO - 1478527836: (..\BlockchainScanner.cpp:650) scanned from height #373649 to #374121
-INFO - 1478527845: (..\BlockchainScanner.cpp:650) scanned from height #374122 to #374507
-INFO - 1478527961: (..\BlockchainScanner.cpp:650) scanned from height #374508 to #375658
-INFO - 1478527980: (..\BlockchainScanner.cpp:650) scanned from height #375659 to #376531
-INFO - 1478527990: (..\BlockchainScanner.cpp:650) scanned from height #376532 to #377202
-INFO - 1478528128: (..\BlockchainScanner.cpp:650) scanned from height #377203 to #378285
-INFO - 1478528200: (..\BlockchainScanner.cpp:650) scanned from height #378286 to #379440
-INFO - 1478528240: (..\BlockchainScanner.cpp:650) scanned from height #379441 to #380375
-INFO - 1478528336: (..\BlockchainScanner.cpp:650) scanned from height #380376 to #381068
-INFO - 1478528373: (..\BlockchainScanner.cpp:650) scanned from height #381069 to #381734
-INFO - 1478528423: (..\BlockchainScanner.cpp:650) scanned from height #381735 to #382465
-INFO - 1478528486: (..\BlockchainScanner.cpp:650) scanned from height #382466 to #383333
-ERROR - 1478528497: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1478528497: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478528497: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1478528516: (..\BlockchainScanner.cpp:650) scanned from height #383334 to #384008
-INFO - 1478528551: (..\BlockchainScanner.cpp:650) scanned from height #384009 to #385054
-INFO - 1478528580: (..\BlockchainScanner.cpp:650) scanned from height #385055 to #385623
-INFO - 1478528650: (..\BlockchainScanner.cpp:650) scanned from height #385624 to #386304
-INFO - 1478528765: (..\BlockchainScanner.cpp:650) scanned from height #386305 to #387306
-INFO - 1478528814: (..\BlockchainScanner.cpp:650) scanned from height #387307 to #388192
-INFO - 1478528822: (..\BlockchainScanner.cpp:650) scanned from height #388193 to #388290
-INFO - 1478528822: (..\BlockchainScanner.cpp:650) scanned from height #388291 to #388292
-INFO - 1478528853: (..\BlockchainScanner.cpp:650) scanned from height #388293 to #388765
-INFO - 1478528864: (..\BlockchainScanner.cpp:650) scanned from height #388766 to #389116
-INFO - 1478528879: (..\BlockchainScanner.cpp:650) scanned from height #389117 to #389390
-INFO - 1478529060: (..\BlockchainScanner.cpp:650) scanned from height #389391 to #390539
-INFO - 1478529095: (..\BlockchainScanner.cpp:650) scanned from height #390540 to #391463
-INFO - 1478529128: (..\BlockchainScanner.cpp:650) scanned from height #391464 to #392382
-INFO - 1478529140: (..\BlockchainScanner.cpp:650) scanned from height #392383 to #392908
-INFO - 1478529183: (..\BlockchainScanner.cpp:650) scanned from height #392909 to #393539
-INFO - 1478529191: (..\BlockchainScanner.cpp:650) scanned from height #393540 to #393884
-INFO - 1478529230: (..\BlockchainScanner.cpp:650) scanned from height #393885 to #394948
-INFO - 1478529238: (..\BlockchainScanner.cpp:650) scanned from height #394949 to #395202
-INFO - 1478529259: (..\BlockchainScanner.cpp:650) scanned from height #395203 to #396096
-INFO - 1478529338: (..\BlockchainScanner.cpp:650) scanned from height #396097 to #396960
-INFO - 1478529355: (..\BlockchainScanner.cpp:650) scanned from height #396961 to #397425
-INFO - 1478529424: (..\BlockchainScanner.cpp:650) scanned from height #397426 to #398298
-INFO - 1478529475: (..\BlockchainScanner.cpp:650) scanned from height #398299 to #398994
-INFO - 1478529531: (..\BlockchainScanner.cpp:650) scanned from height #398995 to #399554
-INFO - 1478529542: (..\BlockchainScanner.cpp:650) scanned from height #399555 to #399752
-INFO - 1478529669: (..\BlockchainScanner.cpp:650) scanned from height #399753 to #400705
-INFO - 1478529735: (..\BlockchainScanner.cpp:650) scanned from height #400706 to #401440
-ERROR - 1478529753: (..\BitcoinP2P.cpp:865) caught BitcoinP2P_Exception in processDataStackThread: invalid header size
-INFO - 1478529753: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-ERROR - 1478529754: (..\BitcoinP2P.cpp:851) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-ERROR - 1478529754: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1478529754: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1478529754: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1478529754: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1478529754: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1478529754: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-INFO - 1478529756: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478529756: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node Then I close ArmoryQT. 2016-11-07 18:24 (ERROR) -- SDM.pyc:607 - bitcoind failed to shutdown in less than 2 minutes. Terminating.
2016-11-07 18:24 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window!
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1247 -
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1248 -
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1249 -
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=R:\Bitcoin\Armory\Data
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1254 - Armory Version : 0.95.1
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1255 - Armory Build: : 374672b751
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1256 - PyBtcWallet Version : 1.35
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1258 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1259 - User home-directory : C:\Users\ARXANGEL\AppData\Roaming
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1260 - Satoshi BTC directory : C:\Users\ARXANGEL\AppData\Roaming\Bitcoin\
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1261 - Armory home dir : R:\Bitcoin\Armory\Data
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs :
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1263 - Total Available RAM : 4.00 GB
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1264 - CPU ID string : Intel64 Family 6 Model 23 Stepping 6, GenuineIntel
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1265 - Number of CPU cores : 2 cores
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1266 - System is 64-bit : True
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1267 - Preferred Encoding : cp1251
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1268 - Machine Arch : amd64
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1269 - Available HDD (ARM) : 53 GB
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1270 - Available HDD (BTC) : 2 GB
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1271 -
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - thread_count : -1
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - rescan : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - ignoreAllZC : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - rescanBalance : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - disableModules : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - port : None
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - interport : 8223
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - skipStatsReport : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - forceWalletCheck: False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - regtest : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - rebuild : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - nettimeout : 2
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - datadir : R:\Bitcoin\Armory\Data
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - clearMempool : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - offline : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - coverageOutputDir: None
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - armoryDBDir : DEFAULT
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_port : 9001
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - satoshiPort : DEFAULT
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - useTorSettings : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - netlog : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - keypool : 100
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - coverageInclude : None
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - forceOnline : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - skipAnnounceCheck: False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - redownload : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_ip : 127.0.0.1
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - multisigFile : DEFAULT
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - ram_usage : -1
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - testAnnounceCode: False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - mtdebug : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - logDisable : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - settingsPath : R:\Bitcoin\Armory\Data\ArmorySettings.txt
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - db_type : DB_FULL
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - doDebug : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - enableDetSign : True
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - disableConfPermis: False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - testnet : False
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - rpcport : DEFAULT
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - satoshiHome : DEFAULT
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - satoshiRpcport : DEFAULT
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - logFile : R:\Bitcoin\Armory\Data\ArmoryQt.exe.log.txt
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1277 - verbosity : None
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2016-11-07 18:24 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2016-11-07 18:24 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background.
2016-11-07 18:24 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2016-11-07 18:24 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2016-11-07 18:24 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: R:\Bitcoin\Armory\Data\ArmorySettings.txt
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 1
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2603 - Wallet (gbdiiRKM): "ArxWallet " (Encrypted)
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2608 - Loading Multisig Lockboxes
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2016-11-07 18:24 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2016-11-07 18:24 (INFO) -- ArmoryQt.py:1530 - URL-register action: AskUser
2016-11-07 18:24 (INFO) -- ArmoryQt.py:546 - Usermode: Expert
2016-11-07 18:24 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2016-11-07 18:24 (INFO) -- ArmoryQt.py:1709 - From: Expert
2016-11-07 18:24 (INFO) -- ArmoryQt.py:1717 - To: Expert
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2016-11-07 18:24 (INFO) -- ArmoryQt.py:2275 - Setting satoshi datadir = R:\Bitcoin\Data
2016-11-07 18:24 (INFO) -- SDM.pyc:301 - Found Bitcoin-Core link on desktop: C:\Program Files (x86)\Armory
2016-11-07 18:24 (INFO) -- SDM.pyc:301 - Found Bitcoin-Core link on desktop: R:\Bitcoin
2016-11-07 18:24 (INFO) -- SDM.pyc:182 - Found bitcoind in the following places:
2016-11-07 18:24 (INFO) -- SDM.pyc:184 - R:\Bitcoin\daemon\bitcoind.exe
2016-11-07 18:24 (INFO) -- SDM.pyc:184 - R:\Bitcoin\daemon\bitcoind.exe
2016-11-07 18:24 (INFO) -- SDM.pyc:186 - Using: R:\Bitcoin\daemon\bitcoind.exe
2016-11-07 18:24 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2016-11-07 18:24 (INFO) -- SDM.pyc:395 - Setting permissions on bitcoin.conf
2016-11-07 18:24 (INFO) -- SDM.pyc:404 - Setting permissions on bitcoin.conf
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'icacls', u'R:\\Bitcoin\\Data\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'ARXANGEL:F']
2016-11-07 18:24 (INFO) -- SDM.pyc:410 - icacls returned:
2016-11-07 18:24 (INFO) -- SDM.pyc:460 - Called startBitcoind
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'R:\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=R:\\Bitcoin\\Data']
2016-11-07 18:24 (INFO) -- SDM.pyc:574 - PID of bitcoind: 7844
2016-11-07 18:24 (INFO) -- SDM.pyc:575 - PID of armory: 7732
2016-11-07 18:24 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '7732', '7844']
2016-11-07 18:24 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-11-07 18:24 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2016-11-07 18:24 (WARNING) -- SDM.pyc:679 - Overriding not-available state. This should happen 0-5 times
2016-11-07 18:25 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2016-11-07 18:25 (INFO) -- ArmoryQt.py:2275 - Setting satoshi datadir = R:\Bitcoin\Data
2016-11-07 18:25 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="CrAkqUJCMEyDu9YyZDD2qU5ZhaKL5X5w5YM51TGq7FPG"', u'--satoshi-datadir="R:\\Bitcoin\\Data\\blocks"', u'--datadir="R:\\Bitcoin\\Armory\\Data"', u'--dbdir="R:\\Bitcoin\\Armory\\Data\\databases"']
2016-11-07 18:25 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-11-07 18:25 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2016-11-07 18:25 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-11-07 18:25 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2016-11-07 20:06 (INFO) -- ArmoryQt.py:6366 - BDM state is scanning -- force shutdown BDM
2016-11-07 20:06 (INFO) -- SDM.pyc:588 - Called stopBitcoind
2016-11-07 20:07 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window! In log also many this msgs (in previous day): 2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-07 08:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded Also very interesting rebuild database log in previous day: Log file opened at 1478435207: R:\Bitcoin\Armory\Data/dbLog.txt
-INFO - 1478435207: (..\main.cpp:23) Running on 2 threads
-INFO - 1478435207: (..\main.cpp:24) Ram usage level: 4
-INFO - 1478435207: (..\BlockUtils.cpp:1338) blkfile dir: R:\Bitcoin\Data\blocks
-INFO - 1478435207: (..\BlockUtils.cpp:1339) lmdb dir: R:\Bitcoin\Armory\Data\databases
-INFO - 1478435207: (..\lmdb_wrapper.cpp:388) Opening databases...
--INFO - 1478438332: -INFO - 1478438332: (..\BDM_Server.cpp:INFO - 1478438332826-INFO - 1478438332(: : (..\BlockUtils.cpp:1521) unregistered bdv: 7b2732ee2fee9a513bc1
) ..\BitcoinP2P.cpp(Executing: doInitialSyncOnLoad
:783..\BDM_Server.cpp:797) Connected to Bitcoin node
) registered bdv: 7b2732ee2fee9a513bc1
-INFO - 1478438347: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1478438348: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO - 1478438348: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO - 1478438348: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1478438354: (..\DatabaseBuilder.cpp:268) parsed block file #1
-INFO - 1478438358: (..\DatabaseBuilder.cpp:268) parsed block file #3
-INFO - 1478438363: (..\DatabaseBuilder.cpp:268) parsed block file #5
-INFO - 1478438367: (..\DatabaseBuilder.cpp:268) parsed block file #7
-INFO - 1478438373: (..\DatabaseBuilder.cpp:268) parsed block file #9
-INFO - 1478438388: (..\DatabaseBuilder.cpp:268) parsed block file #11
-INFO - 1478438392: (..\DatabaseBuilder.cpp:268) parsed block file #13
--INFO - 1478458298: ERROR - 1478458298: ((..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
..\DatabaseBuilder.cpp:268) parsed block file #15
-INFO - 1478458298: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1478458309: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1478458457: (..\DatabaseBuilder.cpp:268) parsed block file #17
-INFO - 1478458490: (..\DatabaseBuilder.cpp:268) parsed block file #19
-INFO - 1478458530: (..\DatabaseBuilder.cpp:268) parsed block file #21On red lines I need to press Enter in ArmoryDB, otherwise she freeze, may be it's consilience or my brakes hardware. Armory 0.94.1 works not good, but works (infinite freezes on sync cure restart and etc).
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 07, 2016, 05:42:04 PM
Your bitcoin node keeps crashing for some reason. You need to figure out why.
Title: Re: Armory 0.95.1 is out
Post by: ARXANGEL on November 07, 2016, 05:58:12 PM
You suggest rebuild full 100Gb in Bitcoin Core? BitcoinQT not find problems. Bitcoind not crash and work fine all time.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 07, 2016, 06:47:52 PM
Does it work with 0.94.1?
Title: Re: Armory 0.95.1 is out
Post by: ARXANGEL on November 07, 2016, 06:58:10 PM
Yes, it work with 0.94.1. I try rebuild Armory database again. May be it help (it's not fast :) ).
Title: Re: Armory 0.95.1 is out
Post by: ARXANGEL on November 08, 2016, 04:54:38 PM
Rerebuild Armory database is solution. It's work! All loads normal. http://s017.radikal.ru/i444/1611/d6/b91a8461618d.jpgBut ArmoryQT I think lost ArmoryDB after run (or ArmoryDB freeze). I can see balance, can do transactions and etc, but new blocks not load many time. http://s017.radikal.ru/i410/1611/6c/3e9ad3cb31bb.jpgAnd process explorer: http://s011.radikal.ru/i318/1611/9b/a4941f355bd7.jpgArmoryDB log: Log file opened at 1478581789: R:\Bitcoin\Armory\Data/dbLog.txt
-INFO - 1478581789: (..\main.cpp:23) Running on 2 threads
-INFO - 1478581789: (..\main.cpp:24) Ram usage level: 4
-INFO - 1478581789: (..\BlockUtils.cpp:1338) blkfile dir: R:\Bitcoin\Data\blocks
-INFO - 1478581789: (..\BlockUtils.cpp:1339) lmdb dir: R:\Bitcoin\Armory\Data\databases
-INFO - 1478581789: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1478581790: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1478581791: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1478581791: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO - 1478581791: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO - 1478581791: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1478581791: (..\BDM_Server.cpp:797) registered bdv: a072566614b74ec0c87c
-INFO - 1478581796: (..\DatabaseBuilder.cpp:268) parsed block file #1
-INFO - 1478581803: (..\DatabaseBuilder.cpp:268) parsed block file #2
-INFO - 1478581807: (..\DatabaseBuilder.cpp:268) parsed block file #4
-INFO - 1478581811: (..\DatabaseBuilder.cpp:268) parsed block file #6
-INFO - 1478581814: (..\DatabaseBuilder.cpp:268) parsed block file #8
-INFO - 1478581818: (..\DatabaseBuilder.cpp:268) parsed block file #10
-INFO - 1478581837: (..\DatabaseBuilder.cpp:268) parsed block file #11
-INFO - 1478581838: (..\DatabaseBuilder.cpp:268) parsed block file #12
-INFO - 1478581842: (..\DatabaseBuilder.cpp:268) parsed block file #14
-INFO - 1478581846: (..\DatabaseBuilder.cpp:268) parsed block file #16
-INFO - 1478581852: (..\DatabaseBuilder.cpp:268) parsed block file #18
-INFO - 1478581856: (..\DatabaseBuilder.cpp:268) parsed block file #20
-INFO - 1478581860: (..\DatabaseBuilder.cpp:268) parsed block file #22
-INFO - 1478581864: (..\DatabaseBuilder.cpp:268) parsed block file #24
-INFO - 1478581867: (..\DatabaseBuilder.cpp:268) parsed block file #26
-INFO - 1478581887: (..\DatabaseBuilder.cpp:268) parsed block file #28
-INFO - 1478581891: (..\DatabaseBuilder.cpp:268) parsed block file #30
-INFO - 1478581907: (..\DatabaseBuilder.cpp:268) parsed block file #31
-INFO - 1478581911: (..\DatabaseBuilder.cpp:268) parsed block file #33
-INFO - 1478581915: (..\DatabaseBuilder.cpp:268) parsed block file #34
-INFO - 1478581919: (..\DatabaseBuilder.cpp:268) parsed block file #36
-INFO - 1478581922: (..\DatabaseBuilder.cpp:268) parsed block file #38
-INFO - 1478581926: (..\DatabaseBuilder.cpp:268) parsed block file #40
-INFO - 1478581930: (..\DatabaseBuilder.cpp:268) parsed block file #42
-INFO - 1478581933: (..\DatabaseBuilder.cpp:268) parsed block file #44
-INFO - 1478581937: (..\DatabaseBuilder.cpp:268) parsed block file #46
-INFO - 1478581940: (..\DatabaseBuilder.cpp:268) parsed block file #48
-INFO - 1478581944: (..\DatabaseBuilder.cpp:268) parsed block file #50
-INFO - 1478581947: (..\DatabaseBuilder.cpp:268) parsed block file #52
-INFO - 1478581981: (..\DatabaseBuilder.cpp:268) parsed block file #53
-INFO - 1478581984: (..\DatabaseBuilder.cpp:268) parsed block file #55
-INFO - 1478581991: (..\DatabaseBuilder.cpp:268) parsed block file #56
-INFO - 1478581999: (..\DatabaseBuilder.cpp:268) parsed block file #58
-ERROR - 1478582020: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1478582020: (..\BitcoinP2P.cpp:851) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO - 1478582050: (..\DatabaseBuilder.cpp:268) parsed block file #59
-INFO - 1478582056: (..\DatabaseBuilder.cpp:268) parsed block file #61
-INFO - 1478582066: (..\DatabaseBuilder.cpp:268) parsed block file #62
-INFO - 1478582072: (..\DatabaseBuilder.cpp:268) parsed block file #64
-INFO - 1478582080: (..\DatabaseBuilder.cpp:268) parsed block file #65
-INFO - 1478582085: (..\DatabaseBuilder.cpp:268) parsed block file #67
-INFO - 1478582090: (..\DatabaseBuilder.cpp:268) parsed block file #69
-INFO - 1478582094: (..\DatabaseBuilder.cpp:268) parsed block file #71
-INFO - 1478582099: (..\DatabaseBuilder.cpp:268) parsed block file #73
-INFO - 1478582103: (..\DatabaseBuilder.cpp:268) parsed block file #75
-INFO - 1478582108: (..\DatabaseBuilder.cpp:268) parsed block file #77
-INFO - 1478582112: (..\DatabaseBuilder.cpp:268) parsed block file #79
-INFO - 1478582120: (..\DatabaseBuilder.cpp:268) parsed block file #81
-INFO - 1478582123: (..\DatabaseBuilder.cpp:268) parsed block file #83
-INFO - 1478582128: (..\DatabaseBuilder.cpp:268) parsed block file #85
-INFO - 1478582133: (..\DatabaseBuilder.cpp:268) parsed block file #87
-INFO - 1478582136: (..\DatabaseBuilder.cpp:268) parsed block file #89
-INFO - 1478582140: (..\DatabaseBuilder.cpp:268) parsed block file #91
-INFO - 1478582144: (..\DatabaseBuilder.cpp:268) parsed block file #93
-INFO - 1478582149: (..\DatabaseBuilder.cpp:268) parsed block file #95
-INFO - 1478582153: (..\DatabaseBuilder.cpp:268) parsed block file #97
-INFO - 1478582156: (..\DatabaseBuilder.cpp:268) parsed block file #99
-INFO - 1478582160: (..\DatabaseBuilder.cpp:268) parsed block file #101
-INFO - 1478582164: (..\DatabaseBuilder.cpp:268) parsed block file #103
-INFO - 1478582168: (..\DatabaseBuilder.cpp:268) parsed block file #105
-INFO - 1478582172: (..\DatabaseBuilder.cpp:268) parsed block file #107
-INFO - 1478582176: (..\DatabaseBuilder.cpp:268) parsed block file #109
-INFO - 1478582179: (..\DatabaseBuilder.cpp:268) parsed block file #111
-INFO - 1478582183: (..\DatabaseBuilder.cpp:268) parsed block file #113
-INFO - 1478582241: (..\DatabaseBuilder.cpp:268) parsed block file #115
-INFO - 1478582245: (..\DatabaseBuilder.cpp:268) parsed block file #117
-INFO - 1478582248: (..\DatabaseBuilder.cpp:268) parsed block file #119
-INFO - 1478582251: (..\DatabaseBuilder.cpp:268) parsed block file #121
-INFO - 1478582255: (..\DatabaseBuilder.cpp:268) parsed block file #123
-INFO - 1478582280: (..\DatabaseBuilder.cpp:268) parsed block file #125
-INFO - 1478582416: (..\DatabaseBuilder.cpp:268) parsed block file #127
-INFO - 1478582502: (..\DatabaseBuilder.cpp:268) parsed block file #129
-INFO - 1478582507: (..\DatabaseBuilder.cpp:268) parsed block file #131
-INFO - 1478582511: (..\DatabaseBuilder.cpp:268) parsed block file #133
-INFO - 1478582546: (..\DatabaseBuilder.cpp:268) parsed block file #135
-INFO - 1478582598: (..\DatabaseBuilder.cpp:268) parsed block file #137
-INFO - 1478582601: (..\DatabaseBuilder.cpp:268) parsed block file #139
-INFO - 1478582605: (..\DatabaseBuilder.cpp:268) parsed block file #141
-INFO - 1478582608: (..\DatabaseBuilder.cpp:268) parsed block file #143
-INFO - 1478582612: (..\DatabaseBuilder.cpp:268) parsed block file #145
-INFO - 1478582615: (..\DatabaseBuilder.cpp:268) parsed block file #147
-INFO - 1478582619: (..\DatabaseBuilder.cpp:268) parsed block file #149
-INFO - 1478582628: (..\DatabaseBuilder.cpp:268) parsed block file #151
-INFO - 1478582654: (..\DatabaseBuilder.cpp:268) parsed block file #153
-INFO - 1478582686: (..\DatabaseBuilder.cpp:268) parsed block file #155
-INFO - 1478582689: (..\DatabaseBuilder.cpp:268) parsed block file #157
-INFO - 1478582693: (..\DatabaseBuilder.cpp:268) parsed block file #159
-INFO - 1478582700: (..\DatabaseBuilder.cpp:268) parsed block file #161
-INFO - 1478582707: (..\DatabaseBuilder.cpp:268) parsed block file #163
-INFO - 1478582728: (..\DatabaseBuilder.cpp:268) parsed block file #165
-INFO - 1478582734: (..\DatabaseBuilder.cpp:268) parsed block file #167
-INFO - 1478582774: (..\DatabaseBuilder.cpp:268) parsed block file #169
-INFO - 1478582799: (..\DatabaseBuilder.cpp:268) parsed block file #171
-INFO - 1478582803: (..\DatabaseBuilder.cpp:268) parsed block file #173
-INFO - 1478582810: (..\DatabaseBuilder.cpp:268) parsed block file #175
-INFO - 1478582821: (..\DatabaseBuilder.cpp:268) parsed block file #177
-INFO - 1478582849: (..\DatabaseBuilder.cpp:268) parsed block file #179
-INFO - 1478582857: (..\DatabaseBuilder.cpp:268) parsed block file #181
-INFO - 1478582870: (..\DatabaseBuilder.cpp:268) parsed block file #183
-INFO - 1478582926: (..\DatabaseBuilder.cpp:268) parsed block file #185
-INFO - 1478582943: (..\DatabaseBuilder.cpp:268) parsed block file #187
-INFO - 1478583017: (..\DatabaseBuilder.cpp:268) parsed block file #189
-INFO - 1478583022: (..\DatabaseBuilder.cpp:268) parsed block file #191
-INFO - 1478583030: (..\DatabaseBuilder.cpp:268) parsed block file #193
-INFO - 1478583079: (..\DatabaseBuilder.cpp:268) parsed block file #195
-INFO - 1478583085: (..\DatabaseBuilder.cpp:268) parsed block file #197
-INFO - 1478583100: (..\DatabaseBuilder.cpp:268) parsed block file #199
-INFO - 1478583105: (..\DatabaseBuilder.cpp:268) parsed block file #201
-INFO - 1478583160: (..\DatabaseBuilder.cpp:268) parsed block file #203
-INFO - 1478583168: (..\DatabaseBuilder.cpp:268) parsed block file #205
-INFO - 1478583174: (..\DatabaseBuilder.cpp:268) parsed block file #207
-INFO - 1478583185: (..\DatabaseBuilder.cpp:268) parsed block file #209
-INFO - 1478583294: (..\DatabaseBuilder.cpp:268) parsed block file #211
-INFO - 1478583308: (..\DatabaseBuilder.cpp:268) parsed block file #213
-INFO - 1478583390: (..\DatabaseBuilder.cpp:268) parsed block file #215
-INFO - 1478583430: (..\DatabaseBuilder.cpp:268) parsed block file #217
-INFO - 1478583440: (..\DatabaseBuilder.cpp:268) parsed block file #219
-INFO - 1478583451: (..\DatabaseBuilder.cpp:268) parsed block file #221
-INFO - 1478583533: (..\DatabaseBuilder.cpp:268) parsed block file #223
-INFO - 1478583597: (..\DatabaseBuilder.cpp:268) parsed block file #225
-INFO - 1478583632: (..\DatabaseBuilder.cpp:268) parsed block file #227
-INFO - 1478583677: (..\DatabaseBuilder.cpp:268) parsed block file #229
-INFO - 1478583694: (..\DatabaseBuilder.cpp:268) parsed block file #231
-INFO - 1478583707: (..\DatabaseBuilder.cpp:268) parsed block file #233
-INFO - 1478583784: (..\DatabaseBuilder.cpp:268) parsed block file #235
-INFO - 1478583792: (..\DatabaseBuilder.cpp:268) parsed block file #237
-INFO - 1478583849: (..\DatabaseBuilder.cpp:268) parsed block file #239
-INFO - 1478583889: (..\DatabaseBuilder.cpp:268) parsed block file #241
-INFO - 1478583903: (..\DatabaseBuilder.cpp:268) parsed block file #243
-INFO - 1478583921: (..\DatabaseBuilder.cpp:268) parsed block file #245
-INFO - 1478583929: (..\DatabaseBuilder.cpp:268) parsed block file #247
-INFO - 1478583946: (..\DatabaseBuilder.cpp:268) parsed block file #249
-INFO - 1478583999: (..\DatabaseBuilder.cpp:268) parsed block file #251
-INFO - 1478584031: (..\DatabaseBuilder.cpp:268) parsed block file #253
-INFO - 1478584037: (..\DatabaseBuilder.cpp:268) parsed block file #255
-INFO - 1478584043: (..\DatabaseBuilder.cpp:268) parsed block file #257
-INFO - 1478584057: (..\DatabaseBuilder.cpp:268) parsed block file #259
-INFO - 1478584105: (..\DatabaseBuilder.cpp:268) parsed block file #261
-INFO - 1478584167: (..\DatabaseBuilder.cpp:268) parsed block file #263
-INFO - 1478584183: (..\DatabaseBuilder.cpp:268) parsed block file #265
-INFO - 1478584193: (..\DatabaseBuilder.cpp:268) parsed block file #267
-INFO - 1478584220: (..\DatabaseBuilder.cpp:268) parsed block file #269
-INFO - 1478584234: (..\DatabaseBuilder.cpp:268) parsed block file #271
-INFO - 1478584246: (..\DatabaseBuilder.cpp:268) parsed block file #273
-INFO - 1478584253: (..\DatabaseBuilder.cpp:268) parsed block file #275
-INFO - 1478584272: (..\DatabaseBuilder.cpp:268) parsed block file #277
-INFO - 1478584319: (..\DatabaseBuilder.cpp:268) parsed block file #279
-INFO - 1478584329: (..\DatabaseBuilder.cpp:268) parsed block file #281
-INFO - 1478584344: (..\DatabaseBuilder.cpp:268) parsed block file #283
-INFO - 1478584393: (..\DatabaseBuilder.cpp:268) parsed block file #285
-INFO - 1478584438: (..\DatabaseBuilder.cpp:268) parsed block file #287
-INFO - 1478584490: (..\DatabaseBuilder.cpp:268) parsed block file #289
-INFO - 1478584504: (..\DatabaseBuilder.cpp:268) parsed block file #291
-INFO - 1478584528: (..\DatabaseBuilder.cpp:268) parsed block file #293
-INFO - 1478584574: (..\DatabaseBuilder.cpp:268) parsed block file #295
-INFO - 1478584609: (..\DatabaseBuilder.cpp:268) parsed block file #297
-INFO - 1478584623: (..\DatabaseBuilder.cpp:268) parsed block file #299
-INFO - 1478584654: (..\DatabaseBuilder.cpp:268) parsed block file #301
-INFO - 1478584661: (..\DatabaseBuilder.cpp:268) parsed block file #303
-INFO - 1478584676: (..\DatabaseBuilder.cpp:268) parsed block file #305
-INFO - 1478584732: (..\DatabaseBuilder.cpp:268) parsed block file #307
-INFO - 1478584739: (..\DatabaseBuilder.cpp:268) parsed block file #309
-INFO - 1478584746: (..\DatabaseBuilder.cpp:268) parsed block file #311
-INFO - 1478584776: (..\DatabaseBuilder.cpp:268) parsed block file #313
-INFO - 1478584800: (..\DatabaseBuilder.cpp:268) parsed block file #315
-INFO - 1478584808: (..\DatabaseBuilder.cpp:268) parsed block file #317
-INFO - 1478584876: (..\DatabaseBuilder.cpp:268) parsed block file #319
-INFO - 1478584914: (..\DatabaseBuilder.cpp:268) parsed block file #321
-INFO - 1478584922: (..\DatabaseBuilder.cpp:268) parsed block file #323
-INFO - 1478584968: (..\DatabaseBuilder.cpp:268) parsed block file #325
-INFO - 1478585029: (..\DatabaseBuilder.cpp:268) parsed block file #327
-INFO - 1478585043: (..\DatabaseBuilder.cpp:268) parsed block file #329
-INFO - 1478585061: (..\DatabaseBuilder.cpp:268) parsed block file #331
-INFO - 1478585067: (..\DatabaseBuilder.cpp:268) parsed block file #333
-INFO - 1478585092: (..\DatabaseBuilder.cpp:268) parsed block file #335
-INFO - 1478585144: (..\DatabaseBuilder.cpp:268) parsed block file #337
-INFO - 1478585158: (..\DatabaseBuilder.cpp:268) parsed block file #339
-INFO - 1478585181: (..\DatabaseBuilder.cpp:268) parsed block file #341
-INFO - 1478585190: (..\DatabaseBuilder.cpp:268) parsed block file #343
-INFO - 1478585212: (..\DatabaseBuilder.cpp:268) parsed block file #345
-INFO - 1478585242: (..\DatabaseBuilder.cpp:268) parsed block file #347
-INFO - 1478585249: (..\DatabaseBuilder.cpp:268) parsed block file #349
-INFO - 1478585259: (..\DatabaseBuilder.cpp:268) parsed block file #351
-INFO - 1478585288: (..\DatabaseBuilder.cpp:268) parsed block file #353
-INFO - 1478585296: (..\DatabaseBuilder.cpp:268) parsed block file #355
-INFO - 1478585313: (..\DatabaseBuilder.cpp:268) parsed block file #357
-INFO - 1478585358: (..\DatabaseBuilder.cpp:268) parsed block file #359
-INFO - 1478585418: (..\DatabaseBuilder.cpp:268) parsed block file #361
-INFO - 1478585430: (..\DatabaseBuilder.cpp:268) parsed block file #363
-INFO - 1478585452: (..\DatabaseBuilder.cpp:268) parsed block file #365
-INFO - 1478585502: (..\DatabaseBuilder.cpp:268) parsed block file #367
-INFO - 1478585592: (..\DatabaseBuilder.cpp:268) parsed block file #369
-INFO - 1478585645: (..\DatabaseBuilder.cpp:268) parsed block file #371
-INFO - 1478585653: (..\DatabaseBuilder.cpp:268) parsed block file #373
-INFO - 1478585684: (..\DatabaseBuilder.cpp:268) parsed block file #375
-INFO - 1478585708: (..\DatabaseBuilder.cpp:268) parsed block file #377
-INFO - 1478585747: (..\DatabaseBuilder.cpp:268) parsed block file #379
-INFO - 1478585791: (..\DatabaseBuilder.cpp:268) parsed block file #381
-INFO - 1478585832: (..\DatabaseBuilder.cpp:268) parsed block file #383
-INFO - 1478585842: (..\DatabaseBuilder.cpp:268) parsed block file #385
-INFO - 1478585852: (..\DatabaseBuilder.cpp:268) parsed block file #387
-INFO - 1478585919: (..\DatabaseBuilder.cpp:268) parsed block file #389
-INFO - 1478585993: (..\DatabaseBuilder.cpp:268) parsed block file #391
-INFO - 1478586014: (..\DatabaseBuilder.cpp:268) parsed block file #393
-INFO - 1478586037: (..\DatabaseBuilder.cpp:268) parsed block file #395
-INFO - 1478586106: (..\DatabaseBuilder.cpp:268) parsed block file #397
-INFO - 1478586142: (..\DatabaseBuilder.cpp:268) parsed block file #399
-INFO - 1478586156: (..\DatabaseBuilder.cpp:268) parsed block file #401
-INFO - 1478586189: (..\DatabaseBuilder.cpp:268) parsed block file #403
-INFO - 1478586299: (..\DatabaseBuilder.cpp:268) parsed block file #405
-INFO - 1478586432: (..\DatabaseBuilder.cpp:268) parsed block file #407
-INFO - 1478586458: (..\DatabaseBuilder.cpp:268) parsed block file #409
-INFO - 1478586487: (..\DatabaseBuilder.cpp:268) parsed block file #411
-INFO - 1478586511: (..\DatabaseBuilder.cpp:268) parsed block file #413
-INFO - 1478586555: (..\DatabaseBuilder.cpp:268) parsed block file #415
-INFO - 1478586562: (..\DatabaseBuilder.cpp:268) parsed block file #417
-INFO - 1478586603: (..\DatabaseBuilder.cpp:268) parsed block file #419
-INFO - 1478586609: (..\DatabaseBuilder.cpp:268) parsed block file #421
-INFO - 1478586634: (..\DatabaseBuilder.cpp:268) parsed block file #423
-INFO - 1478586724: (..\DatabaseBuilder.cpp:268) parsed block file #425
-INFO - 1478586746: (..\DatabaseBuilder.cpp:268) parsed block file #427
-INFO - 1478586754: (..\DatabaseBuilder.cpp:268) parsed block file #429
-INFO - 1478586765: (..\DatabaseBuilder.cpp:268) parsed block file #431
-INFO - 1478586801: (..\DatabaseBuilder.cpp:268) parsed block file #433
-INFO - 1478586832: (..\DatabaseBuilder.cpp:268) parsed block file #435
-INFO - 1478586850: (..\DatabaseBuilder.cpp:268) parsed block file #437
-INFO - 1478586858: (..\DatabaseBuilder.cpp:268) parsed block file #439
-INFO - 1478586878: (..\DatabaseBuilder.cpp:268) parsed block file #441
-INFO - 1478586887: (..\DatabaseBuilder.cpp:268) parsed block file #443
-INFO - 1478586908: (..\DatabaseBuilder.cpp:268) parsed block file #445
-INFO - 1478586916: (..\DatabaseBuilder.cpp:268) parsed block file #447
-INFO - 1478586955: (..\DatabaseBuilder.cpp:268) parsed block file #449
-INFO - 1478586967: (..\DatabaseBuilder.cpp:268) parsed block file #451
-INFO - 1478586988: (..\DatabaseBuilder.cpp:268) parsed block file #453
-INFO - 1478587040: (..\DatabaseBuilder.cpp:268) parsed block file #455
-INFO - 1478587112: (..\DatabaseBuilder.cpp:268) parsed block file #457
-INFO - 1478587134: (..\DatabaseBuilder.cpp:268) parsed block file #459
-INFO - 1478587156: (..\DatabaseBuilder.cpp:268) parsed block file #461
-INFO - 1478587207: (..\DatabaseBuilder.cpp:268) parsed block file #463
-INFO - 1478587268: (..\DatabaseBuilder.cpp:268) parsed block file #465
-INFO - 1478587316: (..\DatabaseBuilder.cpp:268) parsed block file #467
-INFO - 1478587379: (..\DatabaseBuilder.cpp:268) parsed block file #469
-INFO - 1478587396: (..\DatabaseBuilder.cpp:268) parsed block file #471
-INFO - 1478587411: (..\DatabaseBuilder.cpp:268) parsed block file #473
-INFO - 1478587417: (..\DatabaseBuilder.cpp:268) parsed block file #475
-INFO - 1478587462: (..\DatabaseBuilder.cpp:268) parsed block file #477
-INFO - 1478587535: (..\DatabaseBuilder.cpp:268) parsed block file #479
-INFO - 1478587547: (..\DatabaseBuilder.cpp:268) parsed block file #481
-INFO - 1478587594: (..\DatabaseBuilder.cpp:268) parsed block file #483
-INFO - 1478587606: (..\DatabaseBuilder.cpp:268) parsed block file #485
-INFO - 1478587635: (..\DatabaseBuilder.cpp:268) parsed block file #487
-INFO - 1478587681: (..\DatabaseBuilder.cpp:268) parsed block file #489
-INFO - 1478587691: (..\DatabaseBuilder.cpp:268) parsed block file #491
-INFO - 1478587703: (..\DatabaseBuilder.cpp:268) parsed block file #493
-INFO - 1478587723: (..\DatabaseBuilder.cpp:268) parsed block file #495
-INFO - 1478587759: (..\DatabaseBuilder.cpp:268) parsed block file #497
-INFO - 1478587799: (..\DatabaseBuilder.cpp:268) parsed block file #499
-INFO - 1478587874: (..\DatabaseBuilder.cpp:268) parsed block file #501
-INFO - 1478587900: (..\DatabaseBuilder.cpp:268) parsed block file #503
-INFO - 1478587909: (..\DatabaseBuilder.cpp:268) parsed block file #505
-INFO - 1478587942: (..\DatabaseBuilder.cpp:268) parsed block file #507
-INFO - 1478587961: (..\DatabaseBuilder.cpp:268) parsed block file #509
-INFO - 1478587986: (..\DatabaseBuilder.cpp:268) parsed block file #511
-INFO - 1478588022: (..\DatabaseBuilder.cpp:268) parsed block file #513
-INFO - 1478588043: (..\DatabaseBuilder.cpp:268) parsed block file #515
-INFO - 1478588070: (..\DatabaseBuilder.cpp:268) parsed block file #517
-INFO - 1478588087: (..\DatabaseBuilder.cpp:268) parsed block file #519
-INFO - 1478588123: (..\DatabaseBuilder.cpp:268) parsed block file #521
-INFO - 1478588135: (..\DatabaseBuilder.cpp:268) parsed block file #523
-INFO - 1478588151: (..\DatabaseBuilder.cpp:268) parsed block file #525
-INFO - 1478588175: (..\DatabaseBuilder.cpp:268) parsed block file #527
-INFO - 1478588248: (..\DatabaseBuilder.cpp:268) parsed block file #529
-INFO - 1478588278: (..\DatabaseBuilder.cpp:268) parsed block file #531
-INFO - 1478588295: (..\DatabaseBuilder.cpp:268) parsed block file #533
-INFO - 1478588386: (..\DatabaseBuilder.cpp:268) parsed block file #535
-INFO - 1478588405: (..\DatabaseBuilder.cpp:268) parsed block file #537
-INFO - 1478588440: (..\DatabaseBuilder.cpp:268) parsed block file #539
-INFO - 1478588519: (..\DatabaseBuilder.cpp:268) parsed block file #541
-INFO - 1478588535: (..\DatabaseBuilder.cpp:268) parsed block file #543
-INFO - 1478588556: (..\DatabaseBuilder.cpp:268) parsed block file #545
-INFO - 1478588630: (..\DatabaseBuilder.cpp:268) parsed block file #547
-INFO - 1478588651: (..\DatabaseBuilder.cpp:268) parsed block file #549
-INFO - 1478588679: (..\DatabaseBuilder.cpp:268) parsed block file #551
-INFO - 1478588761: (..\DatabaseBuilder.cpp:268) parsed block file #553
-INFO - 1478588778: (..\DatabaseBuilder.cpp:268) parsed block file #555
-INFO - 1478588813: (..\DatabaseBuilder.cpp:268) parsed block file #557
-INFO - 1478588841: (..\DatabaseBuilder.cpp:268) parsed block file #559
-INFO - 1478588862: (..\DatabaseBuilder.cpp:268) parsed block file #561
-INFO - 1478588889: (..\DatabaseBuilder.cpp:268) parsed block file #563
-INFO - 1478588903: (..\DatabaseBuilder.cpp:268) parsed block file #565
-INFO - 1478588928: (..\DatabaseBuilder.cpp:268) parsed block file #567
-INFO - 1478588953: (..\DatabaseBuilder.cpp:268) parsed block file #569
-INFO - 1478588967: (..\DatabaseBuilder.cpp:268) parsed block file #571
-INFO - 1478589026: (..\DatabaseBuilder.cpp:268) parsed block file #573
-INFO - 1478589056: (..\DatabaseBuilder.cpp:268) parsed block file #575
-INFO - 1478589066: (..\DatabaseBuilder.cpp:268) parsed block file #577
-INFO - 1478589083: (..\DatabaseBuilder.cpp:268) parsed block file #579
-INFO - 1478589107: (..\DatabaseBuilder.cpp:268) parsed block file #581
-INFO - 1478589124: (..\DatabaseBuilder.cpp:268) parsed block file #583
-INFO - 1478589142: (..\DatabaseBuilder.cpp:268) parsed block file #585
-INFO - 1478589264: (..\DatabaseBuilder.cpp:268) parsed block file #587
-INFO - 1478589285: (..\DatabaseBuilder.cpp:268) parsed block file #589
-INFO - 1478589307: (..\DatabaseBuilder.cpp:268) parsed block file #591
-INFO - 1478589354: (..\DatabaseBuilder.cpp:268) parsed block file #593
-INFO - 1478589374: (..\DatabaseBuilder.cpp:268) parsed block file #595
-INFO - 1478589427: (..\DatabaseBuilder.cpp:268) parsed block file #597
-INFO - 1478589470: (..\DatabaseBuilder.cpp:268) parsed block file #599
-INFO - 1478589586: (..\DatabaseBuilder.cpp:268) parsed block file #601
-INFO - 1478589603: (..\DatabaseBuilder.cpp:268) parsed block file #603
-INFO - 1478589616: (..\DatabaseBuilder.cpp:268) parsed block file #605
-INFO - 1478589693: (..\DatabaseBuilder.cpp:268) parsed block file #607
-INFO - 1478589726: (..\DatabaseBuilder.cpp:268) parsed block file #609
-INFO - 1478589772: (..\DatabaseBuilder.cpp:268) parsed block file #611
-INFO - 1478589784: (..\DatabaseBuilder.cpp:268) parsed block file #613
-INFO - 1478589814: (..\DatabaseBuilder.cpp:268) parsed block file #615
-INFO - 1478589833: (..\DatabaseBuilder.cpp:268) parsed block file #617
-INFO - 1478589857: (..\DatabaseBuilder.cpp:268) parsed block file #619
-INFO - 1478589889: (..\DatabaseBuilder.cpp:268) parsed block file #621
-INFO - 1478589903: (..\DatabaseBuilder.cpp:268) parsed block file #623
-INFO - 1478589912: (..\DatabaseBuilder.cpp:268) parsed block file #625
-INFO - 1478589933: (..\DatabaseBuilder.cpp:268) parsed block file #627
-INFO - 1478589947: (..\DatabaseBuilder.cpp:268) parsed block file #629
-INFO - 1478589980: (..\DatabaseBuilder.cpp:268) parsed block file #631
-INFO - 1478590006: (..\DatabaseBuilder.cpp:268) parsed block file #633
-INFO - 1478590017: (..\DatabaseBuilder.cpp:268) parsed block file #635
-INFO - 1478590025: (..\DatabaseBuilder.cpp:268) parsed block file #637
-INFO - 1478590094: (..\DatabaseBuilder.cpp:268) parsed block file #639
-INFO - 1478590113: (..\DatabaseBuilder.cpp:268) parsed block file #641
-INFO - 1478590130: (..\DatabaseBuilder.cpp:268) parsed block file #643
-INFO - 1478590167: (..\DatabaseBuilder.cpp:268) parsed block file #645
-INFO - 1478590222: (..\DatabaseBuilder.cpp:268) parsed block file #647
-INFO - 1478590235: (..\DatabaseBuilder.cpp:268) parsed block file #649
-INFO - 1478590260: (..\DatabaseBuilder.cpp:268) parsed block file #651
-INFO - 1478590306: (..\DatabaseBuilder.cpp:268) parsed block file #653
-INFO - 1478590316: (..\DatabaseBuilder.cpp:268) parsed block file #655
-INFO - 1478590359: (..\DatabaseBuilder.cpp:268) parsed block file #657
-INFO - 1478590375: (..\DatabaseBuilder.cpp:268) parsed block file #659
-INFO - 1478590438: (..\DatabaseBuilder.cpp:268) parsed block file #661
-INFO - 1478590455: (..\DatabaseBuilder.cpp:268) parsed block file #663
-INFO - 1478590489: (..\DatabaseBuilder.cpp:268) parsed block file #665
-INFO - 1478590512: (..\DatabaseBuilder.cpp:268) parsed block file #667
-INFO - 1478590529: (..\DatabaseBuilder.cpp:268) parsed block file #669
-INFO - 1478590537: (..\DatabaseBuilder.cpp:268) parsed block file #671
-INFO - 1478591231: (..\DatabaseBuilder.cpp:268) parsed block file #672
-DEBUG - 1478591232: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1478591738: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 9947s
-INFO - 1478591738: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-INFO - 1478591739: (..\BDM_supportClasses.cpp:366) Starting address registration process
-INFO - 1478591754: (..\BlockchainScanner.cpp:650) scanned from height #0 to #142518
-INFO - 1478591760: (..\BlockchainScanner.cpp:650) scanned from height #142519 to #163679
-INFO - 1478591766: (..\BlockchainScanner.cpp:650) scanned from height #163680 to #179799
-INFO - 1478591773: (..\BlockchainScanner.cpp:650) scanned from height #179800 to #184367
-INFO - 1478591781: (..\BlockchainScanner.cpp:650) scanned from height #184368 to #188884
-INFO - 1478591786: (..\BlockchainScanner.cpp:650) scanned from height #188885 to #193618
-INFO - 1478591794: (..\BlockchainScanner.cpp:650) scanned from height #193619 to #197561
-INFO - 1478591802: (..\BlockchainScanner.cpp:650) scanned from height #197562 to #202226
-INFO - 1478591811: (..\BlockchainScanner.cpp:650) scanned from height #202227 to #207989
-INFO - 1478591816: (..\BlockchainScanner.cpp:650) scanned from height #207990 to #211738
-INFO - 1478591824: (..\BlockchainScanner.cpp:650) scanned from height #211739 to #214864
-INFO - 1478591828: (..\BlockchainScanner.cpp:650) scanned from height #214865 to #217567
-INFO - 1478591833: (..\BlockchainScanner.cpp:650) scanned from height #217568 to #220141
-INFO - 1478591839: (..\BlockchainScanner.cpp:650) scanned from height #220142 to #222771
-INFO - 1478591845: (..\BlockchainScanner.cpp:650) scanned from height #222772 to #225055
-INFO - 1478591851: (..\BlockchainScanner.cpp:650) scanned from height #225056 to #228002
-INFO - 1478591859: (..\BlockchainScanner.cpp:650) scanned from height #228003 to #230231
-INFO - 1478591866: (..\BlockchainScanner.cpp:650) scanned from height #230232 to #232697
-INFO - 1478591872: (..\BlockchainScanner.cpp:650) scanned from height #232698 to #235139
-INFO - 1478591877: (..\BlockchainScanner.cpp:650) scanned from height #235140 to #237233
-INFO - 1478591885: (..\BlockchainScanner.cpp:650) scanned from height #237234 to #240031
-INFO - 1478591891: (..\BlockchainScanner.cpp:650) scanned from height #240032 to #243363
-INFO - 1478591895: (..\BlockchainScanner.cpp:650) scanned from height #243364 to #247174
-INFO - 1478591901: (..\BlockchainScanner.cpp:650) scanned from height #247175 to #250677
-INFO - 1478591906: (..\BlockchainScanner.cpp:650) scanned from height #250678 to #253678
-INFO - 1478591911: (..\BlockchainScanner.cpp:650) scanned from height #253679 to #256633
-INFO - 1478591916: (..\BlockchainScanner.cpp:650) scanned from height #256634 to #259826
-INFO - 1478591923: (..\BlockchainScanner.cpp:650) scanned from height #259827 to #262871
-INFO - 1478591930: (..\BlockchainScanner.cpp:650) scanned from height #262872 to #266052
-INFO - 1478591935: (..\BlockchainScanner.cpp:650) scanned from height #266053 to #268842
-INFO - 1478591939: (..\BlockchainScanner.cpp:650) scanned from height #268843 to #270791
-INFO - 1478591944: (..\BlockchainScanner.cpp:650) scanned from height #270792 to #272659
-INFO - 1478591960: (..\BlockchainScanner.cpp:650) scanned from height #272660 to #274880
-INFO - 1478591971: (..\BlockchainScanner.cpp:650) scanned from height #274881 to #277185
-INFO - 1478591979: (..\BlockchainScanner.cpp:650) scanned from height #277186 to #279646
-INFO - 1478591988: (..\BlockchainScanner.cpp:650) scanned from height #279647 to #282116
-INFO - 1478591996: (..\BlockchainScanner.cpp:650) scanned from height #282117 to #284930
-INFO - 1478592007: (..\BlockchainScanner.cpp:650) scanned from height #284931 to #287397
-INFO - 1478592014: (..\BlockchainScanner.cpp:650) scanned from height #287398 to #288980
-INFO - 1478592019: (..\BlockchainScanner.cpp:650) scanned from height #288981 to #290734
-INFO - 1478592025: (..\BlockchainScanner.cpp:650) scanned from height #290735 to #292594
-INFO - 1478592031: (..\BlockchainScanner.cpp:650) scanned from height #292595 to #294598
-INFO - 1478592036: (..\BlockchainScanner.cpp:650) scanned from height #294599 to #296152
-INFO - 1478592044: (..\BlockchainScanner.cpp:650) scanned from height #296153 to #297523
-INFO - 1478592047: (..\BlockchainScanner.cpp:650) scanned from height #297524 to #299260
-INFO - 1478592058: (..\BlockchainScanner.cpp:650) scanned from height #299261 to #301745
-INFO - 1478592066: (..\BlockchainScanner.cpp:650) scanned from height #301746 to #303358
-INFO - 1478592073: (..\BlockchainScanner.cpp:650) scanned from height #303359 to #305208
-INFO - 1478592082: (..\BlockchainScanner.cpp:650) scanned from height #305209 to #306985
-INFO - 1478592090: (..\BlockchainScanner.cpp:650) scanned from height #306986 to #308998
-INFO - 1478592098: (..\BlockchainScanner.cpp:650) scanned from height #308999 to #311234
-INFO - 1478592104: (..\BlockchainScanner.cpp:650) scanned from height #311235 to #312705
-INFO - 1478592110: (..\BlockchainScanner.cpp:650) scanned from height #312706 to #314565
-INFO - 1478592116: (..\BlockchainScanner.cpp:650) scanned from height #314566 to #316104
-INFO - 1478592125: (..\BlockchainScanner.cpp:650) scanned from height #316105 to #318384
-INFO - 1478592131: (..\BlockchainScanner.cpp:650) scanned from height #318385 to #319756
-INFO - 1478592142: (..\BlockchainScanner.cpp:650) scanned from height #319757 to #321089
-INFO - 1478592163: (..\BlockchainScanner.cpp:650) scanned from height #321090 to #323073
-INFO - 1478592170: (..\BlockchainScanner.cpp:650) scanned from height #323074 to #324835
-INFO - 1478592180: (..\BlockchainScanner.cpp:650) scanned from height #324836 to #326600
-INFO - 1478592185: (..\BlockchainScanner.cpp:650) scanned from height #326601 to #328037
-INFO - 1478592197: (..\BlockchainScanner.cpp:650) scanned from height #328038 to #329542
-INFO - 1478592203: (..\BlockchainScanner.cpp:650) scanned from height #329543 to #330584
-INFO - 1478592211: (..\BlockchainScanner.cpp:650) scanned from height #330585 to #332844
-INFO - 1478592218: (..\BlockchainScanner.cpp:650) scanned from height #332845 to #334383
-INFO - 1478592227: (..\BlockchainScanner.cpp:650) scanned from height #334384 to #334733
-INFO - 1478592245: (..\BlockchainScanner.cpp:650) scanned from height #334734 to #335987
-INFO - 1478592250: (..\BlockchainScanner.cpp:650) scanned from height #335988 to #337671
-INFO - 1478592257: (..\BlockchainScanner.cpp:650) scanned from height #337672 to #339091
-INFO - 1478592266: (..\BlockchainScanner.cpp:650) scanned from height #339092 to #340133
-INFO - 1478592272: (..\BlockchainScanner.cpp:650) scanned from height #340134 to #341194
-INFO - 1478592279: (..\BlockchainScanner.cpp:650) scanned from height #341195 to #342481
-INFO - 1478592287: (..\BlockchainScanner.cpp:650) scanned from height #342482 to #343670
-INFO - 1478592308: (..\BlockchainScanner.cpp:650) scanned from height #343671 to #344839
-INFO - 1478592314: (..\BlockchainScanner.cpp:650) scanned from height #344840 to #345617
-INFO - 1478592315: (..\BlockchainScanner.cpp:650) scanned from height #345618 to #345624
-INFO - 1478592327: (..\BlockchainScanner.cpp:650) scanned from height #345625 to #347894
-INFO - 1478592336: (..\BlockchainScanner.cpp:650) scanned from height #347895 to #349336
-INFO - 1478592342: (..\BlockchainScanner.cpp:650) scanned from height #349337 to #350335
-INFO - 1478592350: (..\BlockchainScanner.cpp:650) scanned from height #350336 to #351377
-INFO - 1478592352: (..\BlockchainScanner.cpp:650) scanned from height #351378 to #351627
-INFO - 1478592367: (..\BlockchainScanner.cpp:650) scanned from height #351628 to #353471
-INFO - 1478592374: (..\BlockchainScanner.cpp:650) scanned from height #353472 to #354132
-INFO - 1478592382: (..\BlockchainScanner.cpp:650) scanned from height #354133 to #355733
-INFO - 1478592387: (..\BlockchainScanner.cpp:650) scanned from height #355734 to #356739
-INFO - 1478592394: (..\BlockchainScanner.cpp:650) scanned from height #356740 to #357866
-INFO - 1478592403: (..\BlockchainScanner.cpp:650) scanned from height #357867 to #359078
-INFO - 1478592408: (..\BlockchainScanner.cpp:650) scanned from height #359079 to #359929
-INFO - 1478592414: (..\BlockchainScanner.cpp:650) scanned from height #359930 to #360899
-INFO - 1478592437: (..\BlockchainScanner.cpp:650) scanned from height #360900 to #361686
-INFO - 1478592451: (..\BlockchainScanner.cpp:650) scanned from height #361687 to #362628
-INFO - 1478592456: (..\BlockchainScanner.cpp:650) scanned from height #362629 to #363379
-INFO - 1478592463: (..\BlockchainScanner.cpp:650) scanned from height #363380 to #364362
-INFO - 1478592476: (..\BlockchainScanner.cpp:650) scanned from height #364363 to #365053
-INFO - 1478592497: (..\BlockchainScanner.cpp:650) scanned from height #365054 to #365879
-INFO - 1478592511: (..\BlockchainScanner.cpp:650) scanned from height #365880 to #367176
-INFO - 1478592516: (..\BlockchainScanner.cpp:650) scanned from height #367177 to #367528
-INFO - 1478592526: (..\BlockchainScanner.cpp:650) scanned from height #367529 to #368399
-INFO - 1478592535: (..\BlockchainScanner.cpp:650) scanned from height #368400 to #369017
-INFO - 1478592546: (..\BlockchainScanner.cpp:650) scanned from height #369018 to #369823
-INFO - 1478592551: (..\BlockchainScanner.cpp:650) scanned from height #369824 to #370832
-INFO - 1478592558: (..\BlockchainScanner.cpp:650) scanned from height #370833 to #371951
-INFO - 1478592569: (..\BlockchainScanner.cpp:650) scanned from height #371952 to #372774
-INFO - 1478592586: (..\BlockchainScanner.cpp:650) scanned from height #372775 to #373648
-INFO - 1478592591: (..\BlockchainScanner.cpp:650) scanned from height #373649 to #374121
-INFO - 1478592606: (..\BlockchainScanner.cpp:650) scanned from height #374122 to #374507
-INFO - 1478592614: (..\BlockchainScanner.cpp:650) scanned from height #374508 to #375658
-INFO - 1478592618: (..\BlockchainScanner.cpp:650) scanned from height #375659 to #376531
-INFO - 1478592625: (..\BlockchainScanner.cpp:650) scanned from height #376532 to #377202
-INFO - 1478592643: (..\BlockchainScanner.cpp:650) scanned from height #377203 to #378285
-INFO - 1478592657: (..\BlockchainScanner.cpp:650) scanned from height #378286 to #379440
-INFO - 1478592674: (..\BlockchainScanner.cpp:650) scanned from height #379441 to #380375
-INFO - 1478592680: (..\BlockchainScanner.cpp:650) scanned from height #380376 to #381068
-INFO - 1478592684: (..\BlockchainScanner.cpp:650) scanned from height #381069 to #381734
-INFO - 1478592699: (..\BlockchainScanner.cpp:650) scanned from height #381735 to #382465
-INFO - 1478592705: (..\BlockchainScanner.cpp:650) scanned from height #382466 to #383333
-INFO - 1478592713: (..\BlockchainScanner.cpp:650) scanned from height #383334 to #384008
-INFO - 1478592724: (..\BlockchainScanner.cpp:650) scanned from height #384009 to #385054
-INFO - 1478592729: (..\BlockchainScanner.cpp:650) scanned from height #385055 to #385623
-INFO - 1478592734: (..\BlockchainScanner.cpp:650) scanned from height #385624 to #386304
-INFO - 1478592745: (..\BlockchainScanner.cpp:650) scanned from height #386305 to #387306
-INFO - 1478592754: (..\BlockchainScanner.cpp:650) scanned from height #387307 to #388192
-INFO - 1478592760: (..\BlockchainScanner.cpp:650) scanned from height #388193 to #388290
-INFO - 1478592760: (..\BlockchainScanner.cpp:650) scanned from height #388291 to #388292
-INFO - 1478592763: (..\BlockchainScanner.cpp:650) scanned from height #388293 to #388765
-INFO - 1478592767: (..\BlockchainScanner.cpp:650) scanned from height #388766 to #389116
-INFO - 1478592774: (..\BlockchainScanner.cpp:650) scanned from height #389117 to #389390
-INFO - 1478592789: (..\BlockchainScanner.cpp:650) scanned from height #389391 to #390539
-INFO - 1478592800: (..\BlockchainScanner.cpp:650) scanned from height #390540 to #391463
-INFO - 1478592808: (..\BlockchainScanner.cpp:650) scanned from height #391464 to #392382
-INFO - 1478592824: (..\BlockchainScanner.cpp:650) scanned from height #392383 to #392908
-INFO - 1478592828: (..\BlockchainScanner.cpp:650) scanned from height #392909 to #393539
-INFO - 1478592833: (..\BlockchainScanner.cpp:650) scanned from height #393540 to #393884
-INFO - 1478592850: (..\BlockchainScanner.cpp:650) scanned from height #393885 to #394948
-INFO - 1478592855: (..\BlockchainScanner.cpp:650) scanned from height #394949 to #395202
-INFO - 1478592871: (..\BlockchainScanner.cpp:650) scanned from height #395203 to #396096
-INFO - 1478592894: (..\BlockchainScanner.cpp:650) scanned from height #396097 to #396960
-INFO - 1478592907: (..\BlockchainScanner.cpp:650) scanned from height #396961 to #397425
-INFO - 1478592917: (..\BlockchainScanner.cpp:650) scanned from height #397426 to #398298
-INFO - 1478592923: (..\BlockchainScanner.cpp:650) scanned from height #398299 to #398994
-INFO - 1478592932: (..\BlockchainScanner.cpp:650) scanned from height #398995 to #399554
-INFO - 1478592939: (..\BlockchainScanner.cpp:650) scanned from height #399555 to #399752
-INFO - 1478592950: (..\BlockchainScanner.cpp:650) scanned from height #399753 to #400705
-INFO - 1478592961: (..\BlockchainScanner.cpp:650) scanned from height #400706 to #401440
-INFO - 1478592970: (..\BlockchainScanner.cpp:650) scanned from height #401441 to #402029
-INFO - 1478592980: (..\BlockchainScanner.cpp:650) scanned from height #402030 to #402805
-INFO - 1478592998: (..\BlockchainScanner.cpp:650) scanned from height #402806 to #403707
-INFO - 1478593017: (..\BlockchainScanner.cpp:650) scanned from height #403708 to #404478
-INFO - 1478593028: (..\BlockchainScanner.cpp:650) scanned from height #404479 to #404649
-INFO - 1478593032: (..\BlockchainScanner.cpp:650) scanned from height #404650 to #404734
-INFO - 1478593041: (..\BlockchainScanner.cpp:650) scanned from height #404735 to #405233
-INFO - 1478593051: (..\BlockchainScanner.cpp:650) scanned from height #405234 to #405760
-INFO - 1478593065: (..\BlockchainScanner.cpp:650) scanned from height #405761 to #406228
-INFO - 1478593087: (..\BlockchainScanner.cpp:650) scanned from height #406229 to #406924
-INFO - 1478593109: (..\BlockchainScanner.cpp:650) scanned from height #406925 to #407521
-INFO - 1478593113: (..\BlockchainScanner.cpp:650) scanned from height #407522 to #407997
-INFO - 1478593169: (..\BlockchainScanner.cpp:650) scanned from height #407998 to #408648
-INFO - 1478593176: (..\BlockchainScanner.cpp:650) scanned from height #408649 to #409120
-INFO - 1478593207: (..\BlockchainScanner.cpp:650) scanned from height #409121 to #409270
-INFO - 1478593211: (..\BlockchainScanner.cpp:650) scanned from height #409271 to #409338
-INFO - 1478593230: (..\BlockchainScanner.cpp:650) scanned from height #409339 to #409457
-INFO - 1478593244: (..\BlockchainScanner.cpp:650) scanned from height #409458 to #409648
-INFO - 1478593245: (..\BlockchainScanner.cpp:650) scanned from height #409649 to #409717
-INFO - 1478593277: (..\BlockchainScanner.cpp:650) scanned from height #409718 to #411188
-INFO - 1478593287: (..\BlockchainScanner.cpp:650) scanned from height #411189 to #411501
-INFO - 1478593296: (..\BlockchainScanner.cpp:650) scanned from height #411502 to #411992
-INFO - 1478593305: (..\BlockchainScanner.cpp:650) scanned from height #411993 to #412216
-INFO - 1478593381: (..\BlockchainScanner.cpp:650) scanned from height #412217 to #413373
-INFO - 1478593392: (..\BlockchainScanner.cpp:650) scanned from height #413374 to #413453
-INFO - 1478593434: (..\BlockchainScanner.cpp:650) scanned from height #413454 to #414225
-INFO - 1478593465: (..\BlockchainScanner.cpp:650) scanned from height #414226 to #415017
-INFO - 1478593488: (..\BlockchainScanner.cpp:650) scanned from height #415018 to #415397
-INFO - 1478593492: (..\BlockchainScanner.cpp:650) scanned from height #415398 to #415409
-INFO - 1478593562: (..\BlockchainScanner.cpp:650) scanned from height #415410 to #416520
-INFO - 1478593569: (..\BlockchainScanner.cpp:650) scanned from height #416521 to #417059
-INFO - 1478593603: (..\BlockchainScanner.cpp:650) scanned from height #417060 to #417565
-INFO - 1478593633: (..\BlockchainScanner.cpp:650) scanned from height #417566 to #418052
-INFO - 1478593640: (..\BlockchainScanner.cpp:650) scanned from height #418053 to #418355
-INFO - 1478593689: (..\BlockchainScanner.cpp:650) scanned from height #418356 to #418954
-INFO - 1478593704: (..\BlockchainScanner.cpp:650) scanned from height #418955 to #419286
-INFO - 1478593707: (..\BlockchainScanner.cpp:650) scanned from height #419287 to #419358
-INFO - 1478593719: (..\BlockchainScanner.cpp:650) scanned from height #419359 to #419692
-INFO - 1478593740: (..\BlockchainScanner.cpp:650) scanned from height #419693 to #420175
-INFO - 1478593742: (..\BlockchainScanner.cpp:650) scanned from height #420176 to #420205
-INFO - 1478593748: (..\BlockchainScanner.cpp:650) scanned from height #420206 to #420230
-INFO - 1478593751: (..\BlockchainScanner.cpp:650) scanned from height #420231 to #420272
-INFO - 1478593788: (..\BlockchainScanner.cpp:650) scanned from height #420273 to #420828
-INFO - 1478593805: (..\BlockchainScanner.cpp:650) scanned from height #420829 to #421303
-INFO - 1478593884: (..\BlockchainScanner.cpp:650) scanned from height #421304 to #421987
-INFO - 1478593909: (..\BlockchainScanner.cpp:650) scanned from height #421988 to #422499
-INFO - 1478593969: (..\BlockchainScanner.cpp:650) scanned from height #422500 to #423297
-INFO - 1478593988: (..\BlockchainScanner.cpp:650) scanned from height #423298 to #423675
-INFO - 1478594004: (..\BlockchainScanner.cpp:650) scanned from height #423676 to #424205
-INFO - 1478594006: (..\BlockchainScanner.cpp:650) scanned from height #424206 to #424242
-INFO - 1478594045: (..\BlockchainScanner.cpp:650) scanned from height #424243 to #424987
-INFO - 1478594053: (..\BlockchainScanner.cpp:650) scanned from height #424988 to #425183
-INFO - 1478594072: (..\BlockchainScanner.cpp:650) scanned from height #425184 to #425458
-INFO - 1478594089: (..\BlockchainScanner.cpp:650) scanned from height #425459 to #425850
-INFO - 1478594128: (..\BlockchainScanner.cpp:650) scanned from height #425851 to #426419
-INFO - 1478594189: (..\BlockchainScanner.cpp:650) scanned from height #426420 to #427335
-INFO - 1478594205: (..\BlockchainScanner.cpp:650) scanned from height #427336 to #427522
-INFO - 1478594243: (..\BlockchainScanner.cpp:650) scanned from height #427523 to #428116
-INFO - 1478594266: (..\BlockchainScanner.cpp:650) scanned from height #428117 to #428516
-INFO - 1478594289: (..\BlockchainScanner.cpp:650) scanned from height #428517 to #429259
-INFO - 1478594312: (..\BlockchainScanner.cpp:650) scanned from height #429260 to #429895
-INFO - 1478594328: (..\BlockchainScanner.cpp:650) scanned from height #429896 to #430515
-INFO - 1478594332: (..\BlockchainScanner.cpp:650) scanned from height #430516 to #430730
-INFO - 1478594343: (..\BlockchainScanner.cpp:650) scanned from height #430731 to #431226
-INFO - 1478594350: (..\BlockchainScanner.cpp:650) scanned from height #431227 to #431428
-INFO - 1478594359: (..\BlockchainScanner.cpp:650) scanned from height #431429 to #431816
-INFO - 1478594363: (..\BlockchainScanner.cpp:650) scanned from height #431817 to #432001
-INFO - 1478594369: (..\BlockchainScanner.cpp:650) scanned from height #432002 to #432109
-INFO - 1478594378: (..\BlockchainScanner.cpp:650) scanned from height #432110 to #432527
-INFO - 1478594383: (..\BlockchainScanner.cpp:650) scanned from height #432528 to #432745
-INFO - 1478594427: (..\BlockchainScanner.cpp:650) scanned from height #432746 to #433798
-INFO - 1478594445: (..\BlockchainScanner.cpp:650) scanned from height #433799 to #434383
-INFO - 1478594458: (..\BlockchainScanner.cpp:650) scanned from height #434384 to #434910
-INFO - 1478594467: (..\BlockchainScanner.cpp:650) scanned from height #434911 to #435342
-INFO - 1478594482: (..\BlockchainScanner.cpp:650) scanned from height #435343 to #435903
-INFO - 1478594496: (..\BlockchainScanner.cpp:650) scanned from height #435904 to #436244
-INFO - 1478594507: (..\BlockchainScanner.cpp:650) scanned from height #436245 to #437088
-INFO - 1478594514: (..\BlockchainScanner.cpp:650) scanned from height #437089 to #437752
-INFO - 1478594515: (..\BlockchainScanner.cpp:650) scanned from height #437753 to #437853
-INFO - 1478594516: (..\BlockchainScanner.cpp:225) scanned transaction history in 2776.37s
-INFO - 1478594653: (..\BlockchainScanner.cpp:1560) resolving txhashes
-INFO - 1478595079: (..\BlockchainScanner.cpp:1616) 1766 blocks hit by tx filters
-INFO - 1478595536: (..\BlockchainScanner.cpp:1705) found 1804 missing hashes
-INFO - 1478595536: (..\BlockchainScanner.cpp:1750) Resolved missing hashes in 883.852s
-INFO - 1478595538: (..\BlockchainScanner.cpp:650) scanned from height #437853 to #437853
-INFO - 1478595538: (..\BDM_supportClasses.cpp:480) Done with side scan of wallet
-INFO - 1478625764: (..\BDM_Server.cpp:826) unregistered bdv: a072566614b74ec0c87c
-INFO - 1478625765: (..\BDM_Server.cpp:737) proceeding to shutdown
Interesting, that log write to file only after I shoutdown ArmoryQT (in ArmoryDB application adds this line and next: -INFO - 1478625764: (..\BDM_Server.cpp:826) unregistered bdv: a072566614b74ec0c87c).
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 08, 2016, 05:11:14 PM
ArmoryQt will basically crash in its current state if the underlying communication with ArmoryDB is severed, or ArmoryDB itself hangs. The most likely reason is that Bitcoin is not running, or that ArmoryDB can't connect to it (maybe because it filled up with other nodes).
Let's see a log file if anything. I want dblog.txt in particular.
Title: Re: Armory 0.95.1 is out
Post by: ARXANGEL on November 08, 2016, 05:41:01 PM
I add ArmoryDb logs. I think if you add time in armoryDB log it be more simple to understand timing. It's ArmoryDb freeze. After menu close ArmoryQT they closed and close bitcoind. But ArmoryDB not closed automatic. I need to close it manually (by button close in window ArmoryDB). ArmoryQT logs all day interesting too: ...
2016-11-08 08:09 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-11-08 08:09 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2016-11-08 08:09 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-11-08 08:09 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:26 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 08:27 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
...
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 09:16 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2016-11-08 11:59 (INFO) -- ArmoryQt.py:2886 - Current block number: 437853
2016-11-08 13:47 (WARNING) -- ArmoryQt.py:4935 - Called updateSyncProgress while not sync'ing
2016-11-08 14:20 (WARNING) -- ArmoryQt.py:4935 - Called updateSyncProgress while not sync'ing
2016-11-08 14:42 (WARNING) -- ArmoryQt.py:4935 - Called updateSyncProgress while not sync'ing
2016-11-08 19:52 (WARNING) -- ArmoryQt.py:4935 - Called updateSyncProgress while not sync'ing
2016-11-08 20:22 (INFO) -- ArmoryQt.py:6368 - BDM is safe for clean shutdown
2016-11-08 20:22 (INFO) -- SDM.pyc:588 - Called stopBitcoind
2016-11-08 20:23 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window!
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 08, 2016, 06:17:12 PM
What you see in the Armory log are actual C style time stamps. So there is time, just not human readable =D
I just realized your computer has very little RAM (4GB). It's very possible Core and Armory are fighting over RAM. I'd suggest you reduce the ram usage of ArmoryDB and observe it.
Start ArmoryDB manually, lower the ram use with this command line argument: --ram_usage=1 (defaults to 4). If it's still failing, delete your databases folder, then add this cli arg: --db-type=DB_BARE
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 13, 2016, 11:12:32 PM
Hi Goatpig, first of all thanks for all your work. I am having the same problem with the DB but I have 16Gb of RAM plus 16Gb of memory swap, so I don't think RAM is the problem with this bug. At first it would give me the DB error message. Now I tried a clean start by deleting the .armory file and at this point it won't even launch most of the time. Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2016-11-13 17:34 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2016-11-13 17:34 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2016-11-13 17:34 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2016-11-13 17:34 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 13, 2016, 11:29:57 PM
Let's see dbLog.txt and armorylog.txt in full. What piece of log you isolated is RPC failure, this won't prevent Armory from running on its own.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on November 14, 2016, 02:43:34 AM
951 still shows armorydb window?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 14, 2016, 03:05:42 AM
951 still shows armorydb window?
In Windows, yes. Will take it down for next release.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on November 14, 2016, 03:07:02 AM
951 still shows armorydb window?
In Windows, yes. Will take it down for next release. Thanks great work!
Title: Re: Armory 0.95.1 is out
Post by: visdude on November 15, 2016, 03:29:24 AM
With the above setup, ArmoryQt runs just fine and properly spawns ArmoryDB but with a caveat: an "Armory" folder must still exist at the default location (i.e. C:\Users\username\AppData\Roaming\Armory) because it insists on having the "dblog.txt" file reside there. Otherwise, it hangs as before.
That's quite a different situation here from what I had understood. Are you saying the DB won't put its log file in the explicit datadir? That's a bug, not a design choice. I'll try to reproduce on my end and fix it for the point release. This bug from 0.95 has now been squashed in 0.95.1 ;D. Thanks for the fix.
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 12:44:47 AM
Let's see dbLog.txt and armorylog.txt in full. What piece of log you isolated is RPC failure, this won't prevent Armory from running on its own.
Sorry for the delayed reply. I can't seem to find the dblog.txt, is that also in .armory ? Please click here for the armorylog.txt which is too large for this post: https://dl.dropboxusercontent.com/u/48114501/armorylog.txt (https://dl.dropboxusercontent.com/u/48114501/armorylog.txt)
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 16, 2016, 01:13:24 AM
I can't seem to find the dblog.txt, is that also in .armory ?
It should be. For now, delete /home/rojaslee/armory/databases, then run ArmoryDB from the terminal. Then run ArmoryQt from another terminal instance.
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 01:34:24 AM
Sorry the dblog.txt file is not there for some reason. the armorydb command launched the GUI as well, so when I opened another terminal and ran armoryqt it gave me the following error: rojaslee@debian:~$ armory armoryqt
/usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(ERROR) ArmoryQt.py:6836 - Socket already in use. Sending CLI args to existing proc.
(ERROR) ArmoryQt.py:6840 - Exiting...
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 01:48:42 AM
and, I just had armory close bitcoinQT and the terminal gave me these errors:
https://dl.dropboxusercontent.com/u/48114501/secondLog (https://dl.dropboxusercontent.com/u/48114501/secondLog)
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 16, 2016, 03:19:34 AM
Show me the terminal output when running armorydb.
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 03:24:08 AM
Show me the terminal output when running armorydb.
rojaslee@debian:~$ armory armorydb
/usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) ArmoryQt.py:2233 - Tried to start bitcoind, but satoshi already running
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 03:38:24 AM
and here it is after closing bitcoind
https://dl.dropboxusercontent.com/u/48114501/armorydb2.txt (https://dl.dropboxusercontent.com/u/48114501/armorydb2.txt)
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 16, 2016, 03:44:06 AM
Is this your input when trying to run armorydb?
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 04:00:27 AM
Is this your input when trying to run armorydb? Yes. In both instances that was the command
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 04:17:05 AM
because armorydb alone yields the follwing rojaslee@debian:~$ armorydb
bash: armorydb: command not found
rojaslee@debian:~$
same for armoryDB rojaslee@debian:~$ armoryDB
bash: armoryDB: command not found
rojaslee@debian:~$
Title: Re: Armory 0.95.1 is out
Post by: achow101 on November 16, 2016, 04:39:07 AM
because armorydb alone yields the follwing rojaslee@debian:~$ armorydb
bash: armorydb: command not found
rojaslee@debian:~$
same for armoryDB rojaslee@debian:~$ armoryDB
bash: armoryDB: command not found
rojaslee@debian:~$
What about ArmoryDB (with caps A)? I believe that is actually what the binary is called.
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 12:50:45 PM
Oh, thanks for the correction Goatpig: rojaslee@debian:~$ ArmoryDB
/home/rojaslee
logging in /home/rojaslee/.armory/dbLog.txt
-INFO - 1479300560: (main.cpp:23) Running on 4 threads
-INFO - 1479300560: (main.cpp:24) Ram usage level: 4
-INFO - 1479300560: (BlockUtils.cpp:1338) blkfile dir: /home/rojaslee/.bitcoin/blocks
-INFO - 1479300560: (BlockUtils.cpp:1339) lmdb dir: /home/rojaslee/.armory/databases
-INFO - 1479300560: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1479300560: (BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1479300560: (DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1479300560: (lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO - 1479300560: (DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO - 1479300560: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1479300560: (BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1479300563: (DatabaseBuilder.cpp:268) parsed block file #1
-INFO - 1479300565: (DatabaseBuilder.cpp:268) parsed block file #2
-INFO - 1479300567: (DatabaseBuilder.cpp:268) parsed block file #3
-INFO - 1479300569: (DatabaseBuilder.cpp:268) parsed block file #5
-INFO - 1479300570: (DatabaseBuilder.cpp:268) parsed block file #6
-INFO - 1479300571: (DatabaseBuilder.cpp:268) parsed block file #7
-INFO - 1479300574: (DatabaseBuilder.cpp:268) parsed block file #9
-INFO - 1479300575: (DatabaseBuilder.cpp:268) parsed block file #10
-INFO - 1479300576: (DatabaseBuilder.cpp:268) parsed block file #11
-INFO - 1479300579: (DatabaseBuilder.cpp:268) parsed block file #13
-INFO - 1479300580: (DatabaseBuilder.cpp:268) parsed block file #14
-INFO - 1479300581: (DatabaseBuilder.cpp:268) parsed block file #15
-INFO - 1479300584: (DatabaseBuilder.cpp:268) parsed block file #17
-INFO - 1479300585: (DatabaseBuilder.cpp:268) parsed block file #18
-INFO - 1479300586: (DatabaseBuilder.cpp:268) parsed block file #19
-INFO - 1479300589: (DatabaseBuilder.cpp:268) parsed block file #21
and the log entries keep going, seemingly without stop
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 16, 2016, 04:36:33 PM
Just start armorydb from another terminal now.
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 04:41:31 PM
I capitalized. I assumed you wanted that. rojaslee@debian:~$ ArmoryDB
/home/rojaslee
logging in /home/rojaslee/.armory/dbLog.txt
-INFO - 1479314446: (main.cpp:23) Running on 4 threads
-INFO - 1479314446: (main.cpp:24) Ram usage level: 4
-INFO - 1479314446: (BlockUtils.cpp:1338) blkfile dir: /home/rojaslee/.bitcoin/blocks
-INFO - 1479314446: (BlockUtils.cpp:1339) lmdb dir: /home/rojaslee/.armory/databases
-INFO - 1479314446: (lmdb_wrapper.cpp:388) Opening databases...
-ERROR - 1479314446: (BDM_Server.cpp:953) There is already a process listening on 127.0.0.1:9001
-ERROR - 1479314446: (BDM_Server.cpp:955) ArmoryDB cannot start under these conditions. Shutting down!
-ERROR - 1479314446: (BDM_Server.cpp:956) Make sure to shutdown the conflicting processbefore trying again (most likely another ArmoryDB instance).
rojaslee@debian:~$
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 16, 2016, 05:32:40 PM
Ok I messed up. I want you to run 1 ArmoryDB and 1 ArmoryQt, not 2x ArmoryDB.
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 05:47:25 PM
no problem rojaslee@debian:~$ ArmoryDB
/home/rojaslee
logging in /home/rojaslee/.armory/dbLog.txt
-INFO - 1479318205: (main.cpp:23) Running on 4 threads
-INFO - 1479318205: (main.cpp:24) Ram usage level: 4
-INFO - 1479318205: (BlockUtils.cpp:1338) blkfile dir: /home/rojaslee/.bitcoin/blocks
-INFO - 1479318205: (BlockUtils.cpp:1339) lmdb dir: /home/rojaslee/.armory/databases
-INFO - 1479318205: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1479318205: (BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1479318205: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1479318208: (DatabaseBuilder.cpp:208) Found 439241 headers in db
-INFO - 1479318210: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1479318210: (DatabaseBuilder.cpp:477) Found next block after skipping 297810bytes
-INFO - 1479318211: (DatabaseBuilder.cpp:268) parsed block file #680
-DEBUG - 1479318211: (Blockchain.cpp:242) Organizing chain
-INFO - 1479318211: (DatabaseBuilder.cpp:56) updated HEADERS db in 0.636224s
-INFO - 1479318211: (BlockUtils.cpp:1636) Enabling zero-conf tracking
-INFO - 1479318245: (BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1479318249: (BlockchainScanner.cpp:52) no history to scan
rojaslee@debian:~$ ArmoryQT
bash: ArmoryQT: command not found
rojaslee@debian:~$
output for $ armory ArmoryQT https://dl.dropboxusercontent.com/u/48114501/ArmoryQT2.txt (https://dl.dropboxusercontent.com/u/48114501/ArmoryQT2.txt)
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 16, 2016, 06:26:59 PM
i dont know where you got the idea that armory + some name would have any effect.
Run the following:
ArmoryDB
armory
bitcoin-qt
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 16, 2016, 11:23:51 PM
i dont know where you got the idea that armory + some name would have any effect.
in Debian Linux if you get "command not found" then you usually need to call the name of the program first. Did you want those commands in separate terminals as before? or one after the other in the same terminal?
Title: Re: Armory 0.95.1 is out
Post by: zecashminer on November 17, 2016, 02:33:46 AM
I am still on the last version of the old armory on windows. Will I still be able to keep my wallet on there and for how long before I need to move them?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 17, 2016, 02:57:31 AM
in Debian Linux if you get "command not found" then you usually need to call the name of the program first.
Did you want those commands in separate terminals as before? or one after the other in the same terminal?
These are command names, not command line arguments. All cli arg for armory start with --. If the command is not found, it's just a caps issue or a typo.
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 17, 2016, 01:42:37 PM
sorry for the delay rojaslee@debian:~$ killall armory
armory: no process found
rojaslee@debian:~$ killall bitcoind
rojaslee@debian:~$ killall ArmoryDB
ArmoryDB: no process found
rojaslee@debian:~$ ArmoryDB
/home/rojaslee
logging in /home/rojaslee/.armory/dbLog.txt
-INFO - 1479389728: (main.cpp:23) Running on 4 threads
-INFO - 1479389728: (main.cpp:24) Ram usage level: 4
-INFO - 1479389728: (BlockUtils.cpp:1338) blkfile dir: /home/rojaslee/.bitcoin/blocks
-INFO - 1479389728: (BlockUtils.cpp:1339) lmdb dir: /home/rojaslee/.armory/databases
-INFO - 1479389728: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1479389728: (BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1479389728: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1479389738: (DatabaseBuilder.cpp:208) Found 439278 headers in db
-INFO - 1479389741: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1479389744: (DatabaseBuilder.cpp:268) parsed block file #680
-INFO - 1479389746: (DatabaseBuilder.cpp:268) parsed block file #681
-DEBUG - 1479389746: (Blockchain.cpp:242) Organizing chain
-INFO - 1479389746: (DatabaseBuilder.cpp:56) updated HEADERS db in 4.00843s
-INFO - 1479389746: (BlockUtils.cpp:1636) Enabling zero-conf tracking
-INFO - 1479389759: (BitcoinP2P.cpp:783) Connected to Bitcoin node
rojaslee@debian:~$ armory
/usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(ERROR) SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
(ERROR) SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
(ERROR) SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
(ERROR) SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
(ERROR) SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 351, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
rojaslee@debian:~$
Bitcoin QT is not installed globally so I can't really run it from the terminal like that, or I don't know how to do it. Do you need me to install it globally?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 17, 2016, 07:24:24 PM
-INFO - 1479389759: (BitcoinP2P.cpp:783) Connected to Bitcoin node
Bitcoin was running at least this one time, otherwise the DB wouldn't be able to connect. Bitcoin QT is not installed globally so I can't really run it from the terminal like that, or I don't know how to do it. Do you need me to install it globally?
That's ok, you can cd to the folder and start the Binary yourself. The JSON issue you are getting is that Armory (the client) fails to talk to your Bitcoin node over the RPC. This shouldn't prevent the client from processing further unless auto bitcoind management is enabled, in which case the client wants to query the bitcoind status (through the JSON RPC) to know when it is ready, before moving on. So right now I'm guessing you have auto bitcoind enabled. You have 2 solutions: 1) Turn off auto bitcoind (in File -> Settings in the Armory client) and manage bitcoin-qt yourself. 2) Open this file: /home/rojaslee/.bitcoin/bitcoin.conf and add this line: server=1 Save it and start armory (just client, not the DB).
Title: Re: Armory 0.95.1 is out
Post by: bobbyfisher on November 18, 2016, 03:09:17 AM
Thanks Goatpig
The file /home/rojaslee/.bitcoin/bitcoin.conf was not to be found so I opted to control Bitcoin-QT separately.
Thanks for helping the troubleshoot.
Best wishes
Rod
Title: Re: Armory 0.95.1 is out
Post by: bitpop on November 18, 2016, 06:27:13 AM
ArmoryDB crashed for the second time for me. It seems to only last a day.
-INFO - 1479382764: (..\BlockchainScanner.cpp:650) scanned from height #439366 to #439366
-INFO - 1479382785: (..\BlockchainScanner.cpp:650) scanned from height #439367 to #439367
-INFO - 1479383631: (..\BlockchainScanner.cpp:650) scanned from height #439368 to #439368
-INFO - 1479384608: (..\BlockchainScanner.cpp:650) scanned from height #439369 to #439369
-INFO - 1479387881: (..\BlockchainScanner.cpp:650) scanned from height #439370 to #439370
-ERROR - 1479388818: (..\BitcoinP2P.cpp:865) caught BitcoinP2P_Exception in processDataStackThread: invalid header size
-INFO - 1479388818: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1479388818: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1479388818: (..\BitcoinP2P.cpp:865) caught BitcoinP2P_Exception in processDataStackThread: invalid header size
-ERROR - 1479388820: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1479388820: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-ERROR - 1479388820: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
Title: Re: Armory 0.95.1 is out
Post by: naska21 on November 26, 2016, 10:35:27 AM
Hi.
Is 0.93 capable to sign off line transaction generated by 0.95 or I need to install new version on my off-line machine?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 26, 2016, 11:21:01 AM
Hi.
Is 0.93 capable to sign off line transaction generated by 0.95 or I need to install new version on my off-line machine?
You are fine. You will need to upgrade when 0.96 comes out if you want sign SW transactions. If you do not create try to spend SW outputs, you won't need to upgrade.
Title: Re: Armory 0.95.1 is out
Post by: alomar on November 28, 2016, 05:34:45 AM
will this work in Debian 8.6?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 28, 2016, 06:22:27 AM
will this work in Debian 8.6?
Works on Wheezy, no reason it won't on Jessie.
Title: Re: Armory 0.95.1 is out
Post by: Carlton Banks on November 28, 2016, 11:18:49 AM
will this work in Debian 8.6?
I can confirm it's working for me in Debian 8.6, albeit in a Xen based Virtual Machine.
Title: Re: Armory 0.95.1 is out
Post by: alomar on November 28, 2016, 03:42:48 PM
will this work in Debian 8.6?
Works on Wheezy, no reason it won't on Jessie. sorry for the edge case conditions, but will Armory work with Bitcoin Unlimited?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on November 28, 2016, 05:13:52 PM
sorry for the edge case conditions, but will Armory work with Bitcoin Unlimited?
I'm not aware of any changes in BU that would break compatibility with Armory atm, although I don't follow its development.
Title: Re: Armory 0.95.1 is out
Post by: arulbero on November 28, 2016, 06:12:14 PM
will this work in Debian 8.6?
Works on Wheezy, no reason it won't on Jessie. sorry for the edge case conditions, but will Armory work with Bitcoin Unlimited? Armory 0.94.1 + Bitcoin Unlimited 0.12.1 + Ubuntu 14.10 64 bit is working for me.
Title: Re: Armory 0.95.1 is out
Post by: Ente on November 30, 2016, 11:44:29 PM
Today I tried to import a paperwallet privkey into 0.94.1. It worked (import, not sweep), but I couldn't spend the funds: File "/opt/BitcoinArmory/armoryengine/Transaction.py", line 1054, in __init__
raise KeyDataError('Must give pubkey map for singlesig USTXI!')
armoryengine.ArmoryUtils.KeyDataError: Must give pubkey map for singlesig USTXI! So I upgraded to 0.95.1. Which I can't get to start up. Even with an empty armory user folder, it complains about (ERROR) BDM.py:184 - DB error: /home/user/.bitcoin/blocks is not a valid path My .bitcoin folder is a softlink to a folder on another harddisk, as I ran out of space for the bitcoind blockchain. I set all data to my user and 777 again (before, bitcoind ran on its own user with more strict permissions). Still, I get the same error. Is this a known problem? If it takes too much effort to fix, I'll set up the client-server mode on separated machines right away instead. Also, goatpig, I will need to hug you just for this client-server mode alone! Most awesome softwarefeature of the year! :-) Ente
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 01, 2016, 07:13:28 AM
Today I tried to import a paperwallet privkey into 0.94.1. It worked (import, not sweep), but I couldn't spend the funds: File "/opt/BitcoinArmory/armoryengine/Transaction.py", line 1054, in __init__
raise KeyDataError('Must give pubkey map for singlesig USTXI!')
armoryengine.ArmoryUtils.KeyDataError: Must give pubkey map for singlesig USTXI! So I upgraded to 0.95.1. Which I can't get to start up. Even with an empty armory user folder, it complains about (ERROR) BDM.py:184 - DB error: /home/user/.bitcoin/blocks is not a valid path My .bitcoin folder is a softlink to a folder on another harddisk, as I ran out of space for the bitcoind blockchain. I set all data to my user and 777 again (before, bitcoind ran on its own user with more strict permissions). Still, I get the same error. Is this a known problem? If it takes too much effort to fix, I'll set up the client-server mode on separated machines right away instead. Apparently I messed up. Here is the code checking the folder attributes: https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L1109 and here is the underlying call: https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/DBUtils.cpp#L285 Basically this: testPath(blkFileLocation_, 4); Should be: testPath(blkFileLocation_, 2); However, if you chmod your symlink to 777 and it still doesn't work, it may be that access(2) doesn't play well with symlinks altogether. You have a few solutions to try. First, you should set the 4 to a 2, build and try again. If that fails, comment out the path test line entirely and try again. This is just the code testing that the folder exists, for sanity checks. Lastly, if that still fails, try to point the DB directly to that HDD's path.
Title: Re: Armory 0.95.1 is out
Post by: Ente on December 01, 2016, 10:27:00 AM
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L1109 Basically this: testPath(blkFileLocation_, 4); Should be: testPath(blkFileLocation_, 2); However, if you chmod your symlink to 777 and it still doesn't work, it may be that access(2) doesn't play well with symlinks altogether. You have a few solutions to try. First, you should set the 4 to a 2, build and try again. That symlink was already at 777. Changing "4" to "2" solved it! Thank you, Goatpig! :-) I'll set up that client-server-mode on the weekend, aww yeah! Ente
Title: Re: Armory 0.95.1 is out
Post by: Rampion on December 09, 2016, 11:29:12 AM
Hi.
Is 0.93 capable to sign off line transaction generated by 0.95 or I need to install new version on my off-line machine?
You are fine. You will need to upgrade when 0.96 comes out if you want sign SW transactions. If you do not create try to spend SW outputs, you won't need to upgrade. Is there an easy way to avoid to create SW transactions using an updated (+0.13.1) Bitcoin Core once SW is activated?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 09, 2016, 02:24:28 PM
You have to give payers a SegWit address for them to pay you in that fashion. 0.95 can't create SW outputs. 0.96 let's you choose.
Title: Re: Armory 0.95.1 is out
Post by: alomar on December 14, 2016, 01:56:42 AM
You have to give payers a SegWit address for them to pay you in that fashion. 0.95 can't create SW outputs. 0.96 let's you choose.
if you give them a p2sh address can they send you SW outputs?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 14, 2016, 11:56:16 AM
If the P2SH is a nested SW script, that's the idea.
Title: Re: Armory 0.95.1 is out
Post by: alomar on December 14, 2016, 04:31:10 PM
If the P2SH is a nested SW script, that's the idea.
but if the p2sh address you supply to a sender is standard and doesn't involve a nested SW script, sender could still inadvertently (or intentionally) send you SW outputs since the 3* address is essentially just a hash, no?
Title: Re: Armory 0.95.1 is out
Post by: achow101 on December 14, 2016, 04:49:41 PM
If the P2SH is a nested SW script, that's the idea.
but if the p2sh address you supply to a sender is standard and doesn't involve a nested SW script, sender could still inadvertently (or intentionally) send you SW outputs since the 3* address is essentially just a hash, no? No, that is not how segwit works. The sender does not know whether a p2sh address is for a nested segwit output, a multisig, or some other script. Whatever that is, it does not matter. They will create a normal p2sh output. The receiver must know how to spend from that p2sh output. The p2sh output cannot become a p2wsh (basically segwit p2sh). The sender should not assume that any address that they get should be used as a segwit output and not the normal output format for that type of address.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on December 15, 2016, 10:27:40 AM
If the P2SH is a nested SW script, that's the idea.
but if the p2sh address you supply to a sender is standard and doesn't involve a nested SW script, sender could still inadvertently (or intentionally) send you SW outputs since the 3* address is essentially just a hash, no? No, that is not how segwit works. The sender does not know whether a p2sh address is for a nested segwit output, a multisig, or some other script. Whatever that is, it does not matter. They will create a normal p2sh output. The receiver must know how to spend from that p2sh output. The p2sh output cannot become a p2wsh (basically segwit p2sh). The sender should not assume that any address that they get should be used as a segwit output and not the normal output format for that type of address. So how do we tell senders?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 15, 2016, 01:07:55 PM
So how do we tell senders?
You don't have to tell them anything.
Title: Re: Armory 0.95.1 is out
Post by: achow101 on December 15, 2016, 03:14:05 PM
So how do we tell senders?
You give the sender your p2sh address. That p2sh address will have as its "redeemscript" the segwit script. But the sender does not need to know, nor should they care, what the script of that p2sh address. For all they know, it could be a normal multisig; it does not matter to them. All the sender needs to know is that they are sending to a p2sh address and should send to it as normally done with p2sh addresses.
Title: Re: Armory 0.95.1 is out
Post by: alomar on December 15, 2016, 11:38:05 PM
So how do we tell senders?
You give the sender your p2sh address. That p2sh address will have as its "redeemscript" the segwit script. But the sender does not need to know, nor should they care, what the script of that p2sh address. For all they know, it could be a normal multisig; it does not matter to them. All the sender needs to know is that they are sending to a p2sh address and should send to it as normally done with p2sh addresses. how does the sender know whether to send std outputs or SW outputs to that p2sh address?
Title: Re: Armory 0.95.1 is out
Post by: achow101 on December 16, 2016, 12:15:02 AM
how does the sender know whether to send std outputs or SW outputs to that p2sh address?
A p2sh address specifies that it must always send normal p2sh outputs. There is no need to send a segwit output (and in fact impossible to with p2sh) to a p2sh address. The segwit output is nested as the script of the p2sh address and that is for the receiver to deal with.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 16, 2016, 12:27:27 AM
how does the sender know whether to send std outputs or SW outputs to that p2sh address?
You need to understand how bitcoin outputs are constructed and how they are redeemed, particularly P2SH. The whole point of P2SH is to let the recipient determine the redeem script.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on December 16, 2016, 11:02:08 AM
how does the sender know whether to send std outputs or SW outputs to that p2sh address?
A p2sh address specifies that it must always send normal p2sh outputs. There is no need to send a segwit output (and in fact impossible to with p2sh) to a p2sh address. The segwit output is nested as the script of the p2sh address and that is for the receiver to deal with. But what if he does send segwit and receiver isn't expecting it? Will you have to redeem it with another wallet to recover it?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 16, 2016, 12:15:14 PM
But what if he does send segwit and receiver isn't expecting it?
How would he be doing this? You at least need to know the public keys of your recipient to craft the output yourself. Neither P2PKH nor P2SH output scripts give you that information. Same with the native SW outputs. The only way you got to do this is by lifting the public keys of your recipients known addresses from the blockchain. There is no mechanic in the bitcoin protocol to prevent someone from spending coins to whatever script they want, but that's basically the same as black-holing coins at this point. If you are afraid your wallet will do this with your coins, that's not how it's supposed to work at all.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on December 16, 2016, 12:16:42 PM
But what if he does send segwit and receiver isn't expecting it?
How would he be doing this? You at least need to know the public keys of your recipient to craft the output yourself. Neither P2PKH nor P2SH output scripts give you that information. Same with the native SW outputs. The only way you got to do this is by lifting the public keys of your recipients known addresses from the blockchain. There is no mechanic in the bitcoin protocol to prevent someone from spending coins to whatever script they want, but that's basically the same as black-holing coins at this point. If you are afraid your wallet will do this with your coins, that's not how it's supposed to work at all. Oh ok, then how would he send a segwit? Do I need to give him other info than a 3* address?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 16, 2016, 12:20:48 PM
The address has everything he needs. If he uses that addresses, it will result in a nested SW output on the network.
Title: Re: Armory 0.95.1 is out
Post by: h00per_tr00per on December 25, 2016, 11:23:44 PM
Just tried to verify signatures for this new build on Debian (downloaded from main Armory site), and no dice. I wondered if I had screwed something up, so I downloaded 93.3 from the same place and verified that without difficulty. Both .deb files are in the same directory. Here's the output of how I did it:
h00per@debian-vm:~/Downloads$ dpkg-sig --verify *.deb
Processing armory_0.93.3_ubuntu-64bit.deb...
GOODSIG _gpgbuilder 821F122936BDD565366AC36A4AB16AEA98832223 1447278319
Processing armory_0.95.1_amd64.deb...
h00per@debian-vm:~/Downloads$
Is .95.1 signed in the same way as the other versions? If not, how do I verify the integrity of this file?
Thanks.
Title: Re: Armory 0.95.1 is out
Post by: achow101 on December 25, 2016, 11:38:13 PM
Do you have the right key imported? You need to have goatpig's key, found at https://github.com/goatpig/BitcoinArmory/blob/master/PublicKeys/goatpig-signing-key.asc
Title: Re: Armory 0.95.1 is out
Post by: h00per_tr00per on December 27, 2016, 01:11:23 AM
Do you have the right key imported? You need to have goatpig's key, found at https://github.com/goatpig/BitcoinArmory/blob/master/PublicKeys/goatpig-signing-key.asc
Thanks for the tip -- I didn't realize that goatpig had taken over when I posted my original thing. But since then, I followed the directions on this page: https://btcarmory.com/docs/verify and even after importing the new key it doesn't work -- it appears the .95.1 binary is unsigned. Here's the output now:
h00per@debian-vm:~/Downloads$ sha256sum -c sha256sum.asc armory_0.95.1_amd64.deb
armory_0.95.1_amd64.deb: OK
sha256sum: armory_0.95.1_osx.tar.gz: No such file or directory
armory_0.95.1_osx.tar.gz: FAILED open or read
sha256sum: armory_0.95.1_win64.exe: No such file or directory
armory_0.95.1_win64.exe: FAILED open or read
sha256sum: WARNING: 20 lines are improperly formatted
sha256sum: WARNING: 2 listed files could not be read
sha256sum: armory_0.95.1_amd64.deb: no properly formatted SHA256 checksum lines found
The earlier lines are reasonable -- I didn't download the files for those other versions. But what's up with the .95.1 file?
Title: Re: Armory 0.95.1 is out
Post by: arulbero on December 27, 2016, 10:28:35 AM
New procedure: $ head -4 sha256sum.asc.txt | tail -1 | sha256sum -c or sha256sum -c sha256sum.asc.txt armory_0.94.1_amd64.deb 2>&1 | grep OK
$ wget https://raw.githubusercontent.com/goatpig/BitcoinArmory/master/PublicKeys/goatpig-signing-key.asc
$ gpg --import goatpig-signing-key.asc
$ gpg --verify sha256sum.asc.txt
gpg: Firma eseguita dom 22 nov 2015 07:34:46 CET
gpg: con RSA chiave 8C5211764922589A
gpg: Firma valida da "goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>" [sconosciuto]
gpg: ATTENZIONE: questa chiave non è certificata con una firma fidata.
gpg: Non ci sono indicazioni che la firma appartenga al proprietario.
Impronta digitale chiave primaria: 745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A
or just take a look at: https://btcarmory.com/docs/verify
Title: Re: Armory 0.95.1 is out
Post by: coinbtm on December 29, 2016, 01:51:10 PM
Hello,
First off i'd like to thank goatpig for his continued effort & development on this piece of software! It's great that Alan open sourced it and capable minds are continuing the development. Looking forward to getting this back up and running on a mac laptop here...
Question: is there anyone doing QA on the new 95.1 OSX binaries? I'm facing a string concatenation error when armory tries to load on this machine. Am unsure if it's my system or armory...
Here's the relevant redacted bits from the log file; it will die immediately upon trying to launch the app:
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1137 - C++ block utilities loaded successfully
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:651 - Executing popen: sysctl hw.memsize
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:651 - Executing popen: sysctl -n machdep.cpu.brand_string
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1247 -
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1248 -
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1249 -
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1250 - ************************************************************
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1251 - Invoked: /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1252 - ************************************************************
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1253 - Loading Armory Engine:
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1254 - Armory Version : 0.95.1
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1255 - Armory Build: : None
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1256 - PyBtcWallet Version : 1.35
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1257 - Detected Operating system: MacOSX
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1258 - OS Variant : 10.10.5
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1259 - User home-directory : [REDACTED]
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1260 - Satoshi BTC directory : [REDACTED]/Bitcoin/
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1261 - Armory home dir : [REDACTED]/Armory/
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1262 - Detected System Specs :
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1263 - Total Available RAM : 16.00 GB
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1264 - CPU ID string : Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1265 - Number of CPU cores : 8 cores
2016-12-29 08:22 (INFO) -- ArmoryUtils.py:1266 - System is 64-bit : True
2016-12-29 08:22 (ERROR) -- Traceback (most recent call last):
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 44, in <module>
from armoryengine.ALL import *
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ALL.py", line 8, in <module>
from armoryengine.ArmoryUtils import *
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ArmoryUtils.py", line 1267, in <module>
LOGINFO(' Preferred Encoding : ' + locale.getpreferredencoding())
TypeError: cannot concatenate 'str' and 'NoneType' objects
Which means the getpreferredencoding() method is returning null.... what gives?
This binary was shasum checked & verified
Doing some python sleuthing and tracing back from line 1267 in the utils file, i don't know why this is occurring... it should return back UTF-8 ... see below from a terminal prompt:
Last login: Thu Dec 29 08:17:47 on ttys007
Thu Dec 29 08:36:51 MacBook Pro:~/Desktop/$ python
Python 2.7.9 (default, Dec 19 2014, 21:06:47)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import locale
>>> locale.getpreferredencoding()
'UTF-8'
>>>
anyone have thoughts or ideas? is the armory app using some weird version of python that is not the supplied or system version? do i need to flag it to use a specific flavor in pyenv or similar?
Title: Re: Armory 0.95.1 is out
Post by: achow101 on December 29, 2016, 05:40:35 PM
Question: is there anyone doing QA on the new 95.1 OSX binaries?
Not particularly. IIRC goatpig does not have a mac to do testing with. There is really only one person who contributes mac stuff for Armory. I'm facing a string concatenation error when armory tries to load on this machine. Am unsure if it's my system or armory...
AFAIK, Armory does work on Macs. It could be an issue with mac versions, I don't remember what version Armory was last tested on.
Title: Re: Armory 0.95.1 is out
Post by: coinbtm on December 29, 2016, 06:24:57 PM
I should note this same machine was running armory on 93.3 fine... using the new 95.1 binary is what no longer works...
Title: Re: Armory 0.95.1 is out
Post by: gangtraet on December 29, 2016, 07:20:56 PM
It works fine on my mac (0.95.1), but I am still on El Capitan. However, I know many Macs have problems with all kinds of Linux software because often they set one of the language environment variables wrong. Try typing this in a terminal: and look for any variables with a value of UTF-8 or the like. They should be en_US.UTF-8 or something like that. A bare value of utf8, UTF8, utf-8 or similar is incorrect and could potentially cause the problem you see.
Title: Re: Armory 0.95.1 is out
Post by: Stroto on December 29, 2016, 08:58:07 PM
Ok I installed 0.95.1 and everything is cool, a few hiccups with installing but nothing that couldn't be solved.
I like that I (easily) can manage the sat/b without having to work around and calculate it myself, Thank You Goatpig for that.
Just a simple question, maybe i just missed a setting somewhere. Now I need to press sat/b for every transaction and put the right amount in (chosing between normal or fast on https://bitcoinfees.21.co/). Is there anyway to have sat/b per default selected with a given amount in the settings? Like we can fill in our own default fee per tx?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 29, 2016, 11:04:47 PM
Question: is there anyone doing QA on the new 95.1 OSX binaries?
Not particularly. IIRC goatpig does not have a mac to do testing with. There is really only one person who contributes mac stuff for Armory. I'm facing a string concatenation error when armory tries to load on this machine. Am unsure if it's my system or armory...
AFAIK, Armory does work on Macs. It could be an issue with mac versions, I don't remember what version Armory was last tested on. I personally debugged 0.95 on Mac. I believe it was on El Capitan. Is there anyway to have sat/b per default selected with a given amount in the settings? Like we can fill in our own default fee per tx?
Next version.
Title: Re: Armory 0.95.1 is out
Post by: btc123thatthere on December 30, 2016, 09:27:28 AM
Any chance of a 32-bit version 0.95.1?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 30, 2016, 09:28:55 AM
Any chance of a 32-bit version 0.95.1?
No. If you want an offline signer in x86, you can use all the way back to 0.92 to sign with 0.95. If you want to go online with an x86 system, you should reconsider that plan to begin with.
Title: Re: Armory 0.95.1 is out
Post by: coinbtm on December 31, 2016, 12:06:46 AM
So, I just tried 93.3 app version and it loaded up fine.... tried the 95.1 again and it's still no dice... same error each time in the log file, this appears to be something to do with the locale not reporting back correctly which gives back a null value and python cannot concatenate a null value with the first part of the string for the logger function... so it breaks
tried it even on another mac that is 10.12.2; same issues... won't load...
out of pure curiosity, i went to the github releases and downloaded 95.0, verified the signature, and tried that one..... this one loads the application window, but hangs on the scanning transaction history... so now i have 3 apps in my applications dir, named: armory951 armory933 and armory95 -- only the latter 2 will load the app... the 951 version will not load at all... with 933 being the only one that actually works...
any ideas?
the 95.0 version in the dblog.txt file shows this as what i perceive to be the error:
Log file opened at 1483142525: /Users/[REDACTED]/Library/Application Support/Armory/dbLog.txt
-INFO - 1483142525: (main.cpp:22) Running on 8 threads
-INFO - 1483142525: (main.cpp:23) Ram usage level: 4
-INFO - 1483142525: (BlockUtils.cpp:1325) blkfile dir: /Users/[REDACTED]/Library/Application Support/Bitcoin/blocks
-INFO - 1483142525: (BlockUtils.cpp:1326) lmdb dir: /Users/[REDACTED]/Library/Application Support/Armory/databases
-INFO - 1483142525: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1483142525: (BlockUtils.cpp:1508) Executing: doInitialSyncOnLoad
-INFO - 1483142525: (BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1483142525: (DatabaseBuilder.cpp:162) Reading headers from db
-ERROR - 1483142525: (StoredBlockObj.cpp:538) buffer is too small: 0 bytes. expected: 106
-ERROR - 1483142525: (BDM_mainthread.cpp:255) BDM thread failed: buffer is too small: 0 bytes. expected: 106
-INFO - 1483142526: (BDM_Server.cpp:797) registered bdv: 5776646e8dbcfba46b0a
-INFO - 1483142526: (BDM_supportClasses.cpp:366) Starting address registration process
-ERROR - 1483142526: (lmdb_wrapper.cpp:1205) Block height exceeds DupID lookup table
-ERROR - 1483142526: (lmdb_wrapper.cpp:1419) Headers DB has no block at height: 4294967295
-ERROR - 1483142526: (lmdb_wrapper.cpp:1399) No headers at height 4294967295
-ERROR - 1483142526: (BlockchainScanner.cpp:204) failed to grab block data starting height: 0
-ERROR - 1483142526: (BlockchainScanner.cpp:206) no block data was scanned
Ideally i'd like the 95.1 version to work which is the original problem with the python locale not working....
Is there something that got messed up in the osx build process that made the binaries maybe?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on December 31, 2016, 09:02:05 AM
https://bitcointalk.org/index.php?topic=1732805.msg17343825#msg17343825
Title: Re: Armory 0.95.1 is out
Post by: coinbtm on December 31, 2016, 03:30:34 PM
Many thanks,
That got me able to load the app, which then complained about a dbdir mismatch, which i found was because of an errant process that needed to be killed, which allowed me to finally get this puppy running.
tweaking the file with the try catch logic on that logger line and also making sure armorydb process doesnt exist when trying to load are key to getting 95.1 working properly
+1 for the tips
~All the best
Title: Re: Armory 0.95.1 is out
Post by: arulbero on January 01, 2017, 01:51:27 PM
Bitcoin Core 0.13.1, blockchain completely synched, Armory 0.95.1 fresh installation, Ubuntu 16.10. Just a little glitch: if I execute only ArmoryDB, it fails because /home/antonio/.armory doesn't exist and it gets stuck on this error: antonio@ubuntu:~$ ls .armory
ls: impossibile accedere a '.armory': File o directory non esistente
antonio@ubuntu:~$ /usr/bin/ArmoryDB
/home/antonio
/home/antonio/.armory is not a valid path
logging in /home/antonio/.armory/dbLog.txt
-INFO - 1483277052: (main.cpp:23) Running on 1 threads
-INFO - 1483277052: (main.cpp:24) Ram usage level: 4
antonio@ubuntu:~$ ls .armory
ls: impossibile accedere a '.armory': File o directory non esistente
"logging in /home/antonio/.armory/dbLog.txt" is then a false message. If I manually create only the .armory directory (not the databases subdirectory), then is ok: antonio@ubuntu:~$ mkdir .armory/
antonio@ubuntu:~$ ls .armory/
antonio@ubuntu:~$ /usr/bin/ArmoryDB
/home/antonio
/home/antonio/.armory/databases is not a valid path
logging in /home/antonio/.armory/dbLog.txt
-INFO - 1483277785: (main.cpp:23) Running on 1 threads
-INFO - 1483277785: (main.cpp:24) Ram usage level: 4
-INFO - 1483277785: (BlockUtils.cpp:1338) blkfile dir: /home/antonio/.bitcoin/blocks
-INFO - 1483277785: (BlockUtils.cpp:1339) lmdb dir: /home/antonio/.armory/databases
-INFO - 1483277785: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1483277785: (BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1483277785: (DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1483277785: (lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO - 1483277785: (DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO - 1483277785: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1483277792: (DatabaseBuilder.cpp:268) parsed block file #0
-INFO - 1483277796: (DatabaseBuilder.cpp:268) parsed block file #1
-INFO - 1483277801: (DatabaseBuilder.cpp:268) parsed block file #2
-INFO - 1483277804: (DatabaseBuilder.cpp:268) parsed block file #3
-INFO - 1483277808: (DatabaseBuilder.cpp:268) parsed block file #4
-INFO - 1483277812: (DatabaseBuilder.cpp:268) parsed block file #5
-INFO - 1483277815: (DatabaseBuilder.cpp:268) parsed block file #6
-INFO - 1483277819: (DatabaseBuilder.cpp:268) parsed block file #7
.....
-INFO - 1483284971: (DatabaseBuilder.cpp:268) parsed block file #726
-DEBUG - 1483284972: (Blockchain.cpp:242) Organizing chain
-INFO - 1483284982: (DatabaseBuilder.cpp:56) updated HEADERS db in 7197s
-INFO - 1483284982: (BlockUtils.cpp:1636) Enabling zero-conf tracking
antonio@ubuntu:~$ ls .armory/
databases dbLog.txt
The warning "/home/antonio/.armory/databases is not a valid path" in this case is only a warning, and Armory resolves the issue by itself. Question #1: is it ok to terminate ArmoryDB with "CTRL + C" ? I didn't figure out another way. Question #2: now if I execute /usr/bin/armory (after quitting ArmoryDB and Bitcoin Core), I get: File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2017-01-01 17:20 (ERROR) -- SDM.py:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 765, in __backgroundRequestTopBlock
numblks = self.proxy.getinfo()['blocks']
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 105, in __call__
resp = json.loads(resp, parse_float=decimal.Decimal)
File "/usr/lib/python2.7/json/__init__.py", line 352, in loads
return cls(encoding=encoding, **kw).decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
and the program gets stuck. I need instead to use the three commands: - /usr/bin/local/bitcoind --daemon
- /usr/bin/ArmoryDB
- python2 /usr/lib/armory/ArmoryQt.py
to make Armory work. Why?
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on January 02, 2017, 06:35:42 PM
Anyone has a recent size number of GB one needs right now for using Armory (to check wallets). Is it really 100 Gb now (counting the blockchain download of bitcoin core) or has this been streamlined somehow ? Thanks
Title: Re: Armory 0.95.1 is out
Post by: Holliday on January 02, 2017, 06:39:32 PM
Anyone has a recent size number of GB one needs right now for using Armory (to check wallets). Is it really 100 Gb now (counting the blockchain download of bitcoin core) or has this been streamlined somehow ? Thanks
You need to have the full block chain in order to use Armory online. A Bitcoin Core install with full sync is just over 100GB. Armory no longer duplicates the block chain data, so as long as you can hold the entire block chain, you should be good to go.
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on January 02, 2017, 06:47:59 PM
Anyone has a recent size number of GB one needs right now for using Armory (to check wallets). Is it really 100 Gb now (counting the blockchain download of bitcoin core) or has this been streamlined somehow ? Thanks
You need to have the full block chain in order to use Armory online. A Bitcoin Core install with full sync is just over 100GB. Armory no longer duplicates the block chain data, so as long as you can hold the entire block chain, you should be good to go. Thanks 100 GB !!! Last time I'm using Armoury after this if I manage. Will forward all the bitcoins to another client that doesn't require full download of the blockchain for sure !!!!
Title: Re: Armory 0.95.1 is out
Post by: Carlton Banks on January 02, 2017, 07:06:54 PM
Thanks 100 GB !!! Last time I'm using Armoury after this if I manage. Will forward all the bitcoins to another client that doesn't require full download of the blockchain for sure !!!!
As long as you don't mind the privacy downgrade, and don't want to contribute to helping the Bitcoin network any more, then that's the correct decision.
Title: Re: Armory 0.95.1 is out
Post by: totalanni on January 03, 2017, 12:50:49 AM
Any chance of a 32-bit version 0.95.1?
No. If you want an offline signer in x86, you can use all the way back to 0.92 to sign with 0.95. If you want to go online with an x86 system, you should reconsider that plan to begin with. Has nothing changed with the online/offline signing? If so, then why does my device not sign anymore? :(
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 03, 2017, 01:02:59 AM
Has nothing changed with the online/offline signing?
If so, then why does my device not sign anymore? :(
I would need to see the logs.
Title: Re: Armory 0.95.1 is out
Post by: totalanni on January 03, 2017, 01:53:00 AM
my device doesnt log.
It just doesnt sign anymore.
I was using this, remember.
https://bitcointalk.org/index.php?topic=870014.0
Title: Re: Armory 0.95.1 is out
Post by: achow101 on January 03, 2017, 01:55:44 AM
my device doesnt log.
Armory creates log files for debugging purposes. We need to see those. Often times something going wrong will result in an error being written to the log file. It just doesnt sign anymore.
Signing and logging are two separate things not related to each other.
Title: Re: Armory 0.95.1 is out
Post by: totalanni on January 03, 2017, 02:03:17 AM
Armory creates an .unsigned.tx that is saved to a sd card and transfered my device to be signed.
When i go to sign it, MY device does not output logs.
I completely understand what you are saying.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 03, 2017, 11:06:35 AM
my device doesnt log.
It just doesnt sign anymore.
I was using this, remember.
https://bitcointalk.org/index.php?topic=870014.0
I know what you are using. My point is without logs, I can't do anything.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on January 11, 2017, 01:38:32 PM
I have a problem installing the latest armoy version on a fresh installed Win10 Prof
Every time I try to create a new wallet the application "armoryQt.exe" does no longer work and I can only close it.
This happens after entering my passphrase the third time (Step 3: Verify Passphrase). Any idea why this happens?
Thank you
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 01:46:30 PM
Post your logs.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on January 11, 2017, 02:04:44 PM
Post your logs.
You can find the log here (https://dl.dropboxusercontent.com/u/7416262/armorylog.txt). Thank you!
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 02:22:28 PM
Delete the log, start Armory in offline mode and try again. If it fails, post the fresh log.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on January 11, 2017, 03:39:53 PM
Delete the log, start Armory in offline mode and try again. If it fails, post the fresh log.
Here is the error screen: https://dl.dropboxusercontent.com/u/7416262/20170111%20-%20Armory%20Offline.PNG And here come the log: https://dl.dropboxusercontent.com/u/7416262/armorylog.txt Thank you!
Title: Re: Armory 0.95.1 is out
Post by: rastapopoulos on January 11, 2017, 04:28:04 PM
Can I sign created transaction with this new release 0.95.1 using an offline version 0.93.3 ?
Do you plan to make an updated standalone / offline bundle, dedicated to cold storage and offline signature, compatible with a more recent OS than ubuntu 12.04 ? (like a 16.04 LTS or tails 2.9) ?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 04:30:07 PM
2017-01-11 16:34 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
You didn't start Armory in offline mode, it just happens to be offline because it failed to auto start bitcoind. Let's take it from the top. 1) Make sure no instance of ArmoryDB.exe is running. If there are, just kill the process in the task manager. 2) Create a shortcut of ArmoryQt.exe. In the shortcut properties, add this to the target field:"--offline", then rename the shortcut to something like "Armory offline". Your target should look like this: C:\Program Files (x86)\Armory\ArmoryQt.exe --offline
3) Delete your log file again, the constant RPC errors make it hard to make sense of anything. 4) Start Armory through the offline shortcut, repeat the process. P.S: is there an ArmoryQt.exe.log file in C:\Program Files (x86)\Armory ? If so, post it.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 04:55:59 PM
Can I sign created transaction with this new release 0.95.1 using an offline version 0.93.3 ?
Yes Do you plan to make an updated standalone / offline bundle, dedicated to cold storage and offline signature, compatible with a more recent OS than ubuntu 12.04 ? (like a 16.04 LTS or tails 2.9) ?
I have not built any offline bundle myself. These are just carryovers from the ATI era, since I have not changed the signing code yet. There is new signer code to cover the new address types for 0.96. This code is only active when spending from the new address types, this means you can use the old offline signers to sign for the legacy addresses funded with 0.96 and later. If you use the new address formats, you'll need a 0.96+ signer. For that purpose I'll put out a new set of offline bundles. Offline bundles aren't just builds however. They come with the packages needed to install Armory offline on the fresh install of the target OS. Assembling and testing the packages is a demanding task on its own, which is why you won't see offline bundles for every release, and only a few OS supported. I use a different process than Alan for builds however. For each package, he would build the binaries directly on the target OS. I build all *nix binaries on Debian Wheezy. These binaries are compatible with everything Debian x64 based. This leaves the question of OSes and arch. Obviously there will be at least one Ubuntu LTS. Other OSes are still up in the air atm. As for Tails, afaik they run on Debian Jessie, so a Jessie offline bundle should work, although I believe they use x86 and not x64, which is annoying in its own right.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on January 11, 2017, 06:05:03 PM
2017-01-11 16:34 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
You didn't start Armory in offline mode, it just happens to be offline because it failed to auto start bitcoind. Let's take it from the top. 1) Make sure no instance of ArmoryDB.exe is running. If there are, just kill the process in the task manager. 2) Create a shortcut of ArmoryQt.exe. In the shortcut properties, add this to the target field:"--offline", then rename the shortcut to something like "Armory offline". Your target should look like this: C:\Program Files (x86)\Armory\ArmoryQt.exe --offline
3) Delete your log file again, the constant RPC errors make it hard to make sense of anything. 4) Start Armory through the offline shortcut, repeat the process. P.S: is there an ArmoryQt.exe.log file in C:\Program Files (x86)\Armory ? If so, post it. Hello, thank you very much for this detailed explanation. I think this time the offline mode worked, but it crashes the same moment (Step 3 on creating a wallet). Here is the log file (I overwrite it every time): https://dl.dropboxusercontent.com/u/7416262/armorylog.txt There is no .log-file in C:\Program Files (x86)\Armory Greetings! Edit: If helpful I could give you Teamviewer access.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 06:10:46 PM
I'll try to reproduce on my own, although I doubt I will manage. You are the first one to report an issue of this nature on 0.95, and there has not been significant changes in that code across versions to justify such failure.
Maybe try to run offline Armory with admin privilege, in the off case it is a permission issue.
Also teamviewer on its own won't help, as I'd need to install a whole suite of development tools to debug the issue.
P.S: Give it a try in testnet by adding --testnet to the offline shortcut target
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on January 11, 2017, 06:23:55 PM
I'll try to reproduce on my own, although I doubt I will manage. You are the first one to report an issue of this nature on 0.95, and there has not been significant changes in that code across versions to justify such failure.
Maybe try to run offline Armory with admin privilege, in the off case it is a permission issue.
Also teamviewer on its own won't help, as I'd need to install a whole suite of development tools to debug the issue.
P.S: Give it a try in testnet by adding --testnet to the offline shortcut target
Adding --testnet and starting with admin privileges does not change it: https://dl.dropboxusercontent.com/u/7416262/armorylog-testnet.txt It only creates a subfolder "testnet3" where the log files are located. It is a clean Win10 Prof Installation, only Windows updates so far, beside the Bitcoin Client + Armory. It is installed on a virtual machine since I only want to start it when access to my wallet is required. Win10 is also activated. I could try another version of armory if this could help. I have an older version of armory installed on my notebook and I would like to import those wallets into this Virtual Machine once it is working. Kind regards
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 06:38:53 PM
Are you using non ascii characters in your password? Try creating a wallet with a very simple password for testing purposes.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on January 11, 2017, 06:52:28 PM
Are you using non ascii characters in your password? Try creating a wallet with a very simple password for testing purposes.
It happens with the password "123456" as well :( If you think it could solve it a reinstall of windows would be no big thing.
Title: Re: Armory 0.95.1 is out
Post by: achow101 on January 11, 2017, 07:06:35 PM
Is the OS 32 bit or 64 bit?
Since you are using a virtual machine, you should try allocating it more than 1 core.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 07:08:35 PM
If you think it could solve it a reinstall of windows would be no big thing.
I don't think it would achieve anything. Do you build your own binaries? I'd have you test it with 0.96
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on January 11, 2017, 07:41:57 PM
If you think it could solve it a reinstall of windows would be no big thing.
I don't think it would achieve anything. Do you build your own binaries? I'd have you test it with 0.96 No, I don't. I just downloaded the installer version from armory website
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 11, 2017, 07:44:18 PM
Then your immediate solution is to install/VM a Debian based Linux distro to create your wallets with. Otherwise, you'll have to wait for the 0.96 testing phase to participate and help me debug the issue if it has persisted until then.
Title: Re: Armory 0.95.1 is out
Post by: Aurik on January 22, 2017, 10:34:21 AM
Any Idea when 0.96 will be released?
A vage timeframe would be enought Informationen
like "within a month" or "somewhat between 30 and 90 days"
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 22, 2017, 11:41:00 AM
Ideally it will go in testing sometimes during the upcoming week.
Title: Re: Armory 0.95.1 is out
Post by: iCan on January 22, 2017, 11:48:06 AM
Hi I have a problem on MacOS Sierra 10.12.3 with Armory 0.95.1. It doesn't launch at all. Just jump 3-4 times in doc and disappear. I have no idea where to dig to fix this problem. Can u help me? Edit: Armory definitely works for me on 10.12.2. Just sent and received coins today, actually. :) That said, can you do me a favor? Go to /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ and edit ArmoryUtils.py at Line 1267. Once saved, start Armory and see if it finishes starting up. Old: LOGINFO(' Preferred Encoding : ' + locale.getpreferredencoding())New: prefEnc = locale.getpreferredencoding()
if prefEnc == None:
if os.environ.get('LC_ALL', '').upper() == 'UTF-8':
prefEnc = 'utf-8'
else:
prefEnc = 'Unknown'
LOGINFO(' Preferred Encoding : ' + prefEnc) : Added a suggested fix. I found out this solution but it doesn't help. Same problem. And my log file is clear... no problem report's at all
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 22, 2017, 08:25:31 PM
Ask droark, I don't do OSX.
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on January 25, 2017, 11:14:18 AM
Hi, trying to verify ubuntu download as per instructions on your site (https://www.bitcoinarmory.com/download/)
When I get to this step:
$ dpkg-sig --verify *.deb > Processing armory_0.85-beta_amd64.deb... > GOODSIG _gpgbuilder 821F122936BDD565366AC36A4AB16AEA**98832223** 1353699840
I only get:
dpkg-sig --verify *.deb
Processing armory_0.95.1_amd64.deb...
not the part after that "> GOODSIG..."
Please help, using Ubuntu 14.04
Thanks
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 25, 2017, 11:44:21 AM
Armory hasn't been signed like this in a long time.
Follow this guide instead:
https://btcarmory.com/docs/verify
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on January 27, 2017, 11:17:42 AM
Armory hasn't been signed like this in a long time.
Follow this guide instead:
https://btcarmory.com/docs/verify
Thanks for the information. Having a different web address than: https://www.bitcoinarmory.com/download/ makes this a bit scary. Shouldn't this information be on that page? Which is the official armory site ? Hope you understand my fear. One question also: If I install armory on ubuntu, do I also have to install bitcoin core first or will armory do that for me?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 27, 2017, 12:01:55 PM
Thanks for the information.
Having a different web address than: https://www.bitcoinarmory.com/download/
makes this a bit scary. Shouldn't this information be on that page? Which is the official armory site ?
Hope you understand my fear.
https://bitcointalk.org/index.php?topic=1588510.0 This stickied btw. As for why the site for my fork doesn't use the old domain: that domain belongs to ATI, the former Armory maintainer. One question also: If I install armory on ubuntu, do I also have to install bitcoin core first or will armory do that for me?
There was code in ATI's Armory (up to 0.93.x) that phoned home. During that process, it would grab the links to the latest Core version, download and install if for you. The phone home server is down and that bit won't work anymore. As for my versions of Armory (0.94+), I've gotten rid of all phone home code to begin with.
Title: Re: Armory 0.95.1 is out
Post by: 2NIzko on January 28, 2017, 12:14:05 PM
Hi goatpig,
I am having big problems with armory 95.1 on Ubuntu 64bit 16.04.
Firstly, running armory while it opens bitcoind itself, gives the errors that others have posted on here which is:
'No JSON object could be decoded' in the armorylog.txt
as well as constant errors in bitcoin debug.log file such as:
'ThreadRPCServer incorrect password attempt from 127.0.0.1:36132'
So i tried to run armory by itself after running bitcoind manually, it scans transaction history and freezes at 97% all the time.
I deleted the armory DB folder, and when restarting armory (while bitcoind is running), it will eventually freeze again at a different %, at a specific block everytime (as far as i can see in the dbLog.txt).
If i repeat this process again, and if i let it run, it would eventually finish, but the block it was stuck on will show at the bottom right hand corner of armory, the block it always freezes on. So in other words, it is not up to date or does not communicate with bitcoind blocks.
Please help and tell me what i can do to solve this issue? should i revert back to armory 93.3?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on January 28, 2017, 02:11:48 PM
Multiple possibilities. Could be bad block data, unstable CPU, running out of RAM, some unknown bug.
You should create your own thread and post armorylog.txt and dbLog.txt. This thread is too long to track this issue here.
Title: Re: Armory 0.95.1 is out
Post by: accounthacked_yuriygeorge on January 31, 2017, 06:42:10 AM
Apologies if this has been asked, I searched around but didn't find.
I updated Bitcoin core to v0.13.99.0-d2c9e4d, but am still on armory 0.93.3.
Getting ready to upgrade to 0.95.1, but after loading up Armory, I still see all my wallets/offline lockboxes/multi-signature wallets and balances are correct.
Can I still use Armory 0.93.3 to sign transactions (with core 0.13 running), and create multi-sig (requires offline signing) transactions? Any danger in at least trying this to see if it works? Thanks!
Title: Re: Armory 0.95.1 is out
Post by: 2NIzko on January 31, 2017, 12:19:54 PM
Multiple possibilities. Could be bad block data, unstable CPU, running out of RAM, some unknown bug.
You should create your own thread and post armorylog.txt and dbLog.txt. This thread is too long to track this issue here.
The problem got solved. While armory was stuck at some percentage everytime (from deleting the DB completely from armory folder), what i did was, killed the armory process and ArmoryDB as well. Restarted it and it started syncing properly with bitcoind. So the above problem only happens when deleting the database folder in armory folder and starting it from scratch, it will reach a certain percentage and freeze at scanning transaction history. The other problem is that i cannot let armory open bitcoind itself, otherwise i get RPC username and password errors. Currently i am running them separately. I really hope that the newer version runs bitcoind on its own by using cookie like you mentioned in your posts. Thanks
Title: Re: Armory 0.95.1 is out
Post by: achow101 on January 31, 2017, 01:47:27 PM
Apologies if this has been asked, I searched around but didn't find.
I updated Bitcoin core to v0.13.99.0-d2c9e4d, but am still on armory 0.93.3.
Getting ready to upgrade to 0.95.1, but after loading up Armory, I still see all my wallets/offline lockboxes/multi-signature wallets and balances are correct.
Can I still use Armory 0.93.3 to sign transactions (with core 0.13 running), and create multi-sig (requires offline signing) transactions? Any danger in at least trying this to see if it works? Thanks!
Yes, 0.93.3 still works. It is recommended that you upgrade so that you can benefit from the reduced database size and better performance.
Title: Re: Armory 0.95.1 is out
Post by: accounthacked_yuriygeorge on February 01, 2017, 01:58:30 AM
Yes, 0.93.3 still works. It is recommended that you upgrade so that you can benefit from the reduced database size and better performance.
Sweet, thanks. On a similar note, if I update Armory to 0.95.1 to my online computer, but keep my offline computer at 0.93.3, will I be able to still use multi-sig across both versions (online at 0.95.1 multi-signing with offline 0.93.3 armory)?
Title: Re: Armory 0.95.1 is out
Post by: achow101 on February 01, 2017, 02:37:12 AM
Yes, 0.93.3 still works. It is recommended that you upgrade so that you can benefit from the reduced database size and better performance.
Sweet, thanks. On a similar note, if I update Armory to 0.95.1 to my online computer, but keep my offline computer at 0.93.3, will I be able to still use multi-sig across both versions (online at 0.95.1 multi-signing with offline 0.93.3 armory)? Yes.
Title: Re: Armory 0.95.1 is out
Post by: Aurik on February 03, 2017, 02:38:25 PM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
Title: Re: Armory 0.95.1 is out
Post by: achow101 on February 03, 2017, 02:58:39 PM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
He is in favor of segwit. The next version of Armory will have segwit support.
Title: Re: Armory 0.95.1 is out
Post by: Aurik on February 03, 2017, 03:11:36 PM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
He is in favor of segwit. The next version of Armory will have segwit support. Doesn't have to mean the same. I also follow every rule of law even if i do not like them...
Title: Re: Armory 0.95.1 is out
Post by: achow101 on February 03, 2017, 03:54:11 PM
A little OT but very short question:
Are you (goatpig) in favor of Segwit / Neutral / in favor of BU ?
I have my own opinion, but also wanna hear from someone who actually has knowledge about code and stuff.
If u have the time you can comment on your opinion, or just give the answer without any explanation.
He is in favor of segwit. The next version of Armory will have segwit support. Doesn't have to mean the same. I also follow every rule of law even if i do not like them... He has explicitly expressed support for Segwit on the IRC channel. Furthermore, Segwit is not a law, nor is it required for every wallet to use segwit. If he did not like segwit, then he does not have to implement it.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on February 03, 2017, 05:31:53 PM
Armory devs have typically refrained from commenting on non technical aspects of consensus debates. I do not intend to break that pattern.
Voting with code is more sensible in this space, and my dev branch currently hosts a fully fleshed SegWit feature set.
Title: Re: Armory 0.95.1 is out
Post by: Aurik on February 05, 2017, 03:17:44 AM
Armory devs have typically refrained from commenting on non technical aspects of consensus debates. I do not intend to break that pattern.
Voting with code is more sensible in this space, and my dev branch currently hosts a fully fleshed SegWit feature set.
Thats good for me :)))
Title: Re: Armory 0.95.1 is out
Post by: MrRog on February 08, 2017, 01:17:59 PM
Hello
I have tr< to install the new version... but I get a lot of this errors...
and the DB want to be build...
I thont know whats hapen...
can everyone helping me
thx
rog
ValueError: No JSON object could be decoded
2017-02-08 13:49 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
Title: Re: Armory 0.95.1 is out
Post by: MrRog on February 08, 2017, 02:49:11 PM
after this
I tried the following settings: going to File > Settings and uncheck the box for "Let Armory run Bitcoin Core in the background". Then Stop Armory and start Bitcoin Core and Armory manually.
I get this Info
ERROR - 1486565046: (..\BlockDataMap.cpp:81) block yields: 605dab8dc7bfc8f90128357807b0f4da269edb32d14cb5395a96792b52a6301d
-ERROR - 1486565046: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO - 1486565046: (..\DatabaseBuilder.cpp:268) parsed block file #278
-DEBUG - 1486565047: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1486565195: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 193.087s
-INFO - 1486565195: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1486565195: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486565195: (..\BlockDataMap.cpp:80) header has: 74e2b0169a6fe4d8bf17c59babd5ba31871acd1c2e7437c77cae9512b945f5e2
-ERROR - 1486565195: (..\BlockDataMap.cpp:81) block yields: 605dab8dc7bfc8f90128357807b0f4da269edb32d14cb5395a96792b52a6301d
-ERROR - 1486565195: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on February 14, 2017, 08:03:45 PM
Hi using an older computer with Ubuntu 14.04 lts
Tried installing this version:
/Downloads/armory$ sudo dpkg -i armory_0.95.1_amd64.deb
but got:
error processing archive armory_0.95.1_amd64.deb (--install):
package architecture (amd64) does not match system (i386)
Supposer I would need a 32 version. Is there any solution, thanks?
Title: Re: Armory 0.95.1 is out
Post by: achow101 on February 14, 2017, 08:09:05 PM
Supposer I would need a 32 version. Is there any solution, thanks?
Unfortunately we no longer support 32 bit OSes.
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on February 15, 2017, 02:27:43 PM
Ok suppose it would be OK to use the newest older version that did support 32 ?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on February 15, 2017, 02:40:56 PM
0.92 can sign for 0.95, sure.
Title: Re: Armory 0.95.1 is out
Post by: frx on February 24, 2017, 02:48:26 PM
Hi,
First, thanks goatpig for all your effort to keep this project alive.
I have been using Armory for some years and recently I installed this new version. I installed it in fresh ubuntu install and I got many problems to make it work. One of the problems was Armory not being able to talk to bitcoind (RPC error in log). I saw some people had this issue and fixed it unchecking the option (Let armory execute bitcoind.....). I did this and it appears is working... but I am still not sure 100% is working.
What happens now is. Having Armory empty (without wallets), it says is online and synced. I close armory, I open it again. It starts building databases, just a few minutes (around 5) and then starts "Organizing blockchain". Problem is... it take hours! Even having Armory synced and online, if I close it, and in order to having working again I have to wait 3h. This does not make too much sense as you have the wallet online, and suddenly if you close you have to wait 3h again.. so is this an issue? normal behavior? Just in case, I run armory in virtual machine, but I have always done this without problems like this one.
Thanks!
Title: Re: Armory 0.95.1 is out
Post by: goatpig on February 24, 2017, 04:11:46 PM
I have been using Armory for some years and recently I installed this new version. I installed it in fresh ubuntu install and I got many problems to make it work. One of the problems was Armory not being able to talk to bitcoind (RPC error in log). I saw some people had this issue and fixed it unchecking the option (Let armory execute bitcoind.....). I did this and it appears is working... but I am still not sure 100% is working.
This should improve a lot in 0.96 What happens now is. Having Armory empty (without wallets), it says is online and synced. I close armory, I open it again. It starts building databases, just a few minutes (around 5) and then starts "Organizing blockchain". Problem is... it take hours! Even having Armory synced and online, if I close it, and in order to having working again I have to wait 3h. This does not make too much sense as you have the wallet online, and suddenly if you close you have to wait 3h again.. so is this an issue? normal behavior? Just in case, I run armory in virtual machine, but I have always done this without problems like this one.
Sounds like a bug. You should participate to the 0.96 testing phase going on atm and help me debug the issue: https://bitcointalk.org/index.php?topic=1784442.0
Title: Re: Armory 0.95.1 is out
Post by: frx on February 24, 2017, 04:19:21 PM
Thanks for your reply. Sure, I will make a new vm to test the testing version. I will let you know.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on February 24, 2017, 04:20:29 PM
Thanks for your reply. Sure, I will make a new vm to test the testing version. I will let you know.
Just to be clear, the code is in the dev and autotools branches atm.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 06, 2017, 11:39:59 AM
This is a known Armory bug, fixed for 0.96.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on March 06, 2017, 12:16:03 PM
This is a known Armory bug, fixed for 0.96.
Excellent. Could you make your signature a link? And add a donation address if you ever feel like it.
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 06, 2017, 04:22:48 PM
Excellent. Could you make your signature a link?
I got no idea how to o.o And add a donation address if you ever feel like it.
Once the new wallets are out Ill feel comfortable doing that.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on March 06, 2017, 05:49:35 PM
Excellent. Could you make your signature a link?
I got no idea how to o.o And add a donation address if you ever feel like it.
Once the new wallets are out Ill feel comfortable doing that. Haha like this [url]https://btcarmory.com[/url]
Title: Re: Armory 0.95.1 is out
Post by: Stroto on March 12, 2017, 01:16:03 PM
Hi, since I've updated to Bitcoin Core 0.14.0 the db keeps giving this message every 40 seconds or so: -ERROR - 1489323791: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323791: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323791: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node this is the db log Log file opened at 1489323546: C:\Users\----\AppData\Roaming\Armory\dbLog.txt
-INFO - 1489323546: (..\main.cpp:23) Running on 8 threads
-INFO - 1489323546: (..\main.cpp:24) Ram usage level: 4
-INFO - 1489323546: (..\BlockUtils.cpp:1338) blkfile dir: D:\Bitcoin\blocks
-INFO - 1489323546: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\-----\AppData\Roaming\Armory\databases
-INFO - 1489323546: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1489323547: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1489323547: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO - 1489323547: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1489323547: (..\BDM_Server.cpp:797) registered bdv: f87d2e25504ce328de4f
-INFO - 1489323549: (..\DatabaseBuilder.cpp:208) Found 456916 headers in db
-INFO - 1489323551: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1489323552: (..\DatabaseBuilder.cpp:477) Found next block after skipping 504928bytes
-INFO - 1489323553: (..\DatabaseBuilder.cpp:268) parsed block file #800
-DEBUG - 1489323553: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1489323553: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 1.419s
-INFO - 1489323553: (..\DatabaseBuilder.cpp:106) scanning new blocks from #456902 to #456905
-INFO - 1489323553: (..\BlockchainScanner.cpp:650) scanned from height #456902 to #456905
-INFO - 1489323553: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.216s
-INFO - 1489323553: (..\DatabaseBuilder.cpp:160) init db in 6.488s
-INFO - 1489323553: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1489323608: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323608: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323608: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323669: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323669: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323669: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323730: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323730: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323730: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323791: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323791: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323791: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323852: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323852: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323852: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489323913: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO - 1489323913: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO - 1489323913: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
and the armory log 2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1247 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1248 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1249 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\Bitcoin
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1254 - Armory Version : 0.95.1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1255 - Armory Build: : 374672b751
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1256 - PyBtcWallet Version : 1.35
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1258 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1259 - User home-directory : C:\Users\-----\AppData\Roaming
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1260 - Satoshi BTC directory : D:\Bitcoin
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1261 - Armory home dir : C:\Users\-----\AppData\Roaming\Armory\
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs :
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1263 - Total Available RAM : 15.93 GB
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1264 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1265 - Number of CPU cores : 8 cores
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1266 - System is 64-bit : True
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1267 - Preferred Encoding : cp1252
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1268 - Machine Arch : amd64
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1269 - Available HDD (ARM) : 146 GB
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1270 - Available HDD (BTC) : 334 GB
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1271 -
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - thread_count : -1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rescan : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - ignoreAllZC : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rescanBalance : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - disableModules : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - port : None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - interport : 8223
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - skipStatsReport : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - forceWalletCheck: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - regtest : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rebuild : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - nettimeout : 2
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - datadir : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - clearMempool : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - offline : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - coverageOutputDir: None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - armoryDBDir : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_port : 9001
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - satoshiPort : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - useTorSettings : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - netlog : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - keypool : 100
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - coverageInclude : None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - forceOnline : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - skipAnnounceCheck: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - redownload : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_ip : 127.0.0.1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - multisigFile : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - ram_usage : -1
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - testAnnounceCode: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - mtdebug : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - logDisable : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - settingsPath : C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - db_type : DB_FULL
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - doDebug : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - enableDetSign : True
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - disableConfPermis: False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - testnet : False
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - rpcport : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - satoshiHome : D:\Bitcoin
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - satoshiRpcport : DEFAULT
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - logFile : C:\Users\-----\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1277 - verbosity : None
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2017-03-12 13:56 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-03-12 13:56 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background.
2017-03-12 13:56 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2017-03-12 13:56 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2017-03-12 13:56 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2608 - Loading Multisig Lockboxes
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1530 - URL-register action: AskUser
2017-03-12 13:56 (INFO) -- ArmoryQt.py:546 - Usermode: Expert
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1709 - From: Expert
2017-03-12 13:56 (INFO) -- ArmoryQt.py:1717 - To: Expert
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:56 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:56 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="FTDLTZaFd5vqTfHqWLBzK91YoDSkR8WYpHbrE8H5fTNc"', u'--satoshi-datadir="D:\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\databases"']
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-03-12 13:56 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:56 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:56 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:58 (INFO) -- ArmoryQt.py:6366 - BDM state is scanning -- force shutdown BDM
2017-03-12 13:58 (INFO) -- SDM.pyc:588 - Called stopBitcoind
2017-03-12 13:58 (INFO) -- SDM.pyc:594 - ...but bitcoind is not running, to be able to stop
2017-03-12 13:58 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window!
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1247 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1248 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1249 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\Bitcoin
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1254 - Armory Version : 0.95.1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1255 - Armory Build: : 374672b751
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1256 - PyBtcWallet Version : 1.35
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1258 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1259 - User home-directory : C:\Users\-----\AppData\Roaming
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1260 - Satoshi BTC directory : D:\Bitcoin
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1261 - Armory home dir : C:\Users\-----\AppData\Roaming\Armory\
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs :
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1263 - Total Available RAM : 15.93 GB
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1264 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1265 - Number of CPU cores : 8 cores
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1266 - System is 64-bit : True
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1267 - Preferred Encoding : cp1252
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1268 - Machine Arch : amd64
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1269 - Available HDD (ARM) : 146 GB
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1270 - Available HDD (BTC) : 334 GB
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1271 -
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - thread_count : -1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rescan : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - ignoreAllZC : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rescanBalance : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - disableModules : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - port : None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - interport : 8223
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - skipStatsReport : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - forceWalletCheck: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - regtest : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rebuild : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - nettimeout : 2
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - datadir : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - clearMempool : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - offline : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - coverageOutputDir: None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - armoryDBDir : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_port : 9001
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - satoshiPort : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - useTorSettings : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - netlog : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - keypool : 100
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - coverageInclude : None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - forceOnline : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - skipAnnounceCheck: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - redownload : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_ip : 127.0.0.1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - multisigFile : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - ram_usage : -1
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - testAnnounceCode: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - mtdebug : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - logDisable : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - settingsPath : C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - db_type : DB_FULL
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - doDebug : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - enableDetSign : True
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - disableConfPermis: False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - testnet : False
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - rpcport : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - satoshiHome : D:\Bitcoin
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - satoshiRpcport : DEFAULT
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - logFile : C:\Users\-----\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1277 - verbosity : None
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2017-03-12 13:58 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-03-12 13:58 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background.
2017-03-12 13:58 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2017-03-12 13:58 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2017-03-12 13:58 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2017-03-12 13:58 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\-----\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-12 13:58 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-03-12 13:58 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2608 - Loading Multisig Lockboxes
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1530 - URL-register action: AskUser
2017-03-12 13:59 (INFO) -- ArmoryQt.py:546 - Usermode: Expert
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1709 - From: Expert
2017-03-12 13:59 (INFO) -- ArmoryQt.py:1717 - To: Expert
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:59 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-12 13:59 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="BMA8coF2js6PSn1AGtq7WukybjnYTSDL18pZ87deE3zk"', u'--satoshi-datadir="D:\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\-----\\AppData\\Roaming\\Armory\\databases"']
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-12 13:59 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:59 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-12 13:59 (INFO) -- ArmoryQt.py:2886 - Current block number: 456905
2017-03-12 14:07 (INFO) -- ArmoryQt.py:4024 - Log saved to C:/Users/-----/Desktop/armorylog_20170312_1407.txt
Log file opened at 1480191063: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480191121: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1480193992: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1480320551: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1480320743: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
-ERROR - 1480320743: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1480321940: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1480322061: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1480322186: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480331726: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480334931: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1480425759: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1481270669: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1482609187: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1482786751: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483042311: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483045028: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483052315: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483053886: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483133221: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483189468: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483281107: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483285553: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483291195: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483299834: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483366683: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483647966: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483727714: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483818976: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1483906647: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484046465: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484073963: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484075731: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484078389: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484080635: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
-ERROR - 1484080635: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484080643: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484082887: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484085444: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484085467: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1484085599: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1484085660: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484085667: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484088951: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484089032: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484089081: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484130979: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484154629: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484162710: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484215947: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484216054: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484220135: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484297027: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484302559: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484339516: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484384155: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484491464: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484558186: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484591486: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484913666: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1484995269: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485099093: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485116867: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1485116886: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1485117250: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485120544: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1485120633: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1485121265: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485283114: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485534680: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485640126: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1485640145: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1485640462: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485642079: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485765749: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485814169: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1485978322: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486287544: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1486287563: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1486290523: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1486293646: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1486293657: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486381490: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486458264: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486629459: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486915604: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486939664: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486976206: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486976397: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486976741: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486979143: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1486981467: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1487186040: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1487435332: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1487435350: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1487435832: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1487544196: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488741920: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1488741939: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1488742042: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488749048: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488970297: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1488987113: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489047143: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489047533: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489047645: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
-ERROR - 1489047645: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489047655: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489048422: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489048440: (..\SwigClient.cpp:61) can't connect socket
Log file opened at 1489048554: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489315279: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489315377: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489318882: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489320121: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489320128: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489320725: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
Log file opened at 1489323360: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 1489323510: (..\SocketObject.cpp:438) POLLERR error in readAndWrite
Log file opened at 1489323530: C:\Users\-----\AppData\Roaming\Armory\armorycpplog.txt
is this nothing to worry about (but it does prevent broadcasting txs sometimes) or can i solve this somehow? EDIT: I should have read a couple of posts above me ::)
Title: Re: Armory 0.95.1 is out
Post by: bitpop on March 12, 2017, 01:26:04 PM
Yeah Same here :)
I guess the problem is Bitcoin > 0.12?
I've been doing offline transactions but still can sign them online then broadcasting on bci
Title: Re: Armory 0.95.1 is out
Post by: JeffZwolle on March 12, 2017, 09:22:59 PM
FYI:
I have been running BitcoinCore 0.14.0 together with Armory 0.95.1 without any problem on Windows 7 64bit.
Title: Re: Armory 0.95.1 is out
Post by: bitpop on March 13, 2017, 12:56:12 AM
FYI:
I have been running BitcoinCore 0.14.0 together with Armory 0.95.1 without any problem on Windows 7 64bit.
Are you sure the log doesn't have anything? Because the gui works
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 23, 2017, 02:37:25 PM
I still have a problem with my Armory installations. I set up a new (virtual) machine (Win10 64Bit) for Armory. It was working fine right after setup and I also could send BTC, that was some weeks ago. When I do start armory now the "armorydb.exe" is shown (seems working normal) and after some time Armory looks normal and shows status "Connected ( 453226)". The problem is: Currently we do have 458560 and Armory does not load new transactions. Unfortunately I sent some BTC to my Armory BTC Address yesterday and those BTC do not show up :-( What can I do? I already updated Bitcoin core to V0.14, but got the same result. I also tried to "Let Armory run Bitcoin-code/bitcoind in the background", but in that case the armorydb.exe windows does not show up and it is scanning transactions for days (always saying 1 second left). Here is the latest log with Bitcoin code V0.14 without having "Let Armory run Bitcoin-code/bitcoind in the background" checked (so armorydb.exe window is shown): 2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1247 -
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1248 -
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1249 -
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1254 - Armory Version : 0.95.1
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1255 - Armory Build: : 374672b751
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1256 - PyBtcWallet Version : 1.35
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1258 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1259 - User home-directory : C:\Users\ITSN\AppData\Roaming
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1260 - Satoshi BTC directory : C:\Users\ITSN\AppData\Roaming\Bitcoin\
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1261 - Armory home dir : C:\Users\ITSN\AppData\Roaming\Armory\
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs :
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1263 - Total Available RAM : 3.99 GB
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1264 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1265 - Number of CPU cores : 2 cores
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1266 - System is 64-bit : True
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1267 - Preferred Encoding : cp1252
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1268 - Machine Arch : amd64
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1269 - Available HDD (ARM) : 68 GB
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1270 - Available HDD (BTC) : 68 GB
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1271 -
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - thread_count : -1
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - rescan : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - ignoreAllZC : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - rescanBalance : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - disableModules : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - port : None
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - interport : 8223
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - skipStatsReport : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - forceWalletCheck: False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - regtest : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - rebuild : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - nettimeout : 2
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - datadir : DEFAULT
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - clearMempool : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - offline : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - coverageOutputDir: None
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - armoryDBDir : DEFAULT
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_port : 9001
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - satoshiPort : DEFAULT
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - useTorSettings : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - netlog : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - keypool : 100
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - coverageInclude : None
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - forceOnline : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - skipAnnounceCheck: False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - redownload : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_ip : 127.0.0.1
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - multisigFile : DEFAULT
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - ram_usage : -1
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - testAnnounceCode: False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - mtdebug : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - logDisable : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - settingsPath : C:\Users\ITSN\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - db_type : DB_FULL
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - doDebug : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - enableDetSign : True
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - disableConfPermis: False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - testnet : False
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - rpcport : DEFAULT
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - satoshiHome : DEFAULT
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - satoshiRpcport : DEFAULT
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - logFile : C:\Users\ITSN\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1277 - verbosity : None
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2017-03-23 15:28 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-03-23 15:28 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background.
2017-03-23 15:28 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2017-03-23 15:28 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2017-03-23 15:28 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\ITSN\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 3ABjes9Ls
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2576 - Wallet 1 (skipped): C:\Users\ITSN\AppData\Roaming\Armory\armory_3ABjes9Ls_decrypt.wallet.wallet
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2577 - Wallet 2 (loaded): C:\Users\ITSN\AppData\Roaming\Armory\armory_3ABjes9Ls_decrypt.wallet.rootpubkey
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 3ABjes9Ls
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2576 - Wallet 1 (skipped): C:\Users\ITSN\AppData\Roaming\Armory\armory_3ABjes9Ls_decrypt.wallet_backup.rootpubkey
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2577 - Wallet 2 (loaded): C:\Users\ITSN\AppData\Roaming\Armory\armory_3ABjes9Ls_decrypt.wallet.rootpubkey
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, DyoF6jaw
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2576 - Wallet 1 (skipped): C:\Users\ITSN\AppData\Roaming\Armory\armory_DyoF6jaw_decrypt.wallet.wallet
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2577 - Wallet 2 (loaded): C:\Users\ITSN\AppData\Roaming\Armory\armory_DyoF6jaw_decrypt.wallet.rootpubkey
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, DyoF6jaw
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2576 - Wallet 1 (skipped): C:\Users\ITSN\AppData\Roaming\Armory\armory_DyoF6jaw_decrypt.wallet_backup.rootpubkey
2017-03-23 15:28 (WARNING) -- ArmoryQt.py:2577 - Wallet 2 (loaded): C:\Users\ITSN\AppData\Roaming\Armory\armory_DyoF6jaw_decrypt.wallet.rootpubkey
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 2
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2603 - Wallet (DyoF6jaw): "ITSN " (Encrypted)
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2603 - Wallet (3ABjes9Ls): "Privat " (Encrypted)
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-03-23 15:28 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-03-23 15:28 (INFO) -- ArmoryQt.py:1480 - Armory already registered for current user. Done!
2017-03-23 15:28 (INFO) -- ArmoryQt.py:546 - Usermode: Advanced
2017-03-23 15:28 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-03-23 15:28 (INFO) -- ArmoryQt.py:1709 - From: Advanced
2017-03-23 15:28 (INFO) -- ArmoryQt.py:1717 - To: Advanced
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-23 15:28 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-23 15:28 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-23 15:28 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="7wSNLhghT1rhhcREWF17kchdo8NNmRZ3foRNYmpSwEB9"', u'--satoshi-datadir="C:\\Users\\ITSN\\AppData\\Roaming\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\ITSN\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\ITSN\\AppData\\Roaming\\Armory\\databases"']
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-03-23 15:28 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-23 15:28 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-23 15:28 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-23 15:32 (WARNING) -- ArmoryQt.py:4935 - Called updateSyncProgress while not sync'ing
2017-03-23 15:32 (INFO) -- ArmoryQt.py:2886 - Current block number: 453226
If I do start it with checked "Let Armory run Bitcoin-code/bitcoind in the background" it looks like this (even after more than 24h): http://fs5.directupload.net/images/170323/c9v63qtd.png (http://www.directupload.net) And this is what is shown in the log: 2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1247 -
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1248 -
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1249 -
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1254 - Armory Version : 0.95.1
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1255 - Armory Build: : 374672b751
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1256 - PyBtcWallet Version : 1.35
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1258 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1259 - User home-directory : C:\Users\ITSN\AppData\Roaming
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1260 - Satoshi BTC directory : C:\Users\ITSN\AppData\Roaming\Bitcoin\
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1261 - Armory home dir : C:\Users\ITSN\AppData\Roaming\Armory\
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs :
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1263 - Total Available RAM : 3.99 GB
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1264 - CPU ID string : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1265 - Number of CPU cores : 2 cores
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1266 - System is 64-bit : True
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1267 - Preferred Encoding : cp1252
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1268 - Machine Arch : amd64
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1269 - Available HDD (ARM) : 68 GB
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1270 - Available HDD (BTC) : 68 GB
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1271 -
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - thread_count : -1
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - rescan : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - ignoreAllZC : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - rescanBalance : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - disableModules : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - port : None
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - interport : 8223
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - skipStatsReport : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - forceWalletCheck: False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - regtest : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - rebuild : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - nettimeout : 2
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - datadir : DEFAULT
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - clearMempool : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - offline : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - coverageOutputDir: None
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - armoryDBDir : DEFAULT
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_port : 9001
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - satoshiPort : DEFAULT
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - useTorSettings : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - netlog : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - keypool : 100
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - coverageInclude : None
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - forceOnline : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - skipAnnounceCheck: False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - redownload : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - armorydb_ip : 127.0.0.1
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - multisigFile : DEFAULT
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - ram_usage : -1
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - testAnnounceCode: False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - mtdebug : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - logDisable : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - settingsPath : C:\Users\ITSN\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - db_type : DB_FULL
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - doDebug : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - enableDetSign : True
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - disableConfPermis: False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - testnet : False
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - rpcport : DEFAULT
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - satoshiHome : DEFAULT
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - satoshiRpcport : DEFAULT
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - logFile : C:\Users\ITSN\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1277 - verbosity : None
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2017-03-23 15:43 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-03-23 15:43 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background.
2017-03-23 15:43 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2017-03-23 15:43 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2017-03-23 15:43 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\ITSN\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, 3ABjes9Ls
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2576 - Wallet 1 (skipped): C:\Users\ITSN\AppData\Roaming\Armory\armory_3ABjes9Ls_decrypt.wallet.wallet
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2577 - Wallet 2 (loaded): C:\Users\ITSN\AppData\Roaming\Armory\armory_3ABjes9Ls_decrypt.wallet.rootpubkey
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, DyoF6jaw
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2576 - Wallet 1 (skipped): C:\Users\ITSN\AppData\Roaming\Armory\armory_DyoF6jaw_decrypt.wallet.wallet
2017-03-23 15:43 (WARNING) -- ArmoryQt.py:2577 - Wallet 2 (loaded): C:\Users\ITSN\AppData\Roaming\Armory\armory_DyoF6jaw_decrypt.wallet.rootpubkey
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 2
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2603 - Wallet (DyoF6jaw): "ITSN " (Encrypted)
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2603 - Wallet (3ABjes9Ls): "Privat " (Encrypted)
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-03-23 15:43 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-03-23 15:43 (INFO) -- ArmoryQt.py:1480 - Armory already registered for current user. Done!
2017-03-23 15:43 (INFO) -- ArmoryQt.py:546 - Usermode: Advanced
2017-03-23 15:43 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-03-23 15:43 (INFO) -- ArmoryQt.py:1709 - From: Advanced
2017-03-23 15:43 (INFO) -- ArmoryQt.py:1717 - To: Advanced
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-23 15:43 (INFO) -- ArmoryQt.py:2275 - Setting satoshi datadir = C:\Users\ITSN\AppData\Roaming\Bitcoin
2017-03-23 15:43 (INFO) -- SDM.pyc:182 - Found bitcoind in the following places:
2017-03-23 15:43 (INFO) -- SDM.pyc:184 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-23 15:43 (INFO) -- SDM.pyc:184 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-23 15:43 (INFO) -- SDM.pyc:186 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-23 15:43 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-23 15:43 (INFO) -- SDM.pyc:460 - Called startBitcoind
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\ITSN\\AppData\\Roaming\\Bitcoin']
2017-03-23 15:43 (INFO) -- SDM.pyc:574 - PID of bitcoind: 6004
2017-03-23 15:43 (INFO) -- SDM.pyc:575 - PID of armory: 6076
2017-03-23 15:43 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '6076', '6004']
2017-03-23 15:43 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-03-23 15:43 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
2017-03-23 15:43 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
Any idea how I can get this solved or at least get my BTC out of it? BR
Title: Re: Armory 0.95.1 is out
Post by: achow101 on March 23, 2017, 03:06:45 PM
The problem is: Currently we do have 458560 and Armory does not load new transactions. Unfortunately I sent some BTC to my Armory BTC Address yesterday and those BTC do not show up :-(
What can I do?
When you sent the Bitcoin, did you receive a message about the transaction broadcast failing or timing out? After you leave Armory running for a while, do you notice that the block count it reports falls behind the real block count? Can you please post your dbLog.txt file? I believe the issue you are experiencing is a known issue and has already been fixed for 0.96. Goatpig will be putting out the 0.96 testing builds once he finishes implementing RBF, which should be in the next couple of days. If you know how to build software, you can pull the latest development version from the dev branch of the github repo and build 0.96 yourself to use. I also tried to "Let Armory run Bitcoin-code/bitcoind in the background", but in that case the armorydb.exe windows does not show up and it is scanning transactions for days (always saying 1 second left)
Yeah, don't do that. It's almost guaranteed to not work if you have auto-managed bitcoind on.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 23, 2017, 03:26:41 PM
The problem is: Currently we do have 458560 and Armory does not load new transactions. Unfortunately I sent some BTC to my Armory BTC Address yesterday and those BTC do not show up :-(
What can I do?
When you sent the Bitcoin, did you receive a message about the transaction broadcast failing or timing out? After you leave Armory running for a while, do you notice that the block count it reports falls behind the real block count? Can you please post your dbLog.txt file? I believe the issue you are experiencing is a known issue and has already been fixed for 0.96. Goatpig will be putting out the 0.96 testing builds once he finishes implementing RBF, which should be in the next couple of days. If you know how to build software, you can pull the latest development version from the dev branch of the github repo and build 0.96 yourself to use. I also tried to "Let Armory run Bitcoin-code/bitcoind in the background", but in that case the armorydb.exe windows does not show up and it is scanning transactions for days (always saying 1 second left)
Yeah, don't do that. It's almost guaranteed to not work if you have auto-managed bitcoind on. I did sent BTC from kraken.com, that transaction is shown as confirmed in the blockchain. The block count does not change, it just stays at 453226. Here is the dbLog.txt:
Log file opened at 1490281848: C:\Users\ITSN\AppData\Roaming\Armory\dbLog.txt
-INFO - 1490281848: (..\main.cpp:23) Running on 2 threads
-INFO - 1490281848: (..\main.cpp:24) Ram usage level: 4
-INFO - 1490281848: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\ITSN\AppData\Roaming\Bitcoin\blocks
-INFO - 1490281848: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\ITSN\AppData\Roaming\Armory\databases
-INFO - 1490281848: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1490281849: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1490281850: (..\BDM_Server.cpp:797) registered bdv: a1d488c8ecd1906333ab
-INFO - 1490281863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1490281891: (..\DatabaseBuilder.cpp:208) Found 453227 headers in db
-INFO - 1490281893: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1490281894: (..\DatabaseBuilder.cpp:477) Found next block after skipping 52493bytes
-INFO - 1490281895: (..\DatabaseBuilder.cpp:268) parsed block file #780
-INFO - 1490281897: (..\DatabaseBuilder.cpp:268) parsed block file #781
-INFO - 1490281898: (..\DatabaseBuilder.cpp:268) parsed block file #782
-INFO - 1490281899: (..\DatabaseBuilder.cpp:268) parsed block file #783
-INFO - 1490281901: (..\DatabaseBuilder.cpp:268) parsed block file #784
-INFO - 1490281904: (..\DatabaseBuilder.cpp:268) parsed block file #786
-INFO - 1490281908: (..\DatabaseBuilder.cpp:268) parsed block file #788
-INFO - 1490281911: (..\DatabaseBuilder.cpp:268) parsed block file #790
-INFO - 1490281914: (..\DatabaseBuilder.cpp:268) parsed block file #792
-INFO - 1490281918: (..\DatabaseBuilder.cpp:268) parsed block file #794
-INFO - 1490281923: (..\DatabaseBuilder.cpp:268) parsed block file #795
-INFO - 1490281927: (..\DatabaseBuilder.cpp:268) parsed block file #797
-INFO - 1490281932: (..\DatabaseBuilder.cpp:268) parsed block file #799
-INFO - 1490281937: (..\DatabaseBuilder.cpp:268) parsed block file #800
-INFO - 1490281945: (..\DatabaseBuilder.cpp:268) parsed block file #802
-INFO - 1490281952: (..\DatabaseBuilder.cpp:268) parsed block file #804
-INFO - 1490281960: (..\DatabaseBuilder.cpp:268) parsed block file #806
-INFO - 1490281971: (..\DatabaseBuilder.cpp:268) parsed block file #808
-INFO - 1490281991: (..\DatabaseBuilder.cpp:268) parsed block file #810
-INFO - 1490282001: (..\DatabaseBuilder.cpp:268) parsed block file #812
-DEBUG - 1490282019: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1490282065: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 172.434s
-INFO - 1490282066: (..\DatabaseBuilder.cpp:106) scanning new blocks from #453227 to #453226
-INFO - 1490282066: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1490282066: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1490282066: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO - 1490282066: (..\DatabaseBuilder.cpp:160) init db in 216.234s
-INFO - 1490282066: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
Unfortunately I have no clue about how to build a new version on windows :-( Is there some kind of ETA for the binaries of 0.96? Or is there any other chance to get my BTC out of that wallet? BR
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 23, 2017, 03:34:50 PM
Do a rebuild & rescan.
Title: Re: Armory 0.95.1 is out
Post by: achow101 on March 23, 2017, 03:34:50 PM
I did sent BTC from kraken.com, that transaction is shown as confirmed in the blockchain.
Ah, whoops. I read that part backwards. The block count does not change, it just stays at 453226.
Restarting Armory should fix the issue, briefly. Armory 0.95.1 currently has an issue where it will disconnect from Bitcoin Core every so often but you won't notice it unless you see that the block count is way off. To get it to reconnect, you need to restart Armory. Here is the dbLog.txt:
Is that all? There should be more. Unfortunately I have no clue about how to build a new version on windows :-(
Is there some kind of ETA for the binaries of 0.96? Or is there any other chance to get my BTC out of that wallet?
BR
I don't know when the testing binaries will be available. If you really want to, you can export your private keys to another wallet. Otherwise, just keep an eye on the ArmoryDB window and if it ever says something like "Disconnecting from node", restart Armory so that it will connect to Bitcoin Core properly so that you can send and receive Bitcoin.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 23, 2017, 03:48:28 PM
The block count does not change, it just stays at 453226.
Restarting Armory should fix the issue, briefly. Armory 0.95.1 currently has an issue where it will disconnect from Bitcoin Core every so often but you won't notice it unless you see that the block count is way off. To get it to reconnect, you need to restart Armory. Unfortunately it does not. If I restart the whole computer and start armory again the armorydb.exe windows appears and armory starts. But the result is always the same - it stops with Block 453226. If I do close only armory then (and leave armorydb.exe window open) this also does not change anything beside the fact that startup is faster (there are no new lines in the armorydb.exe window) Here is the dbLog.txt:
Is that all? There should be more.
I just restarted the computer and deleted all logs. Then started armory again, the result is the same:
Log file opened at 1490283614: C:\Users\ITSN\AppData\Roaming\Armory\dbLog.txt
-INFO - 1490283614: (..\main.cpp:23) Running on 2 threads
-INFO - 1490283614: (..\main.cpp:24) Ram usage level: 4
-INFO - 1490283614: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\ITSN\AppData\Roaming\Bitcoin\blocks
-INFO - 1490283614: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\ITSN\AppData\Roaming\Armory\databases
-INFO - 1490283614: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1490283615: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1490283616: (..\BDM_Server.cpp:797) registered bdv: 808a60339ce348e53614
-INFO - 1490283641: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1490283674: (..\DatabaseBuilder.cpp:208) Found 453227 headers in db
-INFO - 1490283677: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1490283679: (..\DatabaseBuilder.cpp:477) Found next block after skipping 52493bytes
-INFO - 1490283680: (..\DatabaseBuilder.cpp:268) parsed block file #781
-INFO - 1490283683: (..\DatabaseBuilder.cpp:268) parsed block file #783
-INFO - 1490283687: (..\DatabaseBuilder.cpp:268) parsed block file #784
-INFO - 1490283690: (..\DatabaseBuilder.cpp:268) parsed block file #785
-INFO - 1490283691: (..\DatabaseBuilder.cpp:268) parsed block file #786
-INFO - 1490283693: (..\DatabaseBuilder.cpp:268) parsed block file #787
-INFO - 1490283695: (..\DatabaseBuilder.cpp:268) parsed block file #788
-INFO - 1490283696: (..\DatabaseBuilder.cpp:268) parsed block file #789
-INFO - 1490283697: (..\DatabaseBuilder.cpp:268) parsed block file #790
-INFO - 1490283698: (..\DatabaseBuilder.cpp:268) parsed block file #791
-INFO - 1490283699: (..\DatabaseBuilder.cpp:268) parsed block file #792
-INFO - 1490283700: (..\DatabaseBuilder.cpp:268) parsed block file #793
-INFO - 1490283702: (..\DatabaseBuilder.cpp:268) parsed block file #794
-INFO - 1490283705: (..\DatabaseBuilder.cpp:268) parsed block file #796
-INFO - 1490283713: (..\DatabaseBuilder.cpp:268) parsed block file #797
-INFO - 1490283717: (..\DatabaseBuilder.cpp:268) parsed block file #798
-INFO - 1490283718: (..\DatabaseBuilder.cpp:268) parsed block file #799
-INFO - 1490283723: (..\DatabaseBuilder.cpp:268) parsed block file #800
-INFO - 1490283726: (..\DatabaseBuilder.cpp:268) parsed block file #801
-INFO - 1490283730: (..\DatabaseBuilder.cpp:268) parsed block file #802
-INFO - 1490283733: (..\DatabaseBuilder.cpp:268) parsed block file #803
-INFO - 1490283736: (..\DatabaseBuilder.cpp:268) parsed block file #804
-INFO - 1490283741: (..\DatabaseBuilder.cpp:268) parsed block file #806
-INFO - 1490283752: (..\DatabaseBuilder.cpp:268) parsed block file #808
-INFO - 1490283757: (..\DatabaseBuilder.cpp:268) parsed block file #810
-INFO - 1490283765: (..\DatabaseBuilder.cpp:268) parsed block file #812
-DEBUG - 1490283768: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1490283809: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 132.115s
-INFO - 1490283809: (..\DatabaseBuilder.cpp:106) scanning new blocks from #453227 to #453226
-INFO - 1490283809: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1490283809: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1490283810: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.364s
-INFO - 1490283810: (..\DatabaseBuilder.cpp:160) init db in 194.658s
-INFO - 1490283810: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
Greetings
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 23, 2017, 03:51:31 PM
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 23, 2017, 05:36:51 PM
Hello, thank you, I did so. Do I have to be concerned? It seems to be stuck at 96% (1.5 Mins left) of Building Databases (since more than 1h). The dblog also stops at the last line (since more than 1h): Log file opened at 1490283614: C:\Users\ITSN\AppData\Roaming\Armory\dbLog.txt
-INFO - 1490283614: (..\main.cpp:23) Running on 2 threads
-INFO - 1490283614: (..\main.cpp:24) Ram usage level: 4
-INFO - 1490283614: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\ITSN\AppData\Roaming\Bitcoin\blocks
-INFO - 1490283614: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\ITSN\AppData\Roaming\Armory\databases
-INFO - 1490283614: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1490283615: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1490283616: (..\BDM_Server.cpp:797) registered bdv: 808a60339ce348e53614
-INFO - 1490283641: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1490283674: (..\DatabaseBuilder.cpp:208) Found 453227 headers in db
-INFO - 1490283677: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1490283679: (..\DatabaseBuilder.cpp:477) Found next block after skipping 52493bytes
-INFO - 1490283680: (..\DatabaseBuilder.cpp:268) parsed block file #781
-INFO - 1490283683: (..\DatabaseBuilder.cpp:268) parsed block file #783
-INFO - 1490283687: (..\DatabaseBuilder.cpp:268) parsed block file #784
-INFO - 1490283690: (..\DatabaseBuilder.cpp:268) parsed block file #785
-INFO - 1490283691: (..\DatabaseBuilder.cpp:268) parsed block file #786
-INFO - 1490283693: (..\DatabaseBuilder.cpp:268) parsed block file #787
-INFO - 1490283695: (..\DatabaseBuilder.cpp:268) parsed block file #788
-INFO - 1490283696: (..\DatabaseBuilder.cpp:268) parsed block file #789
-INFO - 1490283697: (..\DatabaseBuilder.cpp:268) parsed block file #790
-INFO - 1490283698: (..\DatabaseBuilder.cpp:268) parsed block file #791
-INFO - 1490283699: (..\DatabaseBuilder.cpp:268) parsed block file #792
-INFO - 1490283700: (..\DatabaseBuilder.cpp:268) parsed block file #793
-INFO - 1490283702: (..\DatabaseBuilder.cpp:268) parsed block file #794
-INFO - 1490283705: (..\DatabaseBuilder.cpp:268) parsed block file #796
-INFO - 1490283713: (..\DatabaseBuilder.cpp:268) parsed block file #797
-INFO - 1490283717: (..\DatabaseBuilder.cpp:268) parsed block file #798
-INFO - 1490283718: (..\DatabaseBuilder.cpp:268) parsed block file #799
-INFO - 1490283723: (..\DatabaseBuilder.cpp:268) parsed block file #800
-INFO - 1490283726: (..\DatabaseBuilder.cpp:268) parsed block file #801
-INFO - 1490283730: (..\DatabaseBuilder.cpp:268) parsed block file #802
-INFO - 1490283733: (..\DatabaseBuilder.cpp:268) parsed block file #803
-INFO - 1490283736: (..\DatabaseBuilder.cpp:268) parsed block file #804
-INFO - 1490283741: (..\DatabaseBuilder.cpp:268) parsed block file #806
-INFO - 1490283752: (..\DatabaseBuilder.cpp:268) parsed block file #808
-INFO - 1490283757: (..\DatabaseBuilder.cpp:268) parsed block file #810
-INFO - 1490283765: (..\DatabaseBuilder.cpp:268) parsed block file #812
-DEBUG - 1490283768: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1490283809: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 132.115s
-INFO - 1490283809: (..\DatabaseBuilder.cpp:106) scanning new blocks from #453227 to #453226
-INFO - 1490283809: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1490283809: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1490283810: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.364s
-INFO - 1490283810: (..\DatabaseBuilder.cpp:160) init db in 194.658s
-INFO - 1490283810: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
Log file opened at 1490284828: C:\Users\ITSN\AppData\Roaming\Armory\dbLog.txt
-INFO - 1490284828: (..\main.cpp:23) Running on 2 threads
-INFO - 1490284828: (..\main.cpp:24) Ram usage level: 4
-INFO - 1490284828: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\ITSN\AppData\Roaming\Bitcoin\blocks
-INFO - 1490284828: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\ITSN\AppData\Roaming\Armory\databases
-INFO - 1490284828: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1490284829: (..\BlockUtils.cpp:1540) Executing: doInitialSyncOnLoad_Rebuild
-INFO - 1490284829: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1490284830: (..\BDM_Server.cpp:797) registered bdv: 1a034366de9f7205d2c4
-INFO - 1490284859: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1490284859: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO - 1490284859: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO - 1490284859: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1490284863: (..\DatabaseBuilder.cpp:268) parsed block file #1
-INFO - 1490284866: (..\DatabaseBuilder.cpp:268) parsed block file #3
-INFO - 1490284869: (..\DatabaseBuilder.cpp:268) parsed block file #5
-INFO - 1490284872: (..\DatabaseBuilder.cpp:268) parsed block file #7
-INFO - 1490284876: (..\DatabaseBuilder.cpp:268) parsed block file #9
-INFO - 1490284879: (..\DatabaseBuilder.cpp:268) parsed block file #11
-INFO - 1490284882: (..\DatabaseBuilder.cpp:268) parsed block file #13
-INFO - 1490284884: (..\DatabaseBuilder.cpp:268) parsed block file #15
-INFO - 1490284887: (..\DatabaseBuilder.cpp:268) parsed block file #17
-INFO - 1490284891: (..\DatabaseBuilder.cpp:268) parsed block file #18
-INFO - 1490284893: (..\DatabaseBuilder.cpp:268) parsed block file #19
-INFO - 1490284896: (..\DatabaseBuilder.cpp:268) parsed block file #20
-INFO - 1490284897: (..\DatabaseBuilder.cpp:268) parsed block file #21
-INFO - 1490284899: (..\DatabaseBuilder.cpp:268) parsed block file #22
-INFO - 1490284902: (..\DatabaseBuilder.cpp:268) parsed block file #24
-INFO - 1490284905: (..\DatabaseBuilder.cpp:268) parsed block file #26
-INFO - 1490284912: (..\DatabaseBuilder.cpp:268) parsed block file #28
-INFO - 1490284917: (..\DatabaseBuilder.cpp:268) parsed block file #29
-INFO - 1490284920: (..\DatabaseBuilder.cpp:268) parsed block file #31
-INFO - 1490284923: (..\DatabaseBuilder.cpp:268) parsed block file #33
-INFO - 1490284926: (..\DatabaseBuilder.cpp:268) parsed block file #35
-INFO - 1490284937: (..\DatabaseBuilder.cpp:268) parsed block file #36
-INFO - 1490284940: (..\DatabaseBuilder.cpp:268) parsed block file #38
-INFO - 1490284945: (..\DatabaseBuilder.cpp:268) parsed block file #39
-INFO - 1490284947: (..\DatabaseBuilder.cpp:268) parsed block file #40
-INFO - 1490284949: (..\DatabaseBuilder.cpp:268) parsed block file #42
-INFO - 1490284953: (..\DatabaseBuilder.cpp:268) parsed block file #43
-INFO - 1490284955: (..\DatabaseBuilder.cpp:268) parsed block file #44
-INFO - 1490284957: (..\DatabaseBuilder.cpp:268) parsed block file #46
-INFO - 1490284962: (..\DatabaseBuilder.cpp:268) parsed block file #47
-INFO - 1490284962: (..\DatabaseBuilder.cpp:268) parsed block file #48
-INFO - 1490284966: (..\DatabaseBuilder.cpp:268) parsed block file #50
-INFO - 1490284970: (..\DatabaseBuilder.cpp:268) parsed block file #52
-INFO - 1490284975: (..\DatabaseBuilder.cpp:268) parsed block file #53
-INFO - 1490284978: (..\DatabaseBuilder.cpp:268) parsed block file #55
-INFO - 1490284981: (..\DatabaseBuilder.cpp:268) parsed block file #57
-INFO - 1490284984: (..\DatabaseBuilder.cpp:268) parsed block file #59
-INFO - 1490284988: (..\DatabaseBuilder.cpp:268) parsed block file #61
-INFO - 1490284992: (..\DatabaseBuilder.cpp:268) parsed block file #63
-INFO - 1490284996: (..\DatabaseBuilder.cpp:268) parsed block file #65
-INFO - 1490285001: (..\DatabaseBuilder.cpp:268) parsed block file #67
-INFO - 1490285004: (..\DatabaseBuilder.cpp:268) parsed block file #69
-INFO - 1490285008: (..\DatabaseBuilder.cpp:268) parsed block file #71
-INFO - 1490285011: (..\DatabaseBuilder.cpp:268) parsed block file #73
-INFO - 1490285014: (..\DatabaseBuilder.cpp:268) parsed block file #75
-INFO - 1490285018: (..\DatabaseBuilder.cpp:268) parsed block file #77
-INFO - 1490285022: (..\DatabaseBuilder.cpp:268) parsed block file #79
-INFO - 1490285026: (..\DatabaseBuilder.cpp:268) parsed block file #81
-INFO - 1490285035: (..\DatabaseBuilder.cpp:268) parsed block file #83
-INFO - 1490285038: (..\DatabaseBuilder.cpp:268) parsed block file #85
-INFO - 1490285041: (..\DatabaseBuilder.cpp:268) parsed block file #87
-INFO - 1490285044: (..\DatabaseBuilder.cpp:268) parsed block file #89
-INFO - 1490285052: (..\DatabaseBuilder.cpp:268) parsed block file #91
-INFO - 1490285057: (..\DatabaseBuilder.cpp:268) parsed block file #93
-INFO - 1490285063: (..\DatabaseBuilder.cpp:268) parsed block file #95
-INFO - 1490285065: (..\DatabaseBuilder.cpp:268) parsed block file #97
-INFO - 1490285068: (..\DatabaseBuilder.cpp:268) parsed block file #99
-INFO - 1490285072: (..\DatabaseBuilder.cpp:268) parsed block file #101
-INFO - 1490285075: (..\DatabaseBuilder.cpp:268) parsed block file #103
-INFO - 1490285078: (..\DatabaseBuilder.cpp:268) parsed block file #105
-INFO - 1490285081: (..\DatabaseBuilder.cpp:268) parsed block file #107
-INFO - 1490285095: (..\DatabaseBuilder.cpp:268) parsed block file #109
-INFO - 1490285098: (..\DatabaseBuilder.cpp:268) parsed block file #111
-INFO - 1490285100: (..\DatabaseBuilder.cpp:268) parsed block file #113
-INFO - 1490285118: (..\DatabaseBuilder.cpp:268) parsed block file #115
-INFO - 1490285128: (..\DatabaseBuilder.cpp:268) parsed block file #117
-INFO - 1490285130: (..\DatabaseBuilder.cpp:268) parsed block file #119
-INFO - 1490285134: (..\DatabaseBuilder.cpp:268) parsed block file #121
-INFO - 1490285137: (..\DatabaseBuilder.cpp:268) parsed block file #123
-INFO - 1490285147: (..\DatabaseBuilder.cpp:268) parsed block file #125
-INFO - 1490285151: (..\DatabaseBuilder.cpp:268) parsed block file #127
-INFO - 1490285155: (..\DatabaseBuilder.cpp:268) parsed block file #129
-INFO - 1490285159: (..\DatabaseBuilder.cpp:268) parsed block file #131
-INFO - 1490285167: (..\DatabaseBuilder.cpp:268) parsed block file #133
-INFO - 1490285170: (..\DatabaseBuilder.cpp:268) parsed block file #135
-INFO - 1490285174: (..\DatabaseBuilder.cpp:268) parsed block file #137
-INFO - 1490285178: (..\DatabaseBuilder.cpp:268) parsed block file #139
-INFO - 1490285182: (..\DatabaseBuilder.cpp:268) parsed block file #141
-INFO - 1490285186: (..\DatabaseBuilder.cpp:268) parsed block file #143
-INFO - 1490285190: (..\DatabaseBuilder.cpp:268) parsed block file #145
-INFO - 1490285194: (..\DatabaseBuilder.cpp:268) parsed block file #147
-INFO - 1490285197: (..\DatabaseBuilder.cpp:268) parsed block file #149
-INFO - 1490285200: (..\DatabaseBuilder.cpp:268) parsed block file #151
-INFO - 1490285203: (..\DatabaseBuilder.cpp:268) parsed block file #153
-INFO - 1490285205: (..\DatabaseBuilder.cpp:268) parsed block file #155
-INFO - 1490285209: (..\DatabaseBuilder.cpp:268) parsed block file #157
-INFO - 1490285216: (..\DatabaseBuilder.cpp:268) parsed block file #159
-INFO - 1490285220: (..\DatabaseBuilder.cpp:268) parsed block file #161
-INFO - 1490285224: (..\DatabaseBuilder.cpp:268) parsed block file #163
-INFO - 1490285227: (..\DatabaseBuilder.cpp:268) parsed block file #165
-INFO - 1490285230: (..\DatabaseBuilder.cpp:268) parsed block file #167
-INFO - 1490285241: (..\DatabaseBuilder.cpp:268) parsed block file #169
-INFO - 1490285256: (..\DatabaseBuilder.cpp:268) parsed block file #171
-INFO - 1490285260: (..\DatabaseBuilder.cpp:268) parsed block file #173
-INFO - 1490285263: (..\DatabaseBuilder.cpp:268) parsed block file #175
-INFO - 1490285265: (..\DatabaseBuilder.cpp:268) parsed block file #177
-INFO - 1490285269: (..\DatabaseBuilder.cpp:268) parsed block file #179
-INFO - 1490285275: (..\DatabaseBuilder.cpp:268) parsed block file #181
-INFO - 1490285278: (..\DatabaseBuilder.cpp:268) parsed block file #183
-INFO - 1490285284: (..\DatabaseBuilder.cpp:268) parsed block file #185
-INFO - 1490285288: (..\DatabaseBuilder.cpp:268) parsed block file #187
-INFO - 1490285290: (..\DatabaseBuilder.cpp:268) parsed block file #189
-INFO - 1490285295: (..\DatabaseBuilder.cpp:268) parsed block file #191
-INFO - 1490285299: (..\DatabaseBuilder.cpp:268) parsed block file #193
-INFO - 1490285301: (..\DatabaseBuilder.cpp:268) parsed block file #195
-INFO - 1490285308: (..\DatabaseBuilder.cpp:268) parsed block file #197
-INFO - 1490285310: (..\DatabaseBuilder.cpp:268) parsed block file #199
-INFO - 1490285313: (..\DatabaseBuilder.cpp:268) parsed block file #201
-INFO - 1490285319: (..\DatabaseBuilder.cpp:268) parsed block file #203
-INFO - 1490285322: (..\DatabaseBuilder.cpp:268) parsed block file #205
-INFO - 1490285326: (..\DatabaseBuilder.cpp:268) parsed block file #207
-INFO - 1490285330: (..\DatabaseBuilder.cpp:268) parsed block file #209
-INFO - 1490285334: (..\DatabaseBuilder.cpp:268) parsed block file #211
-INFO - 1490285338: (..\DatabaseBuilder.cpp:268) parsed block file #213
-INFO - 1490285342: (..\DatabaseBuilder.cpp:268) parsed block file #215
-INFO - 1490285347: (..\DatabaseBuilder.cpp:268) parsed block file #217
-INFO - 1490285354: (..\DatabaseBuilder.cpp:268) parsed block file #219
-INFO - 1490285358: (..\DatabaseBuilder.cpp:268) parsed block file #221
-INFO - 1490285363: (..\DatabaseBuilder.cpp:268) parsed block file #223
-INFO - 1490285366: (..\DatabaseBuilder.cpp:268) parsed block file #225
-INFO - 1490285370: (..\DatabaseBuilder.cpp:268) parsed block file #227
-INFO - 1490285373: (..\DatabaseBuilder.cpp:268) parsed block file #229
-INFO - 1490285377: (..\DatabaseBuilder.cpp:268) parsed block file #231
-INFO - 1490285380: (..\DatabaseBuilder.cpp:268) parsed block file #233
-INFO - 1490285396: (..\DatabaseBuilder.cpp:268) parsed block file #235
-INFO - 1490285400: (..\DatabaseBuilder.cpp:268) parsed block file #237
-INFO - 1490285413: (..\DatabaseBuilder.cpp:268) parsed block file #239
-INFO - 1490285416: (..\DatabaseBuilder.cpp:268) parsed block file #241
-INFO - 1490285420: (..\DatabaseBuilder.cpp:268) parsed block file #243
-INFO - 1490285429: (..\DatabaseBuilder.cpp:268) parsed block file #245
-INFO - 1490285432: (..\DatabaseBuilder.cpp:268) parsed block file #247
-INFO - 1490285438: (..\DatabaseBuilder.cpp:268) parsed block file #249
-INFO - 1490285442: (..\DatabaseBuilder.cpp:268) parsed block file #251
-INFO - 1490285449: (..\DatabaseBuilder.cpp:268) parsed block file #253
-INFO - 1490285453: (..\DatabaseBuilder.cpp:268) parsed block file #255
-INFO - 1490285457: (..\DatabaseBuilder.cpp:268) parsed block file #257
-INFO - 1490285460: (..\DatabaseBuilder.cpp:268) parsed block file #259
-INFO - 1490285464: (..\DatabaseBuilder.cpp:268) parsed block file #261
-INFO - 1490285483: (..\DatabaseBuilder.cpp:268) parsed block file #263
-INFO - 1490285486: (..\DatabaseBuilder.cpp:268) parsed block file #265
-INFO - 1490285491: (..\DatabaseBuilder.cpp:268) parsed block file #267
-INFO - 1490285494: (..\DatabaseBuilder.cpp:268) parsed block file #269
-INFO - 1490285498: (..\DatabaseBuilder.cpp:268) parsed block file #271
-INFO - 1490285507: (..\DatabaseBuilder.cpp:268) parsed block file #273
-INFO - 1490285518: (..\DatabaseBuilder.cpp:268) parsed block file #275
-INFO - 1490285522: (..\DatabaseBuilder.cpp:268) parsed block file #277
-INFO - 1490285525: (..\DatabaseBuilder.cpp:268) parsed block file #279
-INFO - 1490285528: (..\DatabaseBuilder.cpp:268) parsed block file #281
-INFO - 1490285534: (..\DatabaseBuilder.cpp:268) parsed block file #283
-INFO - 1490285543: (..\DatabaseBuilder.cpp:268) parsed block file #285
-INFO - 1490285546: (..\DatabaseBuilder.cpp:268) parsed block file #287
-INFO - 1490285551: (..\DatabaseBuilder.cpp:268) parsed block file #289
-INFO - 1490285555: (..\DatabaseBuilder.cpp:268) parsed block file #291
-INFO - 1490285560: (..\DatabaseBuilder.cpp:268) parsed block file #293
-INFO - 1490285563: (..\DatabaseBuilder.cpp:268) parsed block file #295
-INFO - 1490285569: (..\DatabaseBuilder.cpp:268) parsed block file #297
-INFO - 1490285573: (..\DatabaseBuilder.cpp:268) parsed block file #299
-INFO - 1490285578: (..\DatabaseBuilder.cpp:268) parsed block file #301
-INFO - 1490285581: (..\DatabaseBuilder.cpp:268) parsed block file #303
-INFO - 1490285586: (..\DatabaseBuilder.cpp:268) parsed block file #305
-INFO - 1490285590: (..\DatabaseBuilder.cpp:268) parsed block file #307
-INFO - 1490285592: (..\DatabaseBuilder.cpp:268) parsed block file #309
-INFO - 1490285600: (..\DatabaseBuilder.cpp:268) parsed block file #311
-INFO - 1490285602: (..\DatabaseBuilder.cpp:268) parsed block file #313
-INFO - 1490285610: (..\DatabaseBuilder.cpp:268) parsed block file #315
-INFO - 1490285615: (..\DatabaseBuilder.cpp:268) parsed block file #317
-INFO - 1490285621: (..\DatabaseBuilder.cpp:268) parsed block file #319
-INFO - 1490285624: (..\DatabaseBuilder.cpp:268) parsed block file #321
-INFO - 1490285628: (..\DatabaseBuilder.cpp:268) parsed block file #323
-INFO - 1490285633: (..\DatabaseBuilder.cpp:268) parsed block file #325
-INFO - 1490285655: (..\DatabaseBuilder.cpp:268) parsed block file #327
-INFO - 1490285666: (..\DatabaseBuilder.cpp:268) parsed block file #329
-INFO - 1490285671: (..\DatabaseBuilder.cpp:268) parsed block file #331
-INFO - 1490285676: (..\DatabaseBuilder.cpp:268) parsed block file #333
-INFO - 1490285682: (..\DatabaseBuilder.cpp:268) parsed block file #335
-INFO - 1490285686: (..\DatabaseBuilder.cpp:268) parsed block file #337
-INFO - 1490285697: (..\DatabaseBuilder.cpp:268) parsed block file #339
-INFO - 1490285703: (..\DatabaseBuilder.cpp:268) parsed block file #341
-INFO - 1490285712: (..\DatabaseBuilder.cpp:268) parsed block file #343
-INFO - 1490285719: (..\DatabaseBuilder.cpp:268) parsed block file #345
-INFO - 1490285726: (..\DatabaseBuilder.cpp:268) parsed block file #347
-INFO - 1490285732: (..\DatabaseBuilder.cpp:268) parsed block file #349
-INFO - 1490285742: (..\DatabaseBuilder.cpp:268) parsed block file #351
-INFO - 1490285749: (..\DatabaseBuilder.cpp:268) parsed block file #353
-INFO - 1490285756: (..\DatabaseBuilder.cpp:268) parsed block file #355
-INFO - 1490285768: (..\DatabaseBuilder.cpp:268) parsed block file #357
-INFO - 1490285779: (..\DatabaseBuilder.cpp:268) parsed block file #359
-INFO - 1490285792: (..\DatabaseBuilder.cpp:268) parsed block file #361
-INFO - 1490285801: (..\DatabaseBuilder.cpp:268) parsed block file #363
-INFO - 1490285807: (..\DatabaseBuilder.cpp:268) parsed block file #365
-INFO - 1490285819: (..\DatabaseBuilder.cpp:268) parsed block file #367
-INFO - 1490285828: (..\DatabaseBuilder.cpp:268) parsed block file #369
-INFO - 1490285843: (..\DatabaseBuilder.cpp:268) parsed block file #371
-INFO - 1490285855: (..\DatabaseBuilder.cpp:268) parsed block file #373
-INFO - 1490285863: (..\DatabaseBuilder.cpp:268) parsed block file #375
-INFO - 1490285871: (..\DatabaseBuilder.cpp:268) parsed block file #377
-INFO - 1490285880: (..\DatabaseBuilder.cpp:268) parsed block file #379
-INFO - 1490285890: (..\DatabaseBuilder.cpp:268) parsed block file #381
-INFO - 1490285901: (..\DatabaseBuilder.cpp:268) parsed block file #383
-INFO - 1490285906: (..\DatabaseBuilder.cpp:268) parsed block file #385
-INFO - 1490285911: (..\DatabaseBuilder.cpp:268) parsed block file #387
-INFO - 1490285916: (..\DatabaseBuilder.cpp:268) parsed block file #389
-INFO - 1490285922: (..\DatabaseBuilder.cpp:268) parsed block file #391
-INFO - 1490285927: (..\DatabaseBuilder.cpp:268) parsed block file #393
-INFO - 1490285935: (..\DatabaseBuilder.cpp:268) parsed block file #395
-INFO - 1490285941: (..\DatabaseBuilder.cpp:268) parsed block file #397
-INFO - 1490285947: (..\DatabaseBuilder.cpp:268) parsed block file #399
-INFO - 1490285955: (..\DatabaseBuilder.cpp:268) parsed block file #401
-INFO - 1490285962: (..\DatabaseBuilder.cpp:268) parsed block file #403
-INFO - 1490285969: (..\DatabaseBuilder.cpp:268) parsed block file #405
-INFO - 1490285976: (..\DatabaseBuilder.cpp:268) parsed block file #407
-INFO - 1490285983: (..\DatabaseBuilder.cpp:268) parsed block file #409
-INFO - 1490285992: (..\DatabaseBuilder.cpp:268) parsed block file #411
-INFO - 1490286003: (..\DatabaseBuilder.cpp:268) parsed block file #413
-INFO - 1490286011: (..\DatabaseBuilder.cpp:268) parsed block file #415
-INFO - 1490286018: (..\DatabaseBuilder.cpp:268) parsed block file #417
-INFO - 1490286024: (..\DatabaseBuilder.cpp:268) parsed block file #419
-INFO - 1490286028: (..\DatabaseBuilder.cpp:268) parsed block file #421
-INFO - 1490286035: (..\DatabaseBuilder.cpp:268) parsed block file #423
-INFO - 1490286055: (..\DatabaseBuilder.cpp:268) parsed block file #425
-INFO - 1490286069: (..\DatabaseBuilder.cpp:268) parsed block file #427
-INFO - 1490286079: (..\DatabaseBuilder.cpp:268) parsed block file #429
-INFO - 1490286087: (..\DatabaseBuilder.cpp:268) parsed block file #431
-INFO - 1490286097: (..\DatabaseBuilder.cpp:268) parsed block file #433
-INFO - 1490286105: (..\DatabaseBuilder.cpp:268) parsed block file #435
-INFO - 1490286115: (..\DatabaseBuilder.cpp:268) parsed block file #437
-INFO - 1490286122: (..\DatabaseBuilder.cpp:268) parsed block file #439
-INFO - 1490286127: (..\DatabaseBuilder.cpp:268) parsed block file #441
-INFO - 1490286133: (..\DatabaseBuilder.cpp:268) parsed block file #443
-INFO - 1490286138: (..\DatabaseBuilder.cpp:268) parsed block file #445
-INFO - 1490286142: (..\DatabaseBuilder.cpp:268) parsed block file #447
-INFO - 1490286150: (..\DatabaseBuilder.cpp:268) parsed block file #449
-INFO - 1490286154: (..\DatabaseBuilder.cpp:268) parsed block file #451
-INFO - 1490286162: (..\DatabaseBuilder.cpp:268) parsed block file #453
-INFO - 1490286167: (..\DatabaseBuilder.cpp:268) parsed block file #455
-INFO - 1490286172: (..\DatabaseBuilder.cpp:268) parsed block file #457
-INFO - 1490286178: (..\DatabaseBuilder.cpp:268) parsed block file #459
-INFO - 1490286184: (..\DatabaseBuilder.cpp:268) parsed block file #461
-INFO - 1490286190: (..\DatabaseBuilder.cpp:268) parsed block file #463
-INFO - 1490286198: (..\DatabaseBuilder.cpp:268) parsed block file #465
-INFO - 1490286203: (..\DatabaseBuilder.cpp:268) parsed block file #467
-INFO - 1490286209: (..\DatabaseBuilder.cpp:268) parsed block file #469
-INFO - 1490286214: (..\DatabaseBuilder.cpp:268) parsed block file #471
-INFO - 1490286220: (..\DatabaseBuilder.cpp:268) parsed block file #473
-INFO - 1490286225: (..\DatabaseBuilder.cpp:268) parsed block file #475
-INFO - 1490286229: (..\DatabaseBuilder.cpp:268) parsed block file #477
-INFO - 1490286235: (..\DatabaseBuilder.cpp:268) parsed block file #479
-INFO - 1490286239: (..\DatabaseBuilder.cpp:268) parsed block file #481
-INFO - 1490286243: (..\DatabaseBuilder.cpp:268) parsed block file #483
-INFO - 1490286248: (..\DatabaseBuilder.cpp:268) parsed block file #485
-INFO - 1490286253: (..\DatabaseBuilder.cpp:268) parsed block file #487
-INFO - 1490286258: (..\DatabaseBuilder.cpp:268) parsed block file #489
-INFO - 1490286263: (..\DatabaseBuilder.cpp:268) parsed block file #491
-INFO - 1490286267: (..\DatabaseBuilder.cpp:268) parsed block file #493
-INFO - 1490286272: (..\DatabaseBuilder.cpp:268) parsed block file #495
-INFO - 1490286283: (..\DatabaseBuilder.cpp:268) parsed block file #497
-INFO - 1490286289: (..\DatabaseBuilder.cpp:268) parsed block file #499
-INFO - 1490286299: (..\DatabaseBuilder.cpp:268) parsed block file #501
-INFO - 1490286307: (..\DatabaseBuilder.cpp:268) parsed block file #503
-INFO - 1490286312: (..\DatabaseBuilder.cpp:268) parsed block file #505
-INFO - 1490286318: (..\DatabaseBuilder.cpp:268) parsed block file #507
-INFO - 1490286323: (..\DatabaseBuilder.cpp:268) parsed block file #509
-INFO - 1490286328: (..\DatabaseBuilder.cpp:268) parsed block file #511
-INFO - 1490286334: (..\DatabaseBuilder.cpp:268) parsed block file #513
-INFO - 1490286339: (..\DatabaseBuilder.cpp:268) parsed block file #515
-INFO - 1490286344: (..\DatabaseBuilder.cpp:268) parsed block file #517
-INFO - 1490286349: (..\DatabaseBuilder.cpp:268) parsed block file #519
-INFO - 1490286352: (..\DatabaseBuilder.cpp:268) parsed block file #521
-INFO - 1490286360: (..\DatabaseBuilder.cpp:268) parsed block file #523
-INFO - 1490286365: (..\DatabaseBuilder.cpp:268) parsed block file #525
-INFO - 1490286374: (..\DatabaseBuilder.cpp:268) parsed block file #527
-INFO - 1490286378: (..\DatabaseBuilder.cpp:268) parsed block file #529
-INFO - 1490286384: (..\DatabaseBuilder.cpp:268) parsed block file #531
-INFO - 1490286390: (..\DatabaseBuilder.cpp:268) parsed block file #533
-INFO - 1490286396: (..\DatabaseBuilder.cpp:268) parsed block file #535
-INFO - 1490286402: (..\DatabaseBuilder.cpp:268) parsed block file #537
-INFO - 1490286408: (..\DatabaseBuilder.cpp:268) parsed block file #539
-INFO - 1490286412: (..\DatabaseBuilder.cpp:268) parsed block file #541
-INFO - 1490286417: (..\DatabaseBuilder.cpp:268) parsed block file #543
-INFO - 1490286422: (..\DatabaseBuilder.cpp:268) parsed block file #545
-INFO - 1490286428: (..\DatabaseBuilder.cpp:268) parsed block file #547
-INFO - 1490286435: (..\DatabaseBuilder.cpp:268) parsed block file #549
-INFO - 1490286439: (..\DatabaseBuilder.cpp:268) parsed block file #551
-INFO - 1490286446: (..\DatabaseBuilder.cpp:268) parsed block file #553
-INFO - 1490286451: (..\DatabaseBuilder.cpp:268) parsed block file #555
-INFO - 1490286456: (..\DatabaseBuilder.cpp:268) parsed block file #557
-INFO - 1490286464: (..\DatabaseBuilder.cpp:268) parsed block file #559
-INFO - 1490286468: (..\DatabaseBuilder.cpp:268) parsed block file #561
-INFO - 1490286472: (..\DatabaseBuilder.cpp:268) parsed block file #563
-INFO - 1490286476: (..\DatabaseBuilder.cpp:268) parsed block file #565
-INFO - 1490286481: (..\DatabaseBuilder.cpp:268) parsed block file #567
-INFO - 1490286487: (..\DatabaseBuilder.cpp:268) parsed block file #569
-INFO - 1490286492: (..\DatabaseBuilder.cpp:268) parsed block file #571
-INFO - 1490286497: (..\DatabaseBuilder.cpp:268) parsed block file #573
-INFO - 1490286501: (..\DatabaseBuilder.cpp:268) parsed block file #575
-INFO - 1490286506: (..\DatabaseBuilder.cpp:268) parsed block file #577
-INFO - 1490286511: (..\DatabaseBuilder.cpp:268) parsed block file #579
-INFO - 1490286516: (..\DatabaseBuilder.cpp:268) parsed block file #581
-INFO - 1490286519: (..\DatabaseBuilder.cpp:268) parsed block file #583
-INFO - 1490286525: (..\DatabaseBuilder.cpp:268) parsed block file #585
-INFO - 1490286531: (..\DatabaseBuilder.cpp:268) parsed block file #587
-INFO - 1490286539: (..\DatabaseBuilder.cpp:268) parsed block file #589
-INFO - 1490286545: (..\DatabaseBuilder.cpp:268) parsed block file #591
-INFO - 1490286554: (..\DatabaseBuilder.cpp:268) parsed block file #593
-INFO - 1490286565: (..\DatabaseBuilder.cpp:268) parsed block file #595
-INFO - 1490286584: (..\DatabaseBuilder.cpp:268) parsed block file #597
-INFO - 1490286592: (..\DatabaseBuilder.cpp:268) parsed block file #599
-INFO - 1490286598: (..\DatabaseBuilder.cpp:268) parsed block file #601
-INFO - 1490286604: (..\DatabaseBuilder.cpp:268) parsed block file #603
-INFO - 1490286614: (..\DatabaseBuilder.cpp:268) parsed block file #605
-INFO - 1490286622: (..\DatabaseBuilder.cpp:268) parsed block file #607
-INFO - 1490286630: (..\DatabaseBuilder.cpp:268) parsed block file #609
-INFO - 1490286645: (..\DatabaseBuilder.cpp:268) parsed block file #611
-INFO - 1490286655: (..\DatabaseBuilder.cpp:268) parsed block file #613
-INFO - 1490286665: (..\DatabaseBuilder.cpp:268) parsed block file #615
-INFO - 1490286678: (..\DatabaseBuilder.cpp:268) parsed block file #617
-INFO - 1490286691: (..\DatabaseBuilder.cpp:268) parsed block file #619
-INFO - 1490286708: (..\DatabaseBuilder.cpp:268) parsed block file #621
-INFO - 1490286720: (..\DatabaseBuilder.cpp:268) parsed block file #623
-INFO - 1490286727: (..\DatabaseBuilder.cpp:268) parsed block file #625
-INFO - 1490286734: (..\DatabaseBuilder.cpp:268) parsed block file #627
-INFO - 1490286739: (..\DatabaseBuilder.cpp:268) parsed block file #629
-INFO - 1490286745: (..\DatabaseBuilder.cpp:268) parsed block file #631
-INFO - 1490286751: (..\DatabaseBuilder.cpp:268) parsed block file #633
-INFO - 1490286756: (..\DatabaseBuilder.cpp:268) parsed block file #635
-INFO - 1490286763: (..\DatabaseBuilder.cpp:268) parsed block file #637
-INFO - 1490286769: (..\DatabaseBuilder.cpp:268) parsed block file #639
-INFO - 1490286775: (..\DatabaseBuilder.cpp:268) parsed block file #641
-INFO - 1490286781: (..\DatabaseBuilder.cpp:268) parsed block file #643
-INFO - 1490286787: (..\DatabaseBuilder.cpp:268) parsed block file #645
-INFO - 1490286792: (..\DatabaseBuilder.cpp:268) parsed block file #647
-INFO - 1490286797: (..\DatabaseBuilder.cpp:268) parsed block file #649
-INFO - 1490286803: (..\DatabaseBuilder.cpp:268) parsed block file #651
-INFO - 1490286811: (..\DatabaseBuilder.cpp:268) parsed block file #653
-INFO - 1490286818: (..\DatabaseBuilder.cpp:268) parsed block file #655
-INFO - 1490286822: (..\DatabaseBuilder.cpp:268) parsed block file #657
-INFO - 1490286828: (..\DatabaseBuilder.cpp:268) parsed block file #659
-INFO - 1490286833: (..\DatabaseBuilder.cpp:268) parsed block file #661
-INFO - 1490286837: (..\DatabaseBuilder.cpp:268) parsed block file #663
-INFO - 1490286842: (..\DatabaseBuilder.cpp:268) parsed block file #665
-INFO - 1490286850: (..\DatabaseBuilder.cpp:268) parsed block file #667
-INFO - 1490286854: (..\DatabaseBuilder.cpp:268) parsed block file #669
-INFO - 1490286861: (..\DatabaseBuilder.cpp:268) parsed block file #671
-INFO - 1490286866: (..\DatabaseBuilder.cpp:268) parsed block file #673
-INFO - 1490286869: (..\DatabaseBuilder.cpp:268) parsed block file #675
-INFO - 1490286877: (..\DatabaseBuilder.cpp:268) parsed block file #677
-INFO - 1490286881: (..\DatabaseBuilder.cpp:268) parsed block file #679
-INFO - 1490286886: (..\DatabaseBuilder.cpp:268) parsed block file #681
-INFO - 1490286891: (..\DatabaseBuilder.cpp:268) parsed block file #683
-INFO - 1490286896: (..\DatabaseBuilder.cpp:268) parsed block file #685
-INFO - 1490286901: (..\DatabaseBuilder.cpp:268) parsed block file #687
-INFO - 1490286905: (..\DatabaseBuilder.cpp:268) parsed block file #689
-INFO - 1490286916: (..\DatabaseBuilder.cpp:268) parsed block file #691
-INFO - 1490286924: (..\DatabaseBuilder.cpp:268) parsed block file #693
-INFO - 1490286931: (..\DatabaseBuilder.cpp:268) parsed block file #695
-INFO - 1490286938: (..\DatabaseBuilder.cpp:268) parsed block file #697
-INFO - 1490286944: (..\DatabaseBuilder.cpp:268) parsed block file #699
-INFO - 1490286951: (..\DatabaseBuilder.cpp:268) parsed block file #701
-INFO - 1490286957: (..\DatabaseBuilder.cpp:268) parsed block file #703
-INFO - 1490286966: (..\DatabaseBuilder.cpp:268) parsed block file #705
-INFO - 1490286978: (..\DatabaseBuilder.cpp:268) parsed block file #707
-INFO - 1490286989: (..\DatabaseBuilder.cpp:268) parsed block file #709
-INFO - 1490287000: (..\DatabaseBuilder.cpp:268) parsed block file #711
-INFO - 1490287009: (..\DatabaseBuilder.cpp:268) parsed block file #713
-INFO - 1490287022: (..\DatabaseBuilder.cpp:268) parsed block file #715
-INFO - 1490287030: (..\DatabaseBuilder.cpp:268) parsed block file #717
-INFO - 1490287040: (..\DatabaseBuilder.cpp:268) parsed block file #719
-INFO - 1490287047: (..\DatabaseBuilder.cpp:268) parsed block file #721
-INFO - 1490287054: (..\DatabaseBuilder.cpp:268) parsed block file #723
-INFO - 1490287060: (..\DatabaseBuilder.cpp:268) parsed block file #725
-INFO - 1490287069: (..\DatabaseBuilder.cpp:268) parsed block file #727
-INFO - 1490287077: (..\DatabaseBuilder.cpp:268) parsed block file #729
-INFO - 1490287084: (..\DatabaseBuilder.cpp:268) parsed block file #731
-INFO - 1490287090: (..\DatabaseBuilder.cpp:268) parsed block file #733
-INFO - 1490287096: (..\DatabaseBuilder.cpp:268) parsed block file #735
-INFO - 1490287102: (..\DatabaseBuilder.cpp:268) parsed block file #737
-INFO - 1490287109: (..\DatabaseBuilder.cpp:268) parsed block file #739
-INFO - 1490287117: (..\DatabaseBuilder.cpp:268) parsed block file #741
-INFO - 1490287126: (..\DatabaseBuilder.cpp:268) parsed block file #743
-INFO - 1490287133: (..\DatabaseBuilder.cpp:268) parsed block file #745
-INFO - 1490287144: (..\DatabaseBuilder.cpp:268) parsed block file #747
-INFO - 1490287150: (..\DatabaseBuilder.cpp:268) parsed block file #749
-INFO - 1490287155: (..\DatabaseBuilder.cpp:268) parsed block file #751
-INFO - 1490287159: (..\DatabaseBuilder.cpp:268) parsed block file #753
-INFO - 1490287167: (..\DatabaseBuilder.cpp:268) parsed block file #755
-INFO - 1490287174: (..\DatabaseBuilder.cpp:268) parsed block file #757
-INFO - 1490287180: (..\DatabaseBuilder.cpp:268) parsed block file #759
-INFO - 1490287185: (..\DatabaseBuilder.cpp:268) parsed block file #761
-INFO - 1490287191: (..\DatabaseBuilder.cpp:268) parsed block file #763
-INFO - 1490287198: (..\DatabaseBuilder.cpp:268) parsed block file #765
-INFO - 1490287204: (..\DatabaseBuilder.cpp:268) parsed block file #767
-INFO - 1490287211: (..\DatabaseBuilder.cpp:268) parsed block file #769
-INFO - 1490287219: (..\DatabaseBuilder.cpp:268) parsed block file #771
-INFO - 1490287225: (..\DatabaseBuilder.cpp:268) parsed block file #773
-INFO - 1490287233: (..\DatabaseBuilder.cpp:268) parsed block file #775
-INFO - 1490287239: (..\DatabaseBuilder.cpp:268) parsed block file #777
-INFO - 1490287246: (..\DatabaseBuilder.cpp:268) parsed block file #779
-INFO - 1490287253: (..\DatabaseBuilder.cpp:268) parsed block file #781
-INFO - 1490287261: (..\DatabaseBuilder.cpp:268) parsed block file #783
-INFO - 1490287276: (..\DatabaseBuilder.cpp:268) parsed block file #785
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 23, 2017, 05:59:39 PM
1) Delete your DB
2) Start BitcoinQt manually, make sure it is running fine
3) Start ArmoryDB.exe from the command line, let it complete the build (you should see this line: "Enabling zero-conf tracking")
4) Start ArmoryQt.exe, let it scan
At this point you should be good. If it gets stuck at 3) again, post back with your dbLog.txt
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 23, 2017, 06:05:41 PM
1) Delete your DB
2) Start BitcoinQt manually, make sure it is running fine
3) Start ArmoryDB.exe from the command line, let it complete the build (you should see this line: "Enabling zero-conf tracking")
4) Start ArmoryQt.exe, let it scan
At this point you should be good. If it gets stuck at 3) again, post back with your dbLog.txt
Hello, by "Delete your DB" you mean the content of the Armory\databases Folder or some folders within the Bitcoin-Folder (Bitcoin\databases or Bitcoin\blocks)? BR
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 23, 2017, 06:55:43 PM
C:\Users\ITSN\AppData\Roaming\Armory\databases
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 23, 2017, 10:12:16 PM
Hello, after spending the last hours following that guide Armory started correctly and showed the correct BTC Amount. Unfortunately now I do have the next problem: When trying to send Bitcoin to another address this window appears: http://fs5.directupload.net/images/170323/k9i978rj.png (http://www.directupload.net) Furthermore this message (or trying to send BTC) leads to this line in the dbLog.txt: -ERROR - 1490306869: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038 Any idea how that can be solved? Thank you! Edit: My armory shows "Connected (458598)" in the bottom right corner, but as of right now we are already at Block 458617. It seems that it does not sync for some reason what might be the reason for my problem above. Any ideas?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 23, 2017, 10:25:47 PM
Known bug, fixed in 0.96. You'll have to broadcast the raw signed tx.
Title: Re: Armory 0.95.1 is out
Post by: achow101 on March 23, 2017, 10:31:22 PM
My armory shows "Connected (458598)" in the bottom right corner, but as of right now we are already at Block 458617. It seems that it does not sync for some reason what might be the reason for my problem above.
Any ideas?
Restart Armory. Watch the ArmoryDB window (a command prompt window that will have some output) that appears and your current block count in the bottom right hand corner of Armory. When you want to send, make sure that the block count is up to date and that there is no error in the ArmoryDB window that says anything like "Disconnected from Bitcoin node". If you do see that error, or the ArmoryDB window has disappeared, restart Armory, check those again, then send. Repeat until you are able to send.
The bug that is causing this issue has been fixed for 0.96. The 0.96 testing builds will be out soon, after goatpig finishes implementing RBF for 0.96.
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 23, 2017, 10:37:05 PM
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it :(
Title: Re: Armory 0.95.1 is out
Post by: bitpop on March 24, 2017, 01:25:08 AM
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it :(
I click sign offline then sign it and copy the raw transaction, then I pushtx on blockchain.info
Title: Re: Armory 0.95.1 is out
Post by: FlensGold on March 24, 2017, 06:28:59 AM
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it :(
I click sign offline then sign it and copy the raw transaction, then I pushtx on blockchain.info Thank you, that was very helpful since I never did it this way before. I was able to withdraw my BTC!
Title: Re: Armory 0.95.1 is out
Post by: Portnoy on March 24, 2017, 03:53:28 PM
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it :(
I click sign offline then sign it and copy the raw transaction, then I pushtx on blockchain.info One can use this link to even pick who they want to mine it (e.g. if one wants to avoid that bitcoin unlimited $@!%&^* ) http://www.preferredminer.com/ "Instead of broadcasting to the regular mempool, paste a valid raw signed Bitcoin transaction here to be mined by your preferred miner(s)."
Title: Re: Armory 0.95.1 is out - new problem I discovered yesterday 3-26-2017
Post by: OtisG on March 27, 2017, 11:26:28 AM
After inquiring about Armory 0.95.1 working with Core 0.14.0 (was told yes), I updated my full node a couple of weeks ago to Core 0.14.0, and Armory worked just fine with it.
Armory would launch, then the second Armory DB window would open (less than a minute later), and I could see all my cold wallet balances. I have no recent transactions.
Yesterday, I opened Armory for the first time in a couple of weeks, and now the wheel just spins forever. Reading through this forum for thoughts, I deleted the contents of the Armory database directory (after making a backup copy), but the files never rebuilt (so I put them back).
Any ideas why this has suddenly stopped working? I haven't made any changes to Core since the initial change a couple of weeks ago. Any way forward to debug (Win 7 x64)?
Any help is greatly appreciated.
OtisG
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 27, 2017, 11:54:07 AM
Find you bitcoin.conf, remove rpclogin and rpcpassword fields if you have any. Make sure it has a "server=1" entry, then try again. Otherwise, post your logs.
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on March 30, 2017, 12:10:10 PM
Getting the Python Syntax Warning, running 0.95.1 on Lubuntu.
What version of Python is the one I should install, as I think some versions are not supported ?
Thanks
Title: Re: Armory 0.95.1 is out
Post by: goatpig on March 30, 2017, 12:21:37 PM
2.7
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on April 06, 2017, 07:31:25 PM
2.7
Thanks, that's the one I've got. Now restoring and checking online a wallet I get: /usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals): (python2:2713): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed Also in another terminal screen: /usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals): (python2:2270): Gtk-WARNING **: Theme directory imported-Humanity/192 of theme Lubuntu has no size field BDM is ready! (WARNING) ArmoryUtils.py:2416 - ***Checksum error! Attempting to fix... (WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum! ** Any of these sound familiar, do I need to worry ? Right now armory working still, scanning transaction history. Thanks
Title: Re: Armory 0.95.1 is out
Post by: goatpig on April 06, 2017, 10:11:28 PM
1) The first few errors are just Qt4 warnings, these are all false positives 2) This: (WARNING) ArmoryUtils.py:2416 - ***Checksum error! Attempting to fix...
(WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum!
This means a checksum failed and could not be fixed. I'm not sure what you did to get there. If this is the results of your wallets loading, you should run them through the recovery tool. If you are getting this from restoring a wallet, make sure the wallet ID matches what's on the paper backup.
Title: Re: Armory 0.95.1 is out
Post by: Flanagan on April 08, 2017, 02:58:41 PM
1) The first few errors are just Qt4 warnings, these are all false positives 2) This: (WARNING) ArmoryUtils.py:2416 - ***Checksum error! Attempting to fix...
(WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum!
This means a checksum failed and could not be fixed. I'm not sure what you did to get there. If this is the results of your wallets loading, you should run them through the recovery tool. If you are getting this from restoring a wallet, make sure the wallet ID matches what's on the paper backup. Thanks. The recovery tool ? Is this something in the advanced user ?
Title: Re: Armory 0.95.1 is out
Post by: goatpig on April 08, 2017, 08:53:53 PM
http://imgur.com/a/GwEsH (http://imgur.com/a/GwEsH)
Title: Re: Armory 0.95.1 is out
Post by: OtisG on April 09, 2017, 01:33:41 PM
Hi Goatpig,
I finally have some time to work on this (last post was 3-26).
I tried to launch Armory again this morning.
I tried your suggestion for the bitcoin.conf, but it still errors out.
Here's the part of Armorylog.txt where the (ERROR) begins, then it loops over and over.
2017-04-09 07:00 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Users\\USERNAME\\BitCoin-Blockchain']
2017-04-09 07:00 (INFO) -- SDM.pyc:574 - PID of bitcoind: 8284
2017-04-09 07:00 (INFO) -- SDM.pyc:575 - PID of armory: 4464
2017-04-09 07:00 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '4464', '8284']
2017-04-09 07:00 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-04-09 07:00 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2017-04-09 07:00 (WARNING) -- SDM.pyc:679 - Overriding not-available state. This should happen 0-5 times
2017-04-09 07:00 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
Let me know if you need more of the log file or any of the DBLog file.
Thanks!
Title: Re: Armory 0.95.1 is out
Post by: goatpig on April 09, 2017, 03:17:28 PM
https://bitcointalk.org/index.php?topic=1846233.0
Title: Re: Armory 0.95.1 is out
Post by: OtisG on April 09, 2017, 05:30:49 PM
ok, thanks for the help goatpig!
Title: Re: Armory 0.95.1 is out
Post by: truebits on July 15, 2017, 09:41:51 PM
Hi
I updated my software to the 95.1 and now I get the following error:
-ERROR - 1500150674: (..\lmdb_wrapper.cpp:433) DB version mismatch. Use another dbdir!
Armory never seems to go "online" either?
My Bitcoin core is updated as well.
Any idea why I am getting this error?
logging in C:\Users\Cx\AppData\Roaming\Armory\dbLog.txt
-INFO - 1500150674: (..\main.cpp:23) Running on 4 threads
-INFO - 1500150674: (..\main.cpp:24) Ram usage level: 4
-INFO - 1500150674: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\Cx\AppData
\Roaming\Bitcoin\blocks
-INFO - 1500150674: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\Cx\AppData\Ro
aming\Armory\databases
-INFO - 1500150674: (..\lmdb_wrapper.cpp:388) Opening databases...
-ERROR - 1500150674: (..\lmdb_wrapper.cpp:433) DB version mismatch. Use another
dbdir!
Title: Re: Armory 0.95.1 is out
Post by: goatpig on July 15, 2017, 09:55:27 PM
Delete the content of this folder:
C:\Users\Cx\AppData\Roaming\Armory\databases
|
