Topic: Armory 0.96 is not syncing new blocks from Bitcoin Core 0.14.1 (Read 2547 times)
How can CBC even work with on disk encryption? If it's done by using part of the storage device to hold the IVs, no wonder it's damn slow. You should stick XTS.
Quote
There haven't been any sync issues (even with a slow/encrypted HDD), nice job! :-)
This is all you, I have not had time to go over the block delay. Actually it would confirm DB is doing fine on AES128 but chokes on 256
Interesting... so the things I have changed where the encryption strength and deactivation of preventing windows to clear writing cache. But this would definately proof that your assumption of the reduced data transfer rate regarding encryption is true. I'm not sure if the reduction of encryption change had an exponantial or linear impact on that, but it seems XTS-AES 128bit should be the upper limit for ArmoryDB to fetch new block data in-time. At least BitLocker in Windows 10 Pro supports these encryption types: XTS-AES 128bit, XTS-AES 256bit, CBC-AES 128bit, CBC-AES 256bit.
But the CBC types are just necessary for other operating systems than or under Windows 10 for compatibility. So using CBC-AES 128bit might also be not working for Armory, because of the different cipher it may also take a little bit longer to write/read from HDD as CBC has to encrypt each block twice - but that's just speculation.
Quote
There haven't been any sync issues (even with a slow/encrypted HDD), nice job! :-)
This is all you, I have not had time to go over the block delay. Actually it would confirm DB is doing fine on AES128 but chokes on 256
but I have gotten a merkle root mismatch again, BUT without any block deser exception
Getting this error alone is a false positive. The code tests no disk blocks all the time, sometimes they are partial and it won't proceed further. When it's paired with a deser error, it means a block expected to be valid was not. That's the result you want to avoid.
Quote
However during the build&scan process no exception occured what-so-ever, although my ArmoryQt crashed once and after the next start ArmoryQt was 100's of blocks smarter (above) Core...
If you did it while Core was still syncing, the code found the headers but does not yet have the block data, as Core will write the headers first, reserve the size for the block data, and commit that last part eventually.
Understood, thx goatpig. There haven't been any synching issues since decrpyting. Also I have to mention I have encypted my HDD again (this time with 128bit AES) and upgraded to Armory 0.96.0.1-testing build #1 and everything works smooth. There haven't been any sync issues (even with a slow/encrypted HDD), nice job! :-)
Thx for helping me out. Should there occure any issues I will report on that in the testing build thread ;-)
Kind regards,
Mr.Vice
but I have gotten a merkle root mismatch again, BUT without any block deser exception
Getting this error alone is a false positive. The code tests no disk blocks all the time, sometimes they are partial and it won't proceed further. When it's paired with a deser error, it means a block expected to be valid was not. That's the result you want to avoid.
Quote
However during the build&scan process no exception occured what-so-ever, although my ArmoryQt crashed once and after the next start ArmoryQt was 100's of blocks smarter (above) Core...
If you did it while Core was still syncing, the code found the headers but does not yet have the block data, as Core will write the headers first, reserve the size for the block data, and commit that last part eventually.
Don't I have to specify in the config files, that ArmoryQt has to use this custom BDM exclusively?
Client looks for a DB on localhost:9001. If there is one, it will use that instead of spawning its own.
Quote
Because actually if a rebuild and rescan flag has een set, BDM should recognize it and so so, but it just doesn't.
The flag is given to the client. The client needs to spawn the DB itself to pass it the flag. In your case, you should spawn your DB with --rebuild, or wipe the /databases folder
Update on my case:
I have completely decrypted my laptop and have done a rebuild and rescan (also deactivated "prevent windows from emptying HDD's writing cache"). It seems to work until now, but I have gotten a merkle root mismatch again, BUT without any block deser exception (which has never been without since using 0.96 together with my encrypted HDD). So while the block deser exception disappeared the merkle root mismatch still is there. For me that's really strange.
However during the build&scan process no exception occured what-so-ever, although my ArmoryQt crashed once and after the next start ArmoryQt was 100's of blocks smarter (above) Core... So I have no clue what the underlieing problem is. Also it seems to me that when ArmoryDB can't close normally, at the next start of ArmoryQt and ArmoryDB these errors I've mentioned above start to occure...
Don't I have to specify in the config files, that ArmoryQt has to use this custom BDM exclusively?
Client looks for a DB on localhost:9001. If there is one, it will use that instead of spawning its own.
Quote
Because actually if a rebuild and rescan flag has een set, BDM should recognize it and so so, but it just doesn't.
The flag is given to the client. The client needs to spawn the DB itself to pass it the flag. In your case, you should spawn your DB with --rebuild, or wipe the /databases folder
Quote
Could it be possible Armory is still using the old BDM this way?
Unlikely. You can double check by looking at whether ArmoryDB.exe is running.
Quote
Is armorydb.conf in the AppData folder?
If you want to use config files, you have to create them in your Armory datadir (C:\Users\Manfred Reumann\AppData\Roaming\Armory\)
Don't I have to specify in the config files, that ArmoryQt has to use this custom BDM exclusively? Because ArmoryDB doesn't actually start as a hole when firstly executing the custom BDM and afterwards Qt. Because actually if a rebuild and rescan flag has een set, BDM should recognize it and so so, but it just doesn't. So anyway if I want to do a rebuild and rescan I should do this with this new custom BDM?
Quote
Could it be possible Armory is still using the old BDM this way?
Unlikely. You can double check by looking at whether ArmoryDB.exe is running.
Quote
Is armorydb.conf in the AppData folder?
If you want to use config files, you have to create them in your Armory datadir (C:\Users\Manfred Reumann\AppData\Roaming\Armory\)
Run it with your command line args (or set the args in armorydb.conf) then run ArmoryQt and observe the bugs.
I would like to check if I done it wrong over the command line... I've first started my newly generated BlockDataManager.exe and then started ArmoryQt.exe. Could it be possible Armory is still using the old BDM this way? Is armorydb.conf in the AppData folder?
Run it with your command line args (or set the args in armorydb.conf) then run ArmoryQt and observe the bugs.
Not working, but I think I have to do a rebuild and rescan first because the initial errors like block deser, invalid merkle root have already occured last time... but I'll show you the logs first.
Bitcoin Core: debug.log
Code:
2017-05-13 21:12:23 Bitcoin version v0.14.1
2017-05-13 21:12:23 InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2017-05-13 21:12:23 InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2017-05-13 21:12:23 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-05-13 21:12:23 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-05-13 21:12:24 Default data directory C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin
2017-05-13 21:12:24 Using data directory C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\
2017-05-13 21:12:24 Using config file C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\bitcoin.conf
2017-05-13 21:12:24 Using at most 125 automatic connections (2048 file descriptors available)
2017-05-13 21:12:24 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-05-13 21:12:24 Using 2 threads for script verification
2017-05-13 21:12:24 scheduler thread start
2017-05-13 21:12:24 HTTP: creating work queue of depth 16
2017-05-13 21:12:24 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2017-05-13 21:12:24 HTTP: starting 4 worker threads
2017-05-13 21:12:24 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-05-13 21:12:24 Using wallet wallet.dat
2017-05-13 21:12:24 init message: Verifying wallet...
2017-05-13 21:12:24 CDBEnv::Open: LogDir=C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\db.log
2017-05-13 21:12:24 Bound to [::]:8333
2017-05-13 21:12:24 Bound to 0.0.0.0:8333
2017-05-13 21:12:24 Cache configuration:
2017-05-13 21:12:24 * Using 2.0MiB for block index database
2017-05-13 21:12:24 * Using 8.0MiB for chain state database
2017-05-13 21:12:24 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-05-13 21:12:24 init message: Loading block index...
2017-05-13 21:12:24 Opening LevelDB in C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\blocks\index
2017-05-13 21:12:24 Opened LevelDB successfully
2017-05-13 21:12:24 Using obfuscation key for C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-05-13 21:12:24 Opening LevelDB in C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\chainstate
2017-05-13 21:12:25 Opened LevelDB successfully
2017-05-13 21:12:25 Using obfuscation key for C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\chainstate: 7995d0e976831140
2017-05-13 21:12:34 LoadBlockIndexDB: last block file = 864
2017-05-13 21:12:34 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=80, size=78851814, heights=465801...465886, time=2017-05-10...2017-05-11)
2017-05-13 21:12:34 Checking all blk files are present...
2017-05-13 21:12:35 LoadBlockIndexDB: transaction index disabled
2017-05-13 21:12:35 LoadBlockIndexDB: hashBestChain=000000000000000001a93e5a1808693ef52ca24d77ada5afc34cc835ae015ae5 height=465886 date=2017-05-11 09:49:48 progress=0.996918
2017-05-13 21:12:35 init message: Rewinding blocks...
2017-05-13 21:12:36 init message: Verifying blocks...
2017-05-13 21:12:36 Verifying last 6 blocks at level 3
2017-05-13 21:12:36 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-05-13 21:14:51 No coin database inconsistencies in last 7 blocks (14996 transactions)
2017-05-13 21:14:51 block index 146535ms
2017-05-13 21:14:51 init message: Loading wallet...
2017-05-13 21:14:51 nFileVersion = 140100
2017-05-13 21:14:51 Keys: 0 plaintext, 203 encrypted, 203 w/ metadata, 203 total
2017-05-13 21:14:51 wallet 129ms
2017-05-13 21:14:51 setKeyPool.size() = 100
2017-05-13 21:14:51 mapWallet.size() = 0
2017-05-13 21:14:51 mapAddressBook.size() = 1
2017-05-13 21:14:51 mapBlockIndex.size() = 466024
2017-05-13 21:14:51 nBestHeight = 465886
2017-05-13 21:14:51 Failed to open mempool file from disk. Continuing anyway.
2017-05-13 21:14:51 init message: Loading addresses...
2017-05-13 21:14:51 torcontrol thread start
2017-05-13 21:14:51 tor: Got service ID h22udnvqcaelkrwg, advertising service h22udnvqcaelkrwg.onion:8333
2017-05-13 21:14:51 AddLocal(h22udnvqcaelkrwg.onion:8333,4)
2017-05-13 21:14:51 Loaded 64925 addresses from peers.dat 355ms
2017-05-13 21:14:51 init message: Loading banlist...
2017-05-13 21:14:51 init message: Starting network threads...
2017-05-13 21:14:51 net thread start
2017-05-13 21:14:51 init message: Done loading
2017-05-13 21:14:51 addcon thread start
2017-05-13 21:14:51 dnsseed thread start
2017-05-13 21:14:51 opencon thread start
2017-05-13 21:14:51 msghand thread start
2017-05-13 21:14:51 receive version message: Armory:0.96: version 70012, blocks=-1, us=127.0.0.1:8333, peer=0
2017-05-13 21:15:02 Loading addresses from DNS seeds (could take a while)
2017-05-13 21:15:02 0 addresses found from DNS seeds
2017-05-13 21:15:02 dnsseed thread exit
2017-05-13 21:15:12 ERROR: Error reading proxy response
2017-05-13 21:15:13 receive version message: /Satoshi:0.12.0/: version 70012, blocks=466256, us=46.105.100.149:49170, peer=1
2017-05-13 21:15:15 receive version message: /Satoshi:0.13.1/: version 70014, blocks=466256, us=212.83.40.239:32768, peer=2
2017-05-13 21:15:35 ERROR: Error reading proxy response
2017-05-13 21:15:56 ERROR: Error reading proxy response
2017-05-13 21:16:08 UpdateTip: new best=00000000000000000127b26520c9c8b7859c669687b3a52f50da3fa7d9c50569 height=465887 version=0x20000000 log2_work=86.413502 tx=221270934 date='2017-05-11 09:51:17' progress=0.996916 cache=12.5MiB(7464tx)
2017-05-13 21:16:08 UpdateTip: new best=0000000000000000016d8729465b100ae1354aff8c550de31d6b396709557a25 height=465888 version=0x20000000 log2_work=86.413536 tx=221270967 date='2017-05-11 10:11:47' progress=0.996934 cache=12.5MiB(7537tx)
2017-05-13 21:16:08 receive version message: /xbadprobe:1.0/: version 70014, blocks=465166, us=216.150.155.151:8333, peer=3
2017-05-13 21:16:19 UpdateTip: new best=000000000000000000e3e94279f6d403c08ac96aecf813201843d57acc35fe87 height=465889 version=0x20000002 log2_work=86.41357 tx=221273540 date='2017-05-11 10:16:52' progress=0.996938 cache=16.6MiB(12736tx)
2017-05-13 21:16:31 UpdateTip: new best=000000000000000000400459a35d96399d7a1fb207d7791af0397f8a4aaf6f04 height=465890 version=0x20000000 log2_work=86.413603 tx=221275077 date='2017-05-11 10:20:55' progress=0.996942 cache=22.8MiB(16845tx)
2017-05-13 21:16:31 receive version message: /Satoshi:0.13.2/: version 70015, blocks=466257, us=37.187.129.166:43396, peer=4
2017-05-13 21:16:45 UpdateTip: new best=00000000000000000005c250f94b714fbea288b780568239e476a9d69a4fffcc height=465891 version=0x20000000 log2_work=86.413637 tx=221276710 date='2017-05-11 10:31:11' progress=0.996950 cache=24.9MiB(20507tx)
2017-05-13 21:16:45 receive version message: /Satoshi:0.14.1/: version 70015, blocks=466257, us=192.42.116.16:40262, peer=5
2017-05-13 21:17:09 UpdateTip: new best=0000000000000000003cfdc8e26bee0b2c1539ba60f7df35cecfe5b7b778f375 height=465892 version=0x20000000 log2_work=86.413671 tx=221278674 date='2017-05-11 10:42:55' progress=0.996960 cache=32.2MiB(24341tx)
2017-05-13 21:17:09 receive version message: /Satoshi:0.13.2/: version 70015, blocks=466257, us=198.167.223.38:48844, peer=6
2017-05-13 21:17:09 Pre-allocating up to position 0x6000000 in blk00864.dat
2017-05-13 21:17:29 ERROR: Error reading proxy response
2017-05-13 21:17:54 version handshake timeout from 7
2017-05-13 21:18:28 Pre-allocating up to position 0xb00000 in rev00864.dat
2017-05-13 21:18:28 UpdateTip: new best=0000000000000000017aeab36c5f261c1a3ba828a9f4e7352496ef71f5cea56f height=465893 version=0x00000004 log2_work=86.413704 tx=221280996 date='2017-05-11 10:45:23' progress=0.996961 cache=52.7MiB(29549tx)
2017-05-13 21:18:32 version handshake timeout from 8
2017-05-13 21:19:11 UpdateTip: new best=000000000000000000a973dfd6ae4fc6378f6da77fb7cb884dfecc280c4b3341 height=465894 version=0x20000000 log2_work=86.413738 tx=221282906 date='2017-05-11 10:57:03' progress=0.996971 cache=54.8MiB(33705tx)
2017-05-13 21:19:32 ERROR: Error reading proxy response
2017-05-13 21:19:49 UpdateTip: new best=000000000000000001e6e1d086c47781321440c3063b5e9798e35f18ec489817 height=465895 version=0x20000002 log2_work=86.413772 tx=221285434 date='2017-05-11 11:23:44' progress=0.996993 cache=58.0MiB(37974tx)
2017-05-13 21:19:49 version handshake timeout from 9
2017-05-13 21:19:49 UpdateTip: new best=000000000000000001a9c1602ea8d31d3c373137e7e7bb5b9dbc526da89b46cb height=465896 version=0x20000000 log2_work=86.413805 tx=221285435 date='2017-05-11 11:24:06' progress=0.996993 cache=58.0MiB(37975tx)
2017-05-13 21:19:52 ERROR: Error reading proxy response
Bitcoin Armory: armorylog.txt
Code:
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1262 - Armory Version : 0.96
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1263 - Armory Build: : a3d01aa722
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1264 - PyBtcWallet Version : 1.35
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1266 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1267 - User home-directory : C:\Users\Manfred Reumann\AppData\Roaming
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1268 - Satoshi BTC directory : C:\Users\Manfred Reumann\AppData\Roaming\Bitcoin\
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1269 - Armory home dir : C:\Users\Manfred Reumann\AppData\Roaming\Armory\
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs :
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1271 - Total Available RAM : 7.85 GB
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1272 - CPU ID string : Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1273 - Number of CPU cores : 4 cores
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1274 - System is 64-bit : True
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1275 - Preferred Encoding : cp1252
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1276 - Machine Arch : amd64
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1277 - Available HDD (ARM) : 577 GB
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1278 - Available HDD (BTC) : 577 GB
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - thread_count : -1
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - rescan : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - ignoreAllZC : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - rescanBalance : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - disableModules : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - port : None
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - interport : 8223
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - coverageOutputDir: None
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - forceWalletCheck: False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - regtest : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - rebuild : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - nettimeout : 2
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - datadir : DEFAULT
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - clearMempool : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - offline : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - armoryDBDir : DEFAULT
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_port : 9001
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - satoshiPort : DEFAULT
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - useTorSettings : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - netlog : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - keypool : 100
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - coverageInclude : None
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - forceOnline : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - redownload : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - rpcBindAddr : 127.0.0.1
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_ip : 127.0.0.1
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - multisigFile : DEFAULT
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - ram_usage : -1
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - mtdebug : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - logDisable : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - settingsPath : C:\Users\Manfred Reumann\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - language : en
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - db_type : DB_FULL
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - doDebug : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - enableDetSign : True
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - disableConfPermis: False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - testnet : False
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - rpcport : DEFAULT
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - satoshiHome : DEFAULT
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - satoshiRpcport : DEFAULT
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - logFile : C:\Users\Manfred Reumann\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1285 - verbosity : None
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\Manfred Reumann\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: de
2017-05-13 23:12 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-13 23:12 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.
2017-05-13 23:12 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-13 23:12 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-13 23:12 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\Manfred Reumann\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 4
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2172 - Wallet (): " " (No Encryption)
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2172 - Wallet (): " " (No Encryption)
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2172 - Wallet (): " " (Encrypted)
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2172 - Wallet (): " " (Encrypted)
2017-05-13 23:12 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes
2017-05-13 23:12 (INFO) -- MultiSigUtils.pyc:198 - Read in Lockbox:
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user. Done!
2017-05-13 23:12 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1682 - From: Expert
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1690 - To: Expert
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-13 23:12 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-13 23:12 (INFO) -- SDM.pyc:171 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-13 23:12 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-13 23:12 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\Manfred Reumann\\AppData\\Roaming\\Bitcoin\\']
2017-05-13 23:12 (INFO) -- SDM.pyc:443 - PID of bitcoind: 7904
2017-05-13 23:12 (INFO) -- SDM.pyc:444 - PID of armory: 1784
2017-05-13 23:12 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '1784', '7904']
2017-05-13 23:12 (WARNING) -- ArmoryQt.py:1804 - DB is already running
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-13 23:12 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-13 23:12 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-13 23:12 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
Bitcoin Armory: dbLog.txt
Code:
Log file opened at 1494709917: C:\Users\Manfred Reumann\AppData\Roaming/Armory/dbLog.txt
-INFO - 1494709917: (..\main.cpp:23) Running on 4 threads
-INFO - 1494709917: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494709917: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\Manfred Reumann\AppData\Roaming/Bitcoin/blocks
-INFO - 1494709917: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\Manfred Reumann\AppData\Roaming/Armory/databases
-INFO - 1494709917: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494709920: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494709920: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494709922: (..\DatabaseBuilder.cpp:208) Found 465819 headers in db
-INFO - 1494709924: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494709924: (..\DatabaseBuilder.cpp:477) Found next block after skipping 501897bytes
-INFO - 1494709925: (..\DatabaseBuilder.cpp:268) parsed block file #864
-DEBUG - 1494709925: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494709925: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.89s
-INFO - 1494709925: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465813 to #465812
-INFO - 1494709925: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494709925: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494709925: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0s
-INFO - 1494709925: (..\DatabaseBuilder.cpp:160) init db in 5.125s
-INFO - 1494709925: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO - 1494709942: (..\BDM_Server.cpp:996) registered bdv: 40a1b76bd78e96add42d
-INFO - 1494710091: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494710091: (..\nodeRPC.cpp:59) RPC connection established
Run it with your command line args (or set the args in armorydb.conf) then run ArmoryQt and observe the bugs.
This time everything looks good...
Result: Building BlockDataManager
What should I do next after building the "BlackDataManager.exe"?
And many thanks for helping me with that, now I've finally learned how to build from source!...
Result: Building BlockDataManager
Code:
2> BlockDataManager.vcxproj -> C:\Users\..\GitRepository\cppForSwig\x64\Release\BlockDataManager.exe
2> 1 Datei(en) kopiert.
========== Erstellen: 2 erfolgreich, 0 fehlerhaft, 0 aktuell, 0 übersprungen ==========
What should I do next after building the "BlackDataManager.exe"?
And many thanks for helping me with that, now I've finally learned how to build from source!...
I thought you had git installed. Let's do that:
1) Grab "Git for Windows" (google it)
2) After installing that (just go for defaults), you will get a Git Shell. Open it, this should give you a terminal that is git "aware".
3) Now you have to type a bunch of commands in there to clone the repo.
4) First, pick/create a folder for the repo to sit in. Using the shell, cd to that folder.
5) In that type the following commands
6) That should give you all the code you need to build. Now you need to open the .sln file in that codebase using MSVC, redo the delaying change and settings, then build the projects.
EDIT:
Alternatively, you can just copy the code in this repo:
https://github.com/goatpig/libfcgi
and extract it in the /cppForSwig/fcgi folder
1) Grab "Git for Windows" (google it)
2) After installing that (just go for defaults), you will get a Git Shell. Open it, this should give you a terminal that is git "aware".
3) Now you have to type a bunch of commands in there to clone the repo.
4) First, pick/create a folder for the repo to sit in. Using the shell, cd to that folder.
5) In that type the following commands
Code:
git init
git remote add origin https://github.com/goatpig/BitcoinArmory.git
git remote update
git checkout master
git pull
git submodule init
git submodule update
6) That should give you all the code you need to build. Now you need to open the .sln file in that codebase using MSVC, redo the delaying change and settings, then build the projects.
EDIT:
Alternatively, you can just copy the code in this repo:
https://github.com/goatpig/libfcgi
and extract it in the /cppForSwig/fcgi folder
I'm currently at step 5), so it's downloading the repo... sry if I got a little bit desperate for a moment^^
I thought you had git installed. Let's do that:
1) Grab "Git for Windows" (google it)
2) After installing that (just go for defaults), you will get a Git Shell. Open it, this should give you a terminal that is git "aware".
3) Now you have to type a bunch of commands in there to clone the repo.
4) First, pick/create a folder for the repo to sit in. Using the shell, cd to that folder.
5) In that type the following commands
6) That should give you all the code you need to build. Now you need to open the .sln file in that codebase using MSVC, redo the delaying change and settings, then build the projects.
EDIT:
Alternatively, you can just copy the code in this repo:
https://github.com/goatpig/libfcgi
and extract it in the /cppForSwig/fcgi folder
1) Grab "Git for Windows" (google it)
2) After installing that (just go for defaults), you will get a Git Shell. Open it, this should give you a terminal that is git "aware".
3) Now you have to type a bunch of commands in there to clone the repo.
4) First, pick/create a folder for the repo to sit in. Using the shell, cd to that folder.
5) In that type the following commands
Code:
git init
git remote add origin https://github.com/goatpig/BitcoinArmory.git
git remote update
git checkout master
git pull
git submodule init
git submodule update
6) That should give you all the code you need to build. Now you need to open the .sln file in that codebase using MSVC, redo the delaying change and settings, then build the projects.
EDIT:
Alternatively, you can just copy the code in this repo:
https://github.com/goatpig/libfcgi
and extract it in the /cppForSwig/fcgi folder
You didn't download the submodules. Open you git terminal, cd to the code's root folder and type the following:
Code:
git submodule init
git submodule update
I'm really pleased how much effort you brought up in explaining me these steps, but I don't think I will figure that out :-/
You mean the team explorer probably, where I should connect to the github depository? But I can't figure out how to actually do that, sry :-S
I have downloaded the repo manually via the github url you provided in your 0.96 release topic... so there is no connection to your repo where I could download these libaries...
Also I have no clue how to add one in the first place... I have all binaries in my download folder... so when I want to add a local repo I can't select the armory-0.96 folder because it says there is nothing to add...
You didn't download the submodules. Open you git terminal, cd to the code's root folder and type the following:
Code:
git submodule init
git submodule update
1) Actually there is only one file to open. Close everything and do File -> Open Project and pick BitcoinArmory.sln in cppForSwig.
2) Once you have that done, make sure to pick Release and x64 next to the green play button named "Local Windows Debugger"
3) Now you want to introduce the artificial delay checking on disk blocks. Add this line here:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BDM_mainthread.cpp#L219
4) Now build cryptopp: in the solution explorer, pick the cryptopp project then Right Click -> Build
5) Build BlockDataManager.
This should give an ArmoryDB.exe binary in the root folder.
2) Once you have that done, make sure to pick Release and x64 next to the green play button named "Local Windows Debugger"
3) Now you want to introduce the artificial delay checking on disk blocks. Add this line here:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BDM_mainthread.cpp#L219
Quote
auto updateChainLambda = [bdm, this]()->bool
{
this_thread::sleep_for(chrono::seconds(5));
auto reorgState = bdm->readBlkFileUpdate();
if (reorgState.hasNewTop)
{
...
{
this_thread::sleep_for(chrono::seconds(5));
auto reorgState = bdm->readBlkFileUpdate();
if (reorgState.hasNewTop)
{
...
4) Now build cryptopp: in the solution explorer, pick the cryptopp project then Right Click -> Build
5) Build BlockDataManager.
This should give an ArmoryDB.exe binary in the root folder.
4) Build crpytopp
Code:
1>------ Erstellen gestartet: Projekt: cryptopp, Konfiguration: Release x64 ------
1> Performing Custom Build Tools
1> Assembling: C:\Users\..\Downloads\BitcoinArmory-0.96\cppForSwig\cryptopp\x64dll.asm
1> Performing Custom Build Tools
1> Assembling: C:\Users\..\Downloads\BitcoinArmory-0.96\cppForSwig\cryptopp\x64masm.asm
1> 3way.cpp
1> adler32.cpp
1> algebra.cpp
1> algparam.cpp
1> arc4.cpp
1> asn.cpp
1> authenc.cpp
1> base32.cpp
1> base64.cpp
1> basecode.cpp
1> bench.cpp
1> bench2.cpp
1> bfinit.cpp
1> blowfish.cpp
1> blumshub.cpp
1> camellia.cpp
1> cast.cpp
1> casts.cpp
1> cbcmac.cpp
1> ccm.cpp
1> Kompilieren...
1> channels.cpp
1> cmac.cpp
1> cpu.cpp
1> crc.cpp
1> cryptlib.cpp
1> cryptlib_bds.cpp
1> datatest.cpp
1> default.cpp
1> des.cpp
1> dessp.cpp
1> DetSign.cpp
1> dh.cpp
1> dh2.cpp
1> dll.cpp
1> dlltest.cpp
1> dsa.cpp
1> eax.cpp
1> ec2n.cpp
1> eccrypto.cpp
1> ecp.cpp
1> Kompilieren...
1> elgamal.cpp
1> emsa2.cpp
1> eprecomp.cpp
1> esign.cpp
1> files.cpp
1> filters.cpp
1> fips140.cpp
1> fipsalgt.cpp
1> fipstest.cpp
1> gcm.cpp
1> gf256.cpp
1> gf2n.cpp
1> gf2_32.cpp
1> gfpcrypt.cpp
1> gost.cpp
1> gzip.cpp
1> hex.cpp
1> hmac.cpp
1> hrtimer.cpp
1> ida.cpp
1> Kompilieren...
1> idea.cpp
1> integer.cpp
1> iterhash.cpp
1> luc.cpp
1> md2.cpp
1> md4.cpp
1> md5.cpp
1> misc.cpp
1> modes.cpp
1> mqueue.cpp
1> mqv.cpp
1> nbtheory.cpp
1> network.cpp
1> oaep.cpp
1> osrng.cpp
1> pch.cpp
1> pkcspad.cpp
1> polynomi.cpp
1> pssr.cpp
1> pubkey.cpp
1> Kompilieren...
1> queue.cpp
1> rabin.cpp
1> randpool.cpp
1> rc2.cpp
1> rc5.cpp
1> rc6.cpp
1> rdtables.cpp
1> rijndael.cpp
1> ripemd.cpp
1> rng.cpp
1> rsa.cpp
1> rw.cpp
1> safer.cpp
1> salsa.cpp
1> seal.cpp
1> seed.cpp
1> serpent.cpp
1> sha.cpp
1> shacal2.cpp
1> shark.cpp
1> Kompilieren...
1> sharkbox.cpp
1> simple.cpp
1> skipjack.cpp
1> socketft.cpp
1>socketft.cpp(102): warning C4996: 'inet_addr': Use inet_pton() or InetPton() instead or define _WINSOCK_DEPRECATED_NO_WARNINGS to disable deprecated API warnings
1> C:\Program Files (x86)\Windows Kits\8.1\Include\um\winsock2.h(1850): Siehe Deklaration von 'inet_addr'
1>socketft.cpp(136): warning C4996: 'inet_addr': Use inet_pton() or InetPton() instead or define _WINSOCK_DEPRECATED_NO_WARNINGS to disable deprecated API warnings
1> C:\Program Files (x86)\Windows Kits\8.1\Include\um\winsock2.h(1850): Siehe Deklaration von 'inet_addr'
1>socketft.cpp(140): warning C4996: 'gethostbyname': Use getaddrinfo() or GetAddrInfoW() instead or define _WINSOCK_DEPRECATED_NO_WARNINGS to disable deprecated API warnings
1> C:\Program Files (x86)\Windows Kits\8.1\Include\um\winsock2.h(2238): Siehe Deklaration von 'gethostbyname'
1> sosemanuk.cpp
1> square.cpp
1> squaretb.cpp
1> strciphr.cpp
1> tea.cpp
1> test.cpp
1> tftables.cpp
1> tiger.cpp
1> tigertab.cpp
1> trdlocal.cpp
1> ttmac.cpp
1> twofish.cpp
1> vmac.cpp
1> wait.cpp
1> wake.cpp
1> whrlpool.cpp
1> Kompilieren...
1> winpipes.cpp
1> xtr.cpp
1> xtrcrypt.cpp
1> zdeflate.cpp
1> zinflate.cpp
1> zlib.cpp
1> cryptopp.vcxproj -> C:\Users\..\Downloads\BitcoinArmory-0.96\cppForSwig\libs\x64\cryptopp.lib
========== Erstellen: 1 erfolgreich, 0 fehlerhaft, 0 aktuell, 0 übersprungen ==========
5) Build BlockDataManager
Code:
Fehler 71 error C1083: Datei (Include) kann nicht geöffnet werden: "./fcgi/include/fastcgi.h": No such file or directory c:\users\..\downloads\bitcoinarmory-0.96\cppforswig\FcgiMessage.h 16 1 BlockDataManager
Warnung 1 warning C4267: 'Argument': Konvertierung von 'size_t' nach 'uint32_t', Datenverlust möglich c:\users\..\downloads\bitcoinarmory-0.96\cppforswig\TxOutScrRef.h 78 1 BlockDataManager
========== Erstellen: 1 erfolgreich, 1 fehlerhaft, 0 aktuell, 0 übersprungen ==========
I have shortened the above because there haven been 14 errors and over 350 warnings (but all the same in different parts of the code), which I can not post here all. So cryptopp did successfully but BlockDataManager did only partially... what should I do?
For some reason the project is locked on the wrong compiler version. You need to set the compiler to v120. Right click the project, in the General tab, pick it on the platform toolset row.
goatpig, I have absolutely no clue where I should set that configuration :-(
Are you sure I can do that in the express version of vs?
Okay, I hae selected every container in the project explorer and somehow managed to get to this (
For some reason the project is locked on the wrong compiler version. You need to set the compiler to v120. Right click the project, in the General tab, pick it on the platform toolset row.
goatpig, I have absolutely no clue where I should set that configuration :-(
Are you sure I can do that in the express version of vs?
For some reason the project is locked on the wrong compiler version. You need to set the compiler to v120. Right click the project, in the General tab, pick it on the platform toolset row.
1) Actually there is only one file to open. Close everything and do File -> Open Project and pick BitcoinArmory.sln in cppForSwig.
2) Once you have that done, make sure to pick Release and x64 next to the green play button named "Local Windows Debugger"
3) Now you want to introduce the artificial delay checking on disk blocks. Add this line here:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BDM_mainthread.cpp#L219
4) Now build cryptopp: in the solution explorer, pick the cryptopp project then Right Click -> Build
5) Build BlockDataManager.
This should give an ArmoryDB.exe binary in the root folder.
2) Once you have that done, make sure to pick Release and x64 next to the green play button named "Local Windows Debugger"
3) Now you want to introduce the artificial delay checking on disk blocks. Add this line here:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BDM_mainthread.cpp#L219
Quote
auto updateChainLambda = [bdm, this]()->bool
{
this_thread::sleep_for(chrono::seconds(5));
auto reorgState = bdm->readBlkFileUpdate();
if (reorgState.hasNewTop)
{
...
{
this_thread::sleep_for(chrono::seconds(5));
auto reorgState = bdm->readBlkFileUpdate();
if (reorgState.hasNewTop)
{
...
4) Now build cryptopp: in the solution explorer, pick the cryptopp project then Right Click -> Build
5) Build BlockDataManager.
This should give an ArmoryDB.exe binary in the root folder.
I've got the following error messages at step 4:
Code:
Fehler 1 error MSB8020: The build tools for v140 (Platform Toolset = 'v140') cannot be found. To build using the v140 build tools, please install v140 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Upgrade Solution...". C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets 64 5 cryptopp
2 IntelliSense: Die Datei "Quelle" kann nicht geöffnet werden: "./fcgi/include/fcgiapp.h". c:\Users\..\Downloads\BitcoinArmory-0.96\cppForSwig\BDM_Server.h 19 1 BitcoinArmory_CppTests
3 IntelliSense: Die Datei "Quelle" kann nicht geöffnet werden: "./fcgi/include/fcgios.h". c:\Users\..\Downloads\BitcoinArmory-0.96\cppForSwig\BDM_Server.h 20 1 BitcoinArmory_CppTests
4 IntelliSense: Die Datei "Quelle" kann nicht geöffnet werden: "./fcgi/include/fastcgi.h". c:\Users\..\Downloads\BitcoinArmory-0.96\cppForSwig\FcgiMessage.h 16 1 BitcoinArmory_CppTests
It seems I would need some type of tool upgrade?
1) Actually there is only one file to open. Close everything and do File -> Open Project and pick BitcoinArmory.sln in cppForSwig.
2) Once you have that done, make sure to pick Release and x64 next to the green play button named "Local Windows Debugger"
3) Now you want to introduce the artificial delay checking on disk blocks. Add this line here:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BDM_mainthread.cpp#L219
4) Now build cryptopp: in the solution explorer, pick the cryptopp project then Right Click -> Build
5) Build BlockDataManager.
This should give an ArmoryDB.exe binary in the root folder.
2) Once you have that done, make sure to pick Release and x64 next to the green play button named "Local Windows Debugger"
3) Now you want to introduce the artificial delay checking on disk blocks. Add this line here:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BDM_mainthread.cpp#L219
Quote
auto updateChainLambda = [bdm, this]()->bool
{
this_thread::sleep_for(chrono::seconds(5));
auto reorgState = bdm->readBlkFileUpdate();
if (reorgState.hasNewTop)
{
...
{
this_thread::sleep_for(chrono::seconds(5));
auto reorgState = bdm->readBlkFileUpdate();
if (reorgState.hasNewTop)
{
...
4) Now build cryptopp: in the solution explorer, pick the cryptopp project then Right Click -> Build
5) Build BlockDataManager.
This should give an ArmoryDB.exe binary in the root folder.
oic. Building just the DB on Windows is easy enough. You need one piece of software:
Easy enough to find on search engines. Then you want to clone the repo. Once you have that done, I'll walk you through the rest.
Code:
Microsoft Visual Studio Express 2013 for Windows Desktop
Easy enough to find on search engines. Then you want to clone the repo. Once you have that done, I'll walk you through the rest.
Okay, I will install that and inform you when I have it. Thx!
Now I've installed Visual Studio Express 2013 WD and opened every sheet file in the 0.96 repo. What should I do next?
But I've actually no clue how I can import these sheet files into a project map and compile them to run... so it would be great if you could tell me how to do that :-)
I got one problem with version 0.95, then I was advised to let bitcoin download blockchain, instead of leaving Armory to do it. After a week of downloading I then opened Armory to let it build databases and scan transactions and so on, but I forgot to go to settings and have checked that Armory let run bitcoin in the background. This of course, made armory be "online" but with a node offline. I then procceded to let bitcoin sync again, the checked armory to run bitcoin in the background and my issue was solved. Hope that helps you.
oic. Building just the DB on Windows is easy enough. You need one piece of software:
Easy enough to find on search engines. Then you want to clone the repo. Once you have that done, I'll walk you through the rest.
Code:
Microsoft Visual Studio Express 2013 for Windows Desktop
Easy enough to find on search engines. Then you want to clone the repo. Once you have that done, I'll walk you through the rest.
Okay, I will install that and inform you when I have it. Thx!
FWIW, I'm having the same sort of problem on Ubuntu- I'm not receiving TXs that show up on the blockchain. Only thing that seems to work is to wipe out and rebuild the database, and even then it is back to the same issue again in short order.
oic. Building just the DB on Windows is easy enough. You need one piece of software:
Easy enough to find on search engines. Then you want to clone the repo. Once you have that done, I'll walk you through the rest.
Code:
Microsoft Visual Studio Express 2013 for Windows Desktop
Easy enough to find on search engines. Then you want to clone the repo. Once you have that done, I'll walk you through the rest.
Why are you running the code on Windows when you are using a Linux host? It's easier to build on Linux.
No I'm using Windows and activated the Linux subsystem as a feature in Win10 Pro.
Why are you running the code on Windows when you are using a Linux host? It's easier to build on Linux.
If you can build from source on Windows, I can give you a one liner to test my theory. It's fairly easy since you only want to build the DB.
Unfortunatly I don't know how to build from source. I wanted to do so with UASF on Bitcoin Core, but never finished because I was sceptical about the safety of an UASF. But I have activated Windows Subsystem for Linux (beta) by following this guide https://msdn.microsoft.com/en-us/commandline/wsl/install_guide.
Maybe if you could give me a link to an instruction guide I will be able to do so...
If you can build from source on Windows, I can give you a one liner to test my theory. It's fairly easy since you only want to build the DB.
This is my guess at the issue:
Armory gets its new blocks signal from the node, then reads the block data off of disk. Chances are the node pushes the block inv packet before the data is flushed on disk, and the DB ends up just reading a partial block (or only the header).
I'll try to build a unit test with a forced delay to reproduce the issue. I'll need you to test that stuff out when I push the testing builds for .1
Armory gets its new blocks signal from the node, then reads the block data off of disk. Chances are the node pushes the block inv packet before the data is flushed on disk, and the DB ends up just reading a partial block (or only the header).
I'll try to build a unit test with a forced delay to reproduce the issue. I'll need you to test that stuff out when I push the testing builds for .1
Thanks goatpig for your effort, I really appreciate it! I had joined the testing build of 0.96 but this issue occured afterwards, so I was not able to report on that before release - sorry for that.
Of course I will test your mentioned testing build as soon as it's available. This makes absolutely sense - these 256bit AES encyptions can really slow down a HDD. To compensate that I have also activated under my hardware properties the "don't let windows empty your hdd cache" policy to speed things up, but it won't get as fast as an unencrypted HDD.
Kind regards,
Mr.Vice
This is my guess at the issue:
Armory gets its new blocks signal from the node, then reads the block data off of disk. Chances are the node pushes the block inv packet before the data is flushed on disk, and the DB ends up just reading a partial block (or only the header).
I'll try to build a unit test with a forced delay to reproduce the issue. I'll need you to test that stuff out when I push the testing builds for .1
Armory gets its new blocks signal from the node, then reads the block data off of disk. Chances are the node pushes the block inv packet before the data is flushed on disk, and the DB ends up just reading a partial block (or only the header).
I'll try to build a unit test with a forced delay to reproduce the issue. I'll need you to test that stuff out when I push the testing builds for .1
This is fairly odd, I've had the code run for weeks on end. You using a HDD?
I'm using Win10 Pro x64 with the manufacturer's buildt in HDD. I also use Microsoft's BitLocker with a TPM module if that's relavant?
Actually I have a block deser exception again after rebuild & rescan today. :-S
Armory's dbLog.txt
Code:
Log file opened at 1494439626: C:\Users\..\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494439626: (..\main.cpp:23) Running on 4 threads
-INFO - 1494439626: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494439626: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\..\AppData\Roaming\Bitcoin\blocks
-INFO - 1494439626: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\..\AppData\Roaming\Armory\databases
-INFO - 1494439626: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494439628: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494439628: (..\BDM_Server.cpp:996) registered bdv: 0947bfabf926df473789
-INFO - 1494439628: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494439650: (..\DatabaseBuilder.cpp:208) Found 465771 headers in db
-INFO - 1494439652: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494439653: (..\DatabaseBuilder.cpp:477) Found next block after skipping 392700bytes
-INFO - 1494439653: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494439653: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494439654: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 1.547s
-INFO - 1494439654: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465765 to #465764
-INFO - 1494439654: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494439654: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494439654: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO - 1494439654: (..\DatabaseBuilder.cpp:160) init db in 26.057s
-INFO - 1494439654: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO - 1494439729: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494439785: (..\BlockchainScanner.cpp:650) scanned from height #465765 to #465766
-ERROR - 1494439803: (..\DatabaseBuilder.cpp:353) block deser except:
-INFO - 1494439898: (..\BlockchainScanner.cpp:650) scanned from height #465767 to #465768
-INFO - 1494439898: (..\BlockchainScanner.cpp:650) scanned from height #465769 to #465769
-ERROR - 1494439911: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1494439911: (..\BlockDataMap.cpp:80) header has: c7d7e4297efaef06d038403f5f4102aeaf66f453ba34750898683dd153def247
-ERROR - 1494439911: (..\BlockDataMap.cpp:81) block yields: e0db443cd839aa1c07a3525a4c77c6c803e51083b23a5112aef2c77c061314bf
-ERROR - 1494439911: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
The strange thing is that the merkle root's mismatch blocks are always different (the hash values are never the same).
I have shut down Armory normally about 2 hours ago and set my laptop into idle mode - don't know if it's called idle mode in English but I hope you know what I mean. After restarting my Laptop and openening Armory everything loaded like it should but as you see in the log the same issue encounters every time.
I see exactly the same problem with 0.96, similar logs running with params:
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir=f:\armory096 --dbdir=f:\armory096
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir=f:\armory096 --dbdir=f:\armory096
This is fairly odd, I've had the code run for weeks on end. You using a HDD?
How long do you let Armory run for this to happen?
About 4-5 days (not in one rush). I use Armory multiple hours a day. It actually works pretty fine after rebuild and rescan, but when the block deser exception and ivalid merkle root occours it does not take too lang until Armory can not sync anymore. At this stage armorydb often can not close normally any longer (by pressing File>Close).
Recently I have deinstalled Armory from the Program Files directory and installed it in Program Files (x86) instead and I've done a rebuild and rescan again. Let's see how long it may last from now on, but when I see something unusual in the log files I will post it in this thread.
Thanks for helping me out with this!
How long do you let Armory run for this to happen?
Now I've got a block deser exception...
Code:
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494406900: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494406900: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-ERROR - 1494406941: (..\DatabaseBuilder.cpp:353) block deser except:
-ERROR - 1494406967: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1494406967: (..\BlockDataMap.cpp:80) header has: cf96929443598958bbef1e94bcce1c810bda9d9d0dc95d3f901c228f284f1e24
-ERROR - 1494406967: (..\BlockDataMap.cpp:81) block yields: 1c997a4b021a3675498850375b3596f79f44999a72a49db41e15ed9743927433
-ERROR - 1494406967: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-ERROR - 1494407004: (..\DatabaseBuilder.cpp:353) block deser except:
-ERROR - 1494407149: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 1494407149: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO - 1494407174: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN - 1494407330: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494407330: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494407330: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN - 1494407330: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494407349: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494407349: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494407349: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-WARN - 1494407358: (..\BDM_supportClasses.cpp:1891) running 75 zc parser threads
-WARN - 1494407358: (..\BDM_supportClasses.cpp:1891) running 80 zc parser threads
-WARN - 1494407358: (..\BDM_supportClasses.cpp:1891) running 85 zc parser threads
-WARN - 1494407358: (..\BDM_supportClasses.cpp:1891) running 90 zc parser threads
-WARN - 1494407358: (..\BDM_supportClasses.cpp:1891) running 95 zc parser threads
-WARN - 1494407358: (..\BDM_supportClasses.cpp:1891) running 100 zc parser threads
-WARN - 1494407358: (..\BDM_supportClasses.cpp:1891) running 105 zc parser threads
Every now and then there is a problem with the synchronization between Armory and Core. Armory just does not recognize new blocks coming in from Core and the only solution was to do a rebuild and rescan. But it does not help very long, because it occours about every 4-5 days :-/
Can you please help me out with this?
In the log files I did not see any unusual stuff except the missing entry in armorydb regarding the scanning of new blocks. So I will provide the core debug and armorydb logs so you can check the timestamps (it's the log from the same session).
Bitcoin Core debug.log
Armory dbLog.txt
armorylog.txt
Can you please help me out with this?
In the log files I did not see any unusual stuff except the missing entry in armorydb regarding the scanning of new blocks. So I will provide the core debug and armorydb logs so you can check the timestamps (it's the log from the same session).
Bitcoin Core debug.log
Code:
2017-05-10 08:35:16 Bitcoin version v0.14.1
2017-05-10 08:35:16 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-05-10 08:35:16 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-05-10 08:35:16 Default data directory C:\Users\..\AppData\Roaming\Bitcoin
2017-05-10 08:35:16 Using data directory C:\Users\..\AppData\Roaming\Bitcoin\
2017-05-10 08:35:16 Using config file C:\Users\..\AppData\Roaming\Bitcoin\bitcoin.conf
2017-05-10 08:35:16 Using at most 125 automatic connections (2048 file descriptors available)
2017-05-10 08:35:16 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-05-10 08:35:16 Using 2 threads for script verification
2017-05-10 08:35:16 scheduler thread start
2017-05-10 08:35:16 HTTP: creating work queue of depth 16
2017-05-10 08:35:16 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2017-05-10 08:35:16 HTTP: starting 4 worker threads
2017-05-10 08:35:16 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-05-10 08:35:16 Using wallet wallet.dat
2017-05-10 08:35:16 init message: Verifying wallet...
2017-05-10 08:35:16 CDBEnv::Open: LogDir=C:\Users\..\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\..\AppData\Roaming\Bitcoin\db.log
2017-05-10 08:35:16 Bound to [::]:8333
2017-05-10 08:35:16 Bound to 0.0.0.0:8333
2017-05-10 08:35:16 Cache configuration:
2017-05-10 08:35:16 * Using 2.0MiB for block index database
2017-05-10 08:35:16 * Using 8.0MiB for chain state database
2017-05-10 08:35:16 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-05-10 08:35:16 init message: Loading block index...
2017-05-10 08:35:16 Opening LevelDB in C:\Users\..\AppData\Roaming\Bitcoin\blocks\index
2017-05-10 08:35:16 Opened LevelDB successfully
2017-05-10 08:35:16 Using obfuscation key for C:\Users\..\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-05-10 08:35:16 Opening LevelDB in C:\Users\..\AppData\Roaming\Bitcoin\chainstate
2017-05-10 08:35:17 Opened LevelDB successfully
2017-05-10 08:35:17 Using obfuscation key for C:\Users\..\AppData\Roaming\Bitcoin\chainstate: 7995d0e976831140
2017-05-10 08:35:24 LoadBlockIndexDB: last block file = 862
2017-05-10 08:35:24 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=126, size=125107788, heights=465526...465691, time=2017-05-09...2017-05-10)
2017-05-10 08:35:24 Checking all blk files are present...
2017-05-10 08:35:24 LoadBlockIndexDB: transaction index disabled
2017-05-10 08:35:24 LoadBlockIndexDB: hashBestChain=000000000000000000e7417c94d5464de3bee04150b0811254b725a16d38c11a height=465624 date=2017-05-09 15:35:43 progress=0.999114
2017-05-10 08:35:24 init message: Rewinding blocks...
2017-05-10 08:35:26 init message: Verifying blocks...
2017-05-10 08:35:26 Verifying last 6 blocks at level 3
2017-05-10 08:35:26 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-05-10 08:35:29 No coin database inconsistencies in last 7 blocks (14209 transactions)
2017-05-10 08:35:29 block index 12989ms
2017-05-10 08:35:29 init message: Loading wallet...
2017-05-10 08:35:29 nFileVersion = 140100
2017-05-10 08:35:29 Keys: 0 plaintext, 203 encrypted, 203 w/ metadata, 203 total
2017-05-10 08:35:29 wallet 163ms
2017-05-10 08:35:29 setKeyPool.size() = 100
2017-05-10 08:35:29 mapWallet.size() = 0
2017-05-10 08:35:29 mapAddressBook.size() = 1
2017-05-10 08:35:29 mapBlockIndex.size() = 465729
2017-05-10 08:35:29 nBestHeight = 465624
2017-05-10 08:35:29 AddLocal([***]:8333,1)
2017-05-10 08:35:29 Discover: AC10 - ***
2017-05-10 08:35:29 init message: Loading addresses...
2017-05-10 08:35:29 torcontrol thread start
2017-05-10 08:35:29 Loaded 64868 addresses from peers.dat 321ms
2017-05-10 08:35:29 init message: Loading banlist...
2017-05-10 08:35:29 init message: Starting network threads...
2017-05-10 08:35:29 net thread start
2017-05-10 08:35:29 dnsseed thread start
2017-05-10 08:35:29 addcon thread start
2017-05-10 08:35:29 init message: Done loading
2017-05-10 08:35:29 opencon thread start
2017-05-10 08:35:29 msghand thread start
2017-05-10 08:35:40 Loading addresses from DNS seeds (could take a while)
2017-05-10 08:35:41 121 addresses found from DNS seeds
2017-05-10 08:35:41 dnsseed thread exit
2017-05-10 08:35:57 UpdateTip: new best=00000000000000000138253766845fb61b8c3cc80626b6b96a250ab2199e9947 height=465625 version=0x20000002 log2_work=86.404814 tx=220699783 date='2017-05-09 15:41:41' progress=0.999118 cache=12.3MiB(5823tx)
2017-05-10 08:35:57 receive version message: Armory:0.96: version 70012, blocks=-1, us=127.0.0.1:8333, peer=0
2017-05-10 08:36:22 UpdateTip: new best=00000000000000000213f72da45a6b54ed863a2bc2d39074f7bceef264c77e79 height=465626 version=0x20000000 log2_work=86.404846 tx=220702024 date='2017-05-09 15:47:03' progress=0.999123 cache=24.3MiB(11860tx)
2017-05-10 08:36:22 receive version message: /Satoshi:0.14.0/: version 70015, blocks=465722, us=185.12.46.37:51015, peer=1
2017-05-10 08:36:44 UpdateTip: new best=000000000000000000ebfd9bcd60e29e10e2ce382303b5b128144aaec1ca19db height=465627 version=0x20000000 log2_work=86.404878 tx=220704947 date='2017-05-09 15:50:50' progress=0.999126 cache=28.9MiB(18130tx)
2017-05-10 08:36:44 receive version message: /Satoshi:0.14.0/: version 70015, blocks=465722, us=185.12.46.37:51021, peer=2
2017-05-10 08:37:07 UpdateTip: new best=000000000000000001cfa2c6c8e0cc97bc54fd7b025cd79b157d48c90b672744 height=465628 version=0x20000000 log2_work=86.404909 tx=220707407 date='2017-05-09 15:54:11' progress=0.999128 cache=32.9MiB(24033tx)
2017-05-10 08:37:07 ProcessMessages(version, 111 bytes) FAILED peer=3
2017-05-10 08:37:41 UpdateTip: new best=00000000000000000091c8981d610701921d36b4dd6144a7178555f768debb55 height=465629 version=0x20000000 log2_work=86.404941 tx=220710232 date='2017-05-09 15:58:22' progress=0.999131 cache=36.1MiB(29794tx)
2017-05-10 08:37:41 receive version message: /Satoshi:0.13.1/: version 70014, blocks=465722, us=185.12.46.37:51036, peer=4
2017-05-10 08:38:31 UpdateTip: new best=00000000000000000070bcb4ee11f40b71ec116cd69e39a65375d1d758f94074 height=465630 version=0x20000000 log2_work=86.404972 tx=220713653 date='2017-05-09 15:59:25' progress=0.999132 cache=42.3MiB(36331tx)
2017-05-10 08:38:31 version handshake timeout from 5
2017-05-10 08:38:31 receive version message: /Satoshi:0.14.0/: version 70015, blocks=465722, us=185.12.46.37:51040, peer=5
2017-05-10 08:38:43 version handshake timeout from 6
2017-05-10 08:39:00 Pre-allocating up to position 0xd00000 in rev00862.dat
2017-05-10 08:39:00 UpdateTip: new best=000000000000000000372a0fe86acd8ca9618e2574e10eeb0a5c4086e95b0192 height=465631 version=0x20000002 log2_work=86.405004 tx=220716589 date='2017-05-09 16:02:56' progress=0.999134 cache=49.5MiB(41235tx)
2017-05-10 08:39:24 UpdateTip: new best=000000000000000000c40e25052ad2490b3fe9db5a57d6ead3dc0a3b0e6e0ea3 height=465632 version=0x20000002 log2_work=86.405035 tx=220718970 date='2017-05-09 16:09:36' progress=0.999140 cache=56.4MiB(45150tx)
2017-05-10 08:39:24 receive version message: /Satoshi:0.13.1/: version 70014, blocks=465722, us=[2001:0:9d38:6abd:af:397d:46f3:d1da]:51053, peer=7
2017-05-10 08:39:38 version handshake timeout from 7
2017-05-10 08:39:39 UpdateTip: new best=000000000000000000fbed15afc81b8bc81b306b307e09ba236ff4bba4a3553a height=465633 version=0x20000000 log2_work=86.405067 tx=220721687 date='2017-05-09 16:20:15' progress=0.999149 cache=57.9MiB(49341tx)
2017-05-10 08:39:39 receive version message: /Satoshi:0.14.1/: version 70015, blocks=465722, us=185.12.46.37:51058, peer=8
2017-05-10 08:39:54 UpdateTip: new best=0000000000000000017bd9e1ca7cc4052fc161560553fa6b06f655c68f51c435 height=465634 version=0x20000000 log2_work=86.405099 tx=220724818 date='2017-05-09 16:44:18' progress=0.999169 cache=59.2MiB(54065tx)
2017-05-10 08:39:54 receive version message: /Satoshi:0.14.1/: version 70015, blocks=465722, us=185.12.46.37:51070, peer=9
2017-05-10 08:39:54 receive version message: /Satoshi:0.13.1/: version 70014, blocks=465722, us=185.12.46.37:51072, peer=10
2017-05-10 08:40:02 receive version message: /Satoshi:0.14.1/: version 70015, blocks=465722, us=185.12.46.37:51076, peer=11
2017-05-10 08:40:19 UpdateTip: new best=000000000000000000486e27bfdb88eceef9b1894903b71c60574eaef49af05e height=465635 version=0x20000000 log2_work=86.40513 tx=220727697 date='2017-05-09 16:53:51' progress=0.999177 cache=68.8MiB(58525tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:40:35 UpdateTip: new best=000000000000000000eb86562d4eb7d1a64f8d4ccf10f34a9b5a2b162032dc64 height=465636 version=0x20000000 log2_work=86.405162 tx=220730550 date='2017-05-09 16:57:09' progress=0.999180 cache=70.3MiB(62515tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:40:58 UpdateTip: new best=0000000000000000004ff92c9d7f15c824812e04085ea8590bae4b123f418f4e height=465637 version=0x20000000 log2_work=86.405193 tx=220733275 date='2017-05-09 17:09:14' progress=0.999190 cache=73.6MiB(66489tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:41:04 version handshake timeout from 12
2017-05-10 08:41:49 UpdateTip: new best=000000000000000000f56eceef2a1b7440e9f7bdb2b7a3f0a467e01478200ffc height=465638 version=0x20000000 log2_work=86.405225 tx=220735344 date='2017-05-09 17:26:34' progress=0.999205 cache=75.6MiB(70497tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:42:55 UpdateTip: new best=000000000000000000a8462de8becd4fea57eca76ee10582d8fd62cde0883ff9 height=465639 version=0x20000000 log2_work=86.405256 tx=220736726 date='2017-05-09 17:30:11' progress=0.999207 cache=84.5MiB(74279tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:44:58 Pre-allocating up to position 0xe00000 in rev00862.dat
2017-05-10 08:44:58 UpdateTip: new best=000000000000000001e85ec16db1388fe3383c20ed4683493e66c239391e6daa height=465640 version=0x20000000 log2_work=86.405288 tx=220737723 date='2017-05-09 17:31:43' progress=0.999206 cache=85.7MiB(78270tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:45:31 UpdateTip: new best=0000000000000000020c320f9438a67e3a809fe2fd96459310a28fa647065bc6 height=465641 version=0x20000000 log2_work=86.40532 tx=220740456 date='2017-05-09 17:47:51' progress=0.999220 cache=87.2MiB(82193tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:45:48 UpdateTip: new best=000000000000000000e5a92266fc5601dfa711618c3303a681b7bcbe9912e8ab height=465642 version=0x20000000 log2_work=86.405351 tx=220743126 date='2017-05-09 17:59:27' progress=0.999230 cache=90.0MiB(85804tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:46:30 UpdateTip: new best=000000000000000001d2b692385ded133ce6d6d9b96d40171657153af13a9dfa height=465643 version=0x20000002 log2_work=86.405383 tx=220744272 date='2017-05-09 18:01:58' progress=0.999231 cache=91.2MiB(89145tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:46:30 receive version message: /Satoshi:0.14.99/: version 70015, blocks=465724, us=185.12.46.37:51196, peer=15
2017-05-10 08:46:51 UpdateTip: new best=000000000000000001c7e439a2794fcb1a67773c3fcab4fe3bbf592b91c3586e height=465644 version=0x20000000 log2_work=86.405414 tx=220746763 date='2017-05-09 18:09:53' progress=0.999238 cache=94.1MiB(92598tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:47:14 UpdateTip: new best=00000000000000000125fa4b9c9953515f1df30d8c2e507d6e5414b0c8b5c51e height=465645 version=0x20000002 log2_work=86.405446 tx=220748249 date='2017-05-09 18:11:06' progress=0.999239 cache=96.1MiB(95707tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:47:34 UpdateTip: new best=000000000000000000cbb924f7c8fd22c22c26b931489779db251aa2b13f02f8 height=465646 version=0x20000000 log2_work=86.405477 tx=220751099 date='2017-05-09 18:43:44' progress=0.999267 cache=97.7MiB(99407tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:47:53 UpdateTip: new best=000000000000000000cc54bc466cfa2e028a255a75637214a9c85c8f527d728b height=465647 version=0x20000000 log2_work=86.405509 tx=220753659 date='2017-05-09 18:44:17' progress=0.999267 cache=100.4MiB(103004tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:48:12 UpdateTip: new best=000000000000000000f240b4455076c1a6b0a05893f9c6a5e5a94577d6af78dc height=465648 version=0x20000000 log2_work=86.405541 tx=220756160 date='2017-05-09 18:54:36' progress=0.999276 cache=103.8MiB(106284tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:48:26 Pre-allocating up to position 0xf00000 in rev00862.dat
2017-05-10 08:48:27 UpdateTip: new best=00000000000000000118233766a9ca14267543aaf03c51bf97168d10afb4d03d height=465649 version=0x20000002 log2_work=86.405572 tx=220759023 date='2017-05-09 19:09:01' progress=0.999288 cache=104.7MiB(109388tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:48:46 UpdateTip: new best=000000000000000001eb58db60c341ba9e1451ee5f00010833c4514c1d9b1e34 height=465650 version=0x20000000 log2_work=86.405604 tx=220761043 date='2017-05-09 19:11:17' progress=0.999290 cache=106.8MiB(112304tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:48:46 socket recv error Eine vorhandene Verbindung wurde vom Remotehost geschlossen. (10054)
2017-05-10 08:49:31 UpdateTip: new best=000000000000000001e0e484674b9ed64cb71c11599439e0b4fc4444eba96319 height=465651 version=0x20000000 log2_work=86.405635 tx=220761513 date='2017-05-09 19:11:49' progress=0.999289 cache=110.7MiB(116973tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:49:52 version handshake timeout from 16
2017-05-10 08:50:06 UpdateTip: new best=0000000000000000017cee125ae30eacbaca9a006f8f69911843dd8dc71408ee height=465652 version=0x20000000 log2_work=86.405667 tx=220762052 date='2017-05-09 19:14:21' progress=0.999291 cache=111.6MiB(121202tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:50:25 UpdateTip: new best=00000000000000000033c5185c9a6390cf88b60c2ab103e3fee88dda8774404d height=465653 version=0x20000000 log2_work=86.405698 tx=220764091 date='2017-05-09 19:22:53' progress=0.999298 cache=112.5MiB(124181tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:50:37 UpdateTip: new best=00000000000000000123ba44d308180ba5fea3b7a50b483b149aeb53de2a2506 height=465654 version=0x20000002 log2_work=86.40573 tx=220766879 date='2017-05-09 19:30:36' progress=0.999305 cache=114.7MiB(127393tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:51:08 UpdateTip: new best=00000000000000000163673ccbb6bb79e0cb6f64166a2961b098e4b6b5361f86 height=465655 version=0x20000000 log2_work=86.405761 tx=220769680 date='2017-05-09 20:48:12' progress=0.999372 cache=118.5MiB(131758tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:51:20 UpdateTip: new best=0000000000000000012edd52500cdb58ec076e78df4074a382e5c29d59397123 height=465656 version=0x20000000 log2_work=86.405793 tx=220772026 date='2017-05-09 20:50:34' progress=0.999374 cache=119.6MiB(134325tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:51:37 Pre-allocating up to position 0x1000000 in rev00862.dat
2017-05-10 08:51:37 UpdateTip: new best=000000000000000001994cca5ebccc89b7a5ffc7a3c320524542ae417f0d111c height=465657 version=0x20000000 log2_work=86.405825 tx=220774381 date='2017-05-09 21:04:50' progress=0.999386 cache=121.3MiB(137500tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:51:38 receive version message: /Satoshi:0.13.1/: version 70014, blocks=465724, us=185.12.46.37:51318, peer=18
2017-05-10 08:51:42 Leaving block file 862: CBlockFileInfo(blocks=136, size=134209184, heights=465526...465722, time=2017-05-09...2017-05-10)
2017-05-10 08:51:43 Pre-allocating up to position 0x1000000 in blk00863.dat
2017-05-10 08:52:02 Pre-allocating up to position 0x100000 in rev00863.dat
2017-05-10 08:52:02 UpdateTip: new best=00000000000000000164a625cbd750b9b95e29879d10ee64f7d2795c9c33aa99 height=465658 version=0x20000000 log2_work=86.405856 tx=220776698 date='2017-05-09 21:11:35' progress=0.999391 cache=134.6MiB(141499tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:52:21 UpdateTip: new best=00000000000000000067e3b913e6e468b77f7ceba329bbe4010ad7713fce0d01 height=465659 version=0x20000000 log2_work=86.405888 tx=220779522 date='2017-05-09 21:16:43' progress=0.999395 cache=139.6MiB(145219tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:52:21 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-05-10 08:52:21 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=18
2017-05-10 08:52:29 UpdateTip: new best=000000000000000001fef0cbe66464a9cdb0ebfb12588498b6424081485be0fb height=465660 version=0x20000002 log2_work=86.405919 tx=220781576 date='2017-05-09 21:34:37' progress=0.999411 cache=140.3MiB(147449tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:52:30 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-05-10 08:52:30 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=18
2017-05-10 08:53:00 UpdateTip: new best=0000000000000000001910ba63ff808532d7eeb84c0a26b4d6741f9ad7e438ec height=465661 version=0x20000000 log2_work=86.405951 tx=220783491 date='2017-05-09 21:35:03' progress=0.999411 cache=142.3MiB(150940tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:53:51 UpdateTip: new best=0000000000000000015045f89515a251a51125ebaeda4b7fc1b3d591a4538bdc height=465662 version=0x20000002 log2_work=86.405982 tx=220784744 date='2017-05-09 21:40:38' progress=0.999415 cache=149.1MiB(155548tx) warning='2 of last 100 blocks have unexpected version'
2017-05-10 08:54:18 UpdateTip: new best=0000000000000000020b20dfa2ba03b95639110ffec02e86c3bfdffe42344660 height=465663 version=0x20000002 log2_work=86.406014 tx=220786861 date='2017-05-09 21:41:44' progress=0.999415 cache=150.2MiB(159318tx) warning='2 of last 100 blocks have unexpected version'
Armory dbLog.txt
Code:
Log file opened at 1494405316: C:\Users\..\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494405316: (..\main.cpp:23) Running on 4 threads
-INFO - 1494405316: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494405316: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\..\AppData\Roaming\Bitcoin\blocks
-INFO - 1494405316: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\..\AppData\Roaming\Armory\databases
-INFO - 1494405316: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494405317: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494405317: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494405318: (..\BDM_Server.cpp:996) registered bdv: 8408392e90efde6d4d34
-INFO - 1494405320: (..\DatabaseBuilder.cpp:208) Found 465619 headers in db
-INFO - 1494405322: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494405322: (..\DatabaseBuilder.cpp:477) Found next block after skipping 497703bytes
-INFO - 1494405323: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494405323: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494405323: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.814s
-INFO - 1494405323: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465613 to #465612
-INFO - 1494405323: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494405323: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494405323: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO - 1494405323: (..\DatabaseBuilder.cpp:160) init db in 6.154s
-INFO - 1494405323: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO - 1494405357: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494405602: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
armorylog.txt
Code:
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files\Armory\ArmoryQt.exe
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1262 - Armory Version : 0.96
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1263 - Armory Build: : a3d01aa722
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1264 - PyBtcWallet Version : 1.35
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1266 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1267 - User home-directory : C:\Users\..\AppData\Roaming
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1268 - Satoshi BTC directory : C:\Users\..\AppData\Roaming\Bitcoin\
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1269 - Armory home dir : C:\Users\..\AppData\Roaming\Armory\
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs :
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1271 - Total Available RAM : 7.85 GB
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1272 - CPU ID string : Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1273 - Number of CPU cores : 4 cores
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1274 - System is 64-bit : True
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1275 - Preferred Encoding : cp1252
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1276 - Machine Arch : amd64
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1277 - Available HDD (ARM) : 595 GB
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1278 - Available HDD (BTC) : 595 GB
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - thread_count : -1
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - rescan : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - ignoreAllZC : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - rescanBalance : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - disableModules : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - port : None
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - interport : 8223
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - coverageOutputDir: None
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - forceWalletCheck: False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - regtest : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - rebuild : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - nettimeout : 2
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - datadir : DEFAULT
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - clearMempool : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - offline : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - armoryDBDir : DEFAULT
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_port : 9001
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - satoshiPort : DEFAULT
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - useTorSettings : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - netlog : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - keypool : 100
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - coverageInclude : None
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - forceOnline : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - redownload : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - rpcBindAddr : 127.0.0.1
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_ip : 127.0.0.1
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - multisigFile : DEFAULT
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - ram_usage : -1
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - mtdebug : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - logDisable : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - settingsPath : C:\Users\..\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - language : en
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - db_type : DB_FULL
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - doDebug : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - enableDetSign : True
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - disableConfPermis: False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - testnet : False
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - rpcport : DEFAULT
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - satoshiHome : DEFAULT
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - satoshiRpcport : DEFAULT
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - logFile : C:\Users\..\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1285 - verbosity : None
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\..\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: de
2017-05-10 10:35 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-10 10:35 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.
2017-05-10 10:35 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-10 10:35 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-10 10:35 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\..\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 4
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "***" (No Encryption)
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "***" (No Encryption)
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "***" (Encrypted)
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "***" (Encrypted)
2017-05-10 10:35 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes
2017-05-10 10:35 (INFO) -- MultiSigUtils.pyc:198 - Read in Lockbox: ***
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user. Done!
2017-05-10 10:35 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1682 - From: Expert
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1690 - To: Expert
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 10:35 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-10 10:35 (INFO) -- SDM.pyc:171 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-10 10:35 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-10 10:35 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\..\\AppData\\Roaming\\Bitcoin\\']
2017-05-10 10:35 (INFO) -- SDM.pyc:443 - PID of bitcoind: 9124
2017-05-10 10:35 (INFO) -- SDM.pyc:444 - PID of armory: 1932
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '1932', '9124']
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 10:35 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\..\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\..\AppData\Roaming\Armory\" --dbdir="C:\Users\..\AppData\Roaming\Armory\databases"
2017-05-10 10:35 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\..\\AppData\\Roaming\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\..\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\..\\AppData\\Roaming\\Armory\\databases"']
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-10 10:35 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 10:35 (WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
2017-05-10 10:37 (ERROR) -- qtdialogs.pyc:5830 - Error showing TxIn
Traceback (most recent call last):
File "qtdialogs.pyc", line 5828, in showTxInDialog
File "qtdialogs.pyc", line 6001, in __init__
TypeError: sequence item 0: expected string, QString found
Jump to: