Topic: Armory 0.96 is not syncing new blocks from Bitcoin Core 0.14.1 (Read 2479 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?
Jump to: