Title: Users experiencing the BDM error message
Post by: goatpig on February 27, 2015, 04:13:35 PM
I've pushed a tentative fix in branch 0.93-bugfix. If you build Armory yourself, please pull and test away. We're planning on releasing a build to cover the bugs that made it past the testing phase sometimes next week. This fix in particular we'd like to have some testing on before that upcoming release.
As usual, thank you for your patience, and happy testing =)
Title: Re: Users experiencing the BDM error message
Post by: justusranvier on February 27, 2015, 05:41:26 PM
Compiles, indexes blockchain and runs.
So far, so good.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on February 27, 2015, 05:50:24 PM
I do expect this issue to occur only after bitcoind catches up a day or two worth of blocks. I hope some people will try it over the weekend and give me positive responses as well, although ideally I'd like them to try it once for the sanity check and once more a few days later to confirm the fix.
Also, if everything went well, I'd appreciate seeing log files, which will carry the markers for the DB error and the confirmation it was repaired.
Title: Re: Users experiencing the BDM error message
Post by: crazyivan on February 28, 2015, 05:36:38 PM
I keep getting this BDM error when starting my Armory. I have to rebuild the blockchain almost every time.
Is there a solution for this? It happens not only after catching up. Last time it appeared 3 hours after previous rebuilding of my blockchain so there was no significant catching up.
Title: Re: Users experiencing the BDM error message
Post by: doug_armory on February 28, 2015, 06:30:43 PM
I keep getting this BDM error when starting my Armory. I have to rebuild the blockchain almost every time.
Is there a solution for this? It happens not only after catching up. Last time it appeared 3 hours after previous rebuilding of my blockchain so there was no significant catching up.
Are you running 0.93 or have you built and run the version goatpig mentioned?
Title: Re: Users experiencing the BDM error message
Post by: crazyivan on February 28, 2015, 06:51:20 PM
I keep getting this BDM error when starting my Armory. I have to rebuild the blockchain almost every time.
Is there a solution for this? It happens not only after catching up. Last time it appeared 3 hours after previous rebuilding of my blockchain so there was no significant catching up.
Are you running 0.93 or have you built and run the version goatpig mentioned? 0.93 which I downloaded directly via Armory installer.
Title: Re: Users experiencing the BDM error message
Post by: btchris on February 28, 2015, 07:53:43 PM
I hit the BDM error yesterday. I'm running the 0.93-bugfix branch as of this afternoon. The initial rebuild finished without issue.
I'll post back if I see any of the new log messages in armorycpplog (none so far).
Title: Re: Users experiencing the BDM error message
Post by: doug_armory on February 28, 2015, 08:30:54 PM
I keep getting this BDM error when starting my Armory. I have to rebuild the blockchain almost every time.
Is there a solution for this? It happens not only after catching up. Last time it appeared 3 hours after previous rebuilding of my blockchain so there was no significant catching up.
Are you running 0.93 or have you built and run the version goatpig mentioned? 0.93 which I downloaded directly via Armory installer. You need to either build the version I mentioned or wait for the next release. This was mentioned in the OP.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on February 28, 2015, 08:31:31 PM
I hit the BDM error yesterday. I'm running the 0.93-bugfix branch as of this afternoon. The initial rebuild finished without issue.
I'll post back if I see any of the new log messages in armorycpplog (none so far).
You can quick search for the word "repair". If that shows up, you had the issue again, and the fix worked.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on February 28, 2015, 10:49:13 PM
updated the fix some more, people running this fix please pull and build again.
Title: Re: Users experiencing the BDM error message
Post by: btchris on February 28, 2015, 11:45:58 PM
updated the fix some more, people running this fix please pull and build again.
Thanks, done. You can quick search for the word "repair". If that shows up, you had the issue again, and the fix worked.
Will do (nothing yet).
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 01, 2015, 05:55:54 PM
I don't have any of the "repair" messages yet, but something odd did happen. I've no idea if it's related to this branch, but I sent you the full logs just in case. The only thing odd was the content of the armorycpplog file, there were no other symptoms.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 01, 2015, 06:17:48 PM
I've no idea if it's related to this branch, but I sent you the full logs just in case.
In the support channel? Ticket #? Or did you add a link to this thread, or asked for me by name? The migration to the new ticket system left the support channel in a weird state.
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 01, 2015, 06:23:28 PM
I've no idea if it's related to this branch, but I sent you the full logs just in case.
In the support channel? Ticket #? Or did you add a link to this thread, or asked for me by name? The migration to the new ticket system left the support channel in a weird state. Sorry, I should have been more specific. Ticket: ARMORY00000469, I did mention your name in the ticket body.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 01, 2015, 06:24:30 PM
I've no idea if it's related to this branch, but I sent you the full logs just in case.
In the support channel? Ticket #? Or did you add a link to this thread, or asked for me by name? The migration to the new ticket system left the support channel in a weird state. Sorry, I should have been more specific. Ticket: ARMORY00000469, I did mention your name in the ticket body. Ok great
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 01, 2015, 06:54:39 PM
Sorry, I should have been more specific. Ticket: ARMORY00000469, I did mention your name in the ticket body.
This looks like a benign symptom of the same general issue. Did you make sure Armory was displaying the proper top block?
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 01, 2015, 07:17:26 PM
This looks like a benign symptom of the same general issue. Did you make sure Armory was displaying the proper top block?
I didn't, sorry, but I would guess it wasn't. I shut down Armory just before sending out those log files. I started it back up shortly after (and the symptom did not reoccur). Here's the log from that start: -INFO - 1425231061: (..\BlockUtils.cpp:1597) Reading headers from db
-INFO - 1425231062: (..\BlockUtils.cpp:1623) Found 345730 headers in db
-DEBUG - 1425231062: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425231063: (..\BlockUtils.cpp:1285) --- Fetching SSH summaries for 417 registered addresses
-INFO - 1425231063: (..\BlockUtils.cpp:1298) Left off at file 237, offset 47797915
-INFO - 1425231063: (..\BlockUtils.cpp:1301) Reading headers and building chain...
-INFO - 1425231063: (..\BlockUtils.cpp:1302) Starting at block file 237 offset 47797915
-INFO - 1425231063: (..\BlockUtils.cpp:1304) Block height 345607
-DEBUG - 1425231063: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1425231065: (..\BlockUtils.cpp:1339) Looking for first unrecognized block
-INFO - 1425231065: (..\BlockUtils.cpp:1488) Loading block data... file 237 offset 47797907
-ERROR - 1425231065: (..\BlockUtils.cpp:536) Next block header found at offset 47797915
-INFO - 1425231065: (..\BlockUtils.cpp:564) Reading raw blocks finished at file 237 offset 86249538
-INFO - 1425231065: (..\BlockUtils.cpp:1356) Wrote blocks to DB in 0.029s
-WARN - 1425231065: (..\BlockUtils.cpp:1074) Scanning from 345607 to 345717
-INFO - 1425231065: (..\BlockUtils.cpp:1450) Scanned Block range in 0.86s
-INFO - 1425231065: (..\BlockUtils.cpp:1453) Finished loading at file 237, offset 86249538
-INFO - 1425231065: (..\BlockDataViewer.cpp:155) Enabling zero-conf tracking
The unscanned block numbers 345607 to 345717 roughly correspond with the timestamps in the log file I sent you, that's why I'm guessing it wasn't on the top block. Edit: sorry I'm wrong, 345607 was the most recent block after initially starting Armory (in the logs I sent). The odd logging symptom didn't start until a couple of hours later, so I'm not sure how to interpret the log pasted in above.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 01, 2015, 07:23:27 PM
The unscanned block numbers 345607 to 345717 roughly correspond with the timestamps in the log file I sent you, that's why I'm guessing it wasn't on the top block.
Edit: sorry I'm wrong, 345607 was the most recent block after initially starting Armory (in the logs I sent). The odd logging symptom didn't start until a couple of hours later, so I'm not sure how to interpret the log pasted in above.
Is it displaying the correct top block now?
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 01, 2015, 07:32:34 PM
Is it displaying the correct top block now?
Yes.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 03, 2015, 05:23:42 PM
bump
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 03, 2015, 05:40:11 PM
I've been running a4561d1 since my last post. No issues, however no "repair" log entries either (nor any other unusual log entries).
Title: Re: Users experiencing the BDM error message
Post by: justusranvier on March 03, 2015, 06:41:10 PM
Also have not been a been able to trigger a repair log entry.
Everything just works so far.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 03, 2015, 06:52:15 PM
Also have not been a been able to trigger a repair log entry.
Everything just works so far.
Also have not been a been able to trigger a repair log entry.
Everything just works so far.
As long as it works I'm happy. If you want to forcefully trigger the issue, you can point Armory to a copy of the blockchain it wasn't sync'ed against. Core 0.10 chains will definitely trigger it.
Title: Re: Users experiencing the BDM error message
Post by: justusranvier on March 03, 2015, 10:12:12 PM
If you want to forcefully trigger the issue, you can point Armory to a copy of the blockchain it wasn't sync'ed against. Core 0.10 chains will definitely trigger it.
Instead of doing that, I decided to see what would happen if I just deleted the most recent block file (blk00238.dat) entirely. Turns out that Armory can't repair that. Log file opened at 1425420603: redacted/.armory/armorycpplog.txt
-INFO - 1425420605: (BlockUtils.cpp:861) blkfile dir: redacted/bitcoin/blocks
-INFO - 1425420605: (BlockUtils.cpp:862) lmdb dir: redacted/armory
-INFO - 1425420605: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1425420605: (BlockUtils.cpp:1184) Executing: doInitialSyncOnLoad
-INFO - 1425420605: (BlockUtils.cpp:1255) Total number of blk*.dat files: 239
-INFO - 1425420605: (BlockUtils.cpp:1256) Total blockchain bytes: 31,901,658,075
-INFO - 1425420605: (BlockUtils.cpp:1597) Reading headers from db
-INFO - 1425420609: (BlockUtils.cpp:1623) Found 346096 headers in db
-DEBUG - 1425420609: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425420611: (BlockUtils.cpp:1285) --- Fetching SSH summaries for 1345 registered addresses
-ERROR - 1425420611: (BlockUtils.cpp:639) File: redacted/bitcoin/blocks/blk00238.dat is less than 88 bytes!
-WARN - 1425420611: (BlockUtils.cpp:235) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-ERROR - 1425420611: (BDM_mainthread.cpp:427) BDM thread failed: Block file 'redacted/bitcoin/blocks/blk00238.dat' is the wrong network! File: 00000000, expecting f9beb4d9
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 03, 2015, 10:52:10 PM
If you want to forcefully trigger the issue, you can point Armory to a copy of the blockchain it wasn't sync'ed against. Core 0.10 chains will definitely trigger it.
Instead of doing that, I decided to see what would happen if I just deleted the most recent block file (blk00238.dat) entirely. Turns out that Armory can't repair that. That's an interesting approach. First of all Armory is not supposed to recover from that. It expects to always start at the same or higher height than it saw on its last run. If it fails to find its highest known block, that's an acceptable condition to fail and ask for a factory reset. I don't think it should step away from that assumption at the risk of rolling back history or failing to detect newly available blocks, which are issues harder to identify. The weird thing about your log is that you say you deleted the most recent block file, yet Armory detected 239 available block files, which deserves an investigation on its own.
Title: Re: Users experiencing the BDM error message
Post by: etotheipi on March 04, 2015, 02:02:27 AM
Just pushed goatpig's fix into 0.93.0.70. Yeah weird version number. This will be 0.93.1 after we've confirmed it does what it's supposed to.
As usual, get it from the secure downloader within Armory (help->update software). T
Armory 0.93.0.70-testing for Windows XP, Vista, 7, 8+ (64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_winAll.exe)
Armory 0.93.0.70-testing for MacOSX 10.7+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_osx.tar.gz)
Armory 0.93.0.70-testing for Ubuntu 12.04+ (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_ubuntu-32bit.deb)
Armory 0.93.0.70-testing for Ubuntu 12.04+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_ubuntu-64bit.deb)
Armory 0.93.0.70-testing for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_raspbian-armhf.tar.gz)
Armory 0.93.0.70-testing Offline Bundle for Ubuntu 12.04 exact (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_offline_ubuntu_12.04-32.tar.gz)
Armory 0.93.0.70-testing Offline Bundle for Ubuntu 12.04 exact (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_offline_ubuntu_12.04-64.tar.gz)
Armory 0.93.0.70-testing Offline Bundle for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_rpi_bundle.tar.gz)
Armory 0.93.0.70-testing: Signed hashes of all installers (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.70-testing_sha256sum.txt.asc)
Title: Re: Users experiencing the BDM error message
Post by: zveda2000 on March 04, 2015, 06:18:55 AM
I think I'm all good now after updating to fixes branch. Thanks!
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 04, 2015, 02:58:20 PM
Just wondering, has that been tagged on GitHub yet?
Title: Re: Users experiencing the BDM error message
Post by: etotheipi on March 04, 2015, 03:02:43 PM
Just wondering, has that been tagged on GitHub yet?
I tend not to tag the testing versions, though I have done so a couple times in the past. This particular testing release was really to test that the fix works for those reporting problems, before we commit to an official release. So far it is very promising, so we will probably convert this to an official release soon, with a proper signed tag.
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 04, 2015, 03:16:46 PM
Just wondering, has that been tagged on GitHub yet?
I tend not to tag the testing versions, though I have done so a couple times in the past. This particular testing release was really to test that the fix works for those reporting problems, before we commit to an official release. So far it is very promising, so we will probably convert this to an official release soon, with a proper signed tag. Makes sense, thanks for explaining.
Title: Re: Users experiencing the BDM error message
Post by: zveda2000 on March 04, 2015, 09:21:13 PM
When you update the git, do I need to make clean && make or just make will do to incorporate the updates?
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 04, 2015, 09:36:26 PM
When you update the git, do I need to make clean && make or just make will do to incorporate the updates?
Some changes are Python only and can get away with not rebuilding, but it's a general guideline to make clean & make every time to you pull, regardless of the changes.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 05, 2015, 11:23:09 AM
Been testing 0.93.0.70, and I'm managing to trigger the "BDM error!" dialog still. Logs?
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 05, 2015, 03:30:15 PM
Been testing 0.93.0.70, and I'm managing to trigger the "BDM error!" dialog still. Logs?
Yes please.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 05, 2015, 05:45:37 PM
armorylog.txt: ************************************************************
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1188 - Invoked: /usr/lib/armory-testing/ArmoryQt.py
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1189 - ************************************************************
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1190 - Loading Armory Engine:
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1191 - Armory Version : 0.93.0.70
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1192 - Armory Build: : None
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1193 - PyBtcWallet Version : 1.35
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1194 - Detected Operating system: Linux
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1195 - OS Variant : Fedora-20-Heisenbug
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1196 - User home-directory : /home/user
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1197 - Satoshi BTC directory : /home/user/.bitcoin
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1198 - Armory home dir : /home/user/.armory
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1199 - Detected System Specs :
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1200 - Total Available RAM : 1.05 GB
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1201 - CPU ID string :
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1202 - Number of CPU cores : 4 cores
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1203 - System is 64-bit : True
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1204 - Preferred Encoding : ANSI_X3.4-1968
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1205 - Machine Arch : x86_64
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1206 - Available HDD (ARM) : 124 GB
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1207 - Available HDD (BTC) : 124 GB
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1208 -
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1209 - Network Name: Main Network
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1210 - Satoshi Port: 8333
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1211 - Do wlt check: True
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1212 - Named options/arguments to armoryengine.py:
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - nettimeout : 2
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - rescan : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - ignoreAllZC : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - enableSupernode : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - disableModules : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - port : None
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - interport : 8223
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - skipStatsReport : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - forceWalletCheck: False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - rebuild : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - datadir : /home/user/.armory
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - clearMempool : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - offline : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - coverageOutputDir: None
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - armoryDBDir : DEFAULT
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - satoshiPort : DEFAULT
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - useTorSettings : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - netlog : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - keypool : 100
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - coverageInclude : None
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - forceOnline : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - skipAnnounceCheck: False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - redownload : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - multisigFile : DEFAULT
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - disableTorrent : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - testAnnounceCode: False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - mtdebug : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - logDisable : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - settingsPath : /home/user/.armory/ArmorySettings.txt
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - verbosity : None
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - doDebug : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - enableDetSign : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - testnet : False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - rpcport : DEFAULT
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - satoshiHome : /home/user/.bitcoin
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - satoshiRpcport : DEFAULT
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - logFile : /home/user/.armory/ArmoryQt.py.log.txt
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1214 - disableConfPermis: False
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1215 - Other arguments:
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1218 - ************************************************************
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:1613 - C++ block utilities loaded successfully
2015-03-05 10:01 (INFO) -- BDM.py:408 - Using the asynchronous/multi-threaded BlockDataManager.
2015-03-05 10:01 (INFO) -- BDM.py:409 - Blockchain operations will happen in the background.
2015-03-05 10:01 (INFO) -- BDM.py:410 - Devs: check TheBDM.getState() before asking for data.
2015-03-05 10:01 (INFO) -- BDM.py:411 - Registering addresses during rescans will queue them for
2015-03-05 10:01 (INFO) -- BDM.py:412 - inclusion after the current scan is completed.
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:3517 - Using settings file: /home/user/.armory/ArmorySettings.txt
2015-03-05 10:01 (INFO) -- announcefetch.py:95 - Reading files in fetcher directory:
2015-03-05 10:01 (INFO) -- announcefetch.py:104 - downloads : 6c50e8c8d8bf9800cf532d4b20bf49da7c13436189f6c1b02fa8b28b38829b83
2015-03-05 10:01 (INFO) -- announcefetch.py:104 - notify : eba491396ce1d9667177a6e298ae3485c1db35d10d84f89ec9cd882bac2faa9a
2015-03-05 10:01 (INFO) -- announcefetch.py:104 - announce : 6e4ddffcac6fd1ee8936361362f9a0ebb71b445b77fdfa35cfd50e9163ef164e
2015-03-05 10:01 (INFO) -- announcefetch.py:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-03-05 10:01 (INFO) -- announcefetch.py:104 - changelog : 21669c17b620503c05580053595dbedda1a9c2146b3fda89122e24444a45dc6b
2015-03-05 10:01 (INFO) -- announcefetch.py:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2728 - loadWalletsAndSettings
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2782 - Loading wallets...
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2841 - Number of wallets read in: 1
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2846 - Wallet (): " " (Encrypted)
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2855 - Loading Multisig Lockboxes
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2290 - Setting up networking...
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2319 - Internet status: 2
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2434 - startBitcoindIfNecessary
2015-03-05 10:01 (INFO) -- ArmoryQt.py:2483 - setSatoshiPaths
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['whereis', 'bitcoind']
2015-03-05 10:01 (INFO) -- SDM.py:453 - "whereis" returned: ['/usr/bin/bitcoind']
2015-03-05 10:01 (INFO) -- SDM.py:321 - Found bitcoind in the following places:
2015-03-05 10:01 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 10:01 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 10:01 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 10:01 (INFO) -- SDM.py:325 - Using: /usr/bin/bitcoind
2015-03-05 10:01 (INFO) -- SDM.py:496 - Reading bitcoin.conf file
2015-03-05 10:01 (INFO) -- SDM.py:536 - Setting permissions on bitcoin.conf
2015-03-05 10:01 (INFO) -- SDM.py:597 - Called startBitcoind
2015-03-05 10:01 (INFO) -- SDM.py:282 - Total size of files in /home/user/.bitcoin/blocks is 29.8 GB
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:598 - Executing popen: [u'/usr/bin/bitcoind', '-datadir=/home/user/.bitcoin']
2015-03-05 10:01 (INFO) -- SDM.py:669 - PID of bitcoind: 1449
2015-03-05 10:01 (INFO) -- SDM.py:670 - PID of armory: 1440
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['python', '/usr/lib/armory-testing/guardian.py', '1440', '1449']
2015-03-05 10:01 (INFO) -- SDM.py:834 - Creating proxy in SDM: host=127.0.0.1, port=8332
2015-03-05 10:01 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:598 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:598 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2015-03-05 10:01 (INFO) -- ArmoryUtils.py:598 - Executing popen: find /home/user -type f -name "mimeTypes.rdf"
2015-03-05 10:01 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2015-03-05 10:01 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-03-05 10:01 (INFO) -- ArmoryQt.py:1810 - From: Expert
2015-03-05 10:01 (INFO) -- ArmoryQt.py:1818 - To: Expert
2015-03-05 10:01 (INFO) -- ArmoryQt.py:5876 - Dashboard switched to auto-BadConnection
2015-03-05 10:02 (ERROR) -- announcefetch.py:283 - Specified URL was inaccessible
2015-03-05 10:02 (ERROR) -- announcefetch.py:284 - Tried: https://bitcoinarmory.com/announce.txt
2015-03-05 10:02 (INFO) -- announcefetch.py:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2015-03-05 10:02 (ERROR) -- announcefetch.py:283 - Specified URL was inaccessible
2015-03-05 10:02 (ERROR) -- announcefetch.py:284 - Tried: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2015-03-05 10:02 (WARNING) -- announcefetch.py:297 - Error fetching announce digest
2015-03-05 10:02 (INFO) -- Networking.py:65 - Connection initiated. Start handshake
2015-03-05 10:02 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2015-03-05 10:02 (INFO) -- Networking.py:156 - Received version message from peer:
2015-03-05 10:02 (INFO) -- Networking.py:157 - Version: 70002
2015-03-05 10:02 (INFO) -- Networking.py:158 - SubVersion: /Satoshi:0.10.0/
2015-03-05 10:02 (INFO) -- Networking.py:159 - TimeStamp: 1425549747
2015-03-05 10:02 (INFO) -- Networking.py:160 - StartHeight: 346216
2015-03-05 10:02 (INFO) -- Networking.py:356 - Handshake finished, connection open!
2015-03-05 10:03 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:03 (INFO) -- Networking.py:215 - Received new block. 000000000000000001441a00eb3aa579107b9689aad6fb1df9856147d6c8c522
2015-03-05 10:04 (INFO) -- Networking.py:215 - Received new block. 00000000000000000e5e1837341808e682af6466c640b47f58d0f62b624aaf29
2015-03-05 10:04 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:05 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:06 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:07 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:07 (INFO) -- Networking.py:215 - Received new block. 000000000000000015a092aa9fac1304a9dca9fb8d1845afe46e746c70171c4a
2015-03-05 10:08 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:09 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:10 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:11 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:12 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:13 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:14 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:15 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:16 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:17 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:18 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:19 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:20 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:21 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:22 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:23 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:24 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:25 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:26 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:27 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:28 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:29 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:30 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:30 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2015-03-05 10:30 (INFO) -- SDM.py:683 - Called stopBitcoind
2015-03-05 10:30 (WARNING) -- ArmoryUtils.py:629 - Killing process pid=1449
2015-03-05 10:30 (INFO) -- ArmoryQt.py:6798 - Attempting to close the main window!
2015-03-05 10:30 (ERROR) -- Networking.py:365 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1074 - C++ block utilities loaded successfully
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: free -m
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['cat', '/proc/cpuinfo']
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1184 -
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1185 -
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1186 -
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1187 - ************************************************************
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1188 - Invoked: /usr/lib/armory-testing/ArmoryQt.py
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1189 - ************************************************************
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1190 - Loading Armory Engine:
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1191 - Armory Version : 0.93.0.70
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1192 - Armory Build: : None
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1193 - PyBtcWallet Version : 1.35
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1194 - Detected Operating system: Linux
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1195 - OS Variant : Fedora-20-Heisenbug
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1196 - User home-directory : /home/user
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1197 - Satoshi BTC directory : /home/user/.bitcoin
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1198 - Armory home dir : /home/user/.armory
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1199 - Detected System Specs :
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1200 - Total Available RAM : 1.00 GB
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1201 - CPU ID string :
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1202 - Number of CPU cores : 4 cores
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1203 - System is 64-bit : True
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1204 - Preferred Encoding : ANSI_X3.4-1968
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1205 - Machine Arch : x86_64
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1206 - Available HDD (ARM) : 124 GB
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1207 - Available HDD (BTC) : 124 GB
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1208 -
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1209 - Network Name: Main Network
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1210 - Satoshi Port: 8333
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1211 - Do wlt check: True
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1212 - Named options/arguments to armoryengine.py:
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - nettimeout : 2
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - rescan : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - ignoreAllZC : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - enableSupernode : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - disableModules : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - port : None
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - interport : 8223
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - skipStatsReport : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - forceWalletCheck: False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - rebuild : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - datadir : /home/user/.armory
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - clearMempool : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - offline : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - coverageOutputDir: None
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - armoryDBDir : DEFAULT
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - satoshiPort : DEFAULT
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - useTorSettings : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - netlog : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - keypool : 100
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - coverageInclude : None
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - forceOnline : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - skipAnnounceCheck: False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - redownload : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - multisigFile : DEFAULT
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - disableTorrent : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - testAnnounceCode: False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - mtdebug : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - logDisable : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - settingsPath : /home/user/.armory/ArmorySettings.txt
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - verbosity : None
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - doDebug : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - enableDetSign : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - testnet : False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - rpcport : DEFAULT
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - satoshiHome : /home/user/.bitcoin
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - satoshiRpcport : DEFAULT
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - logFile : /home/user/.armory/ArmoryQt.py.log.txt
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1214 - disableConfPermis: False
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1215 - Other arguments:
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1218 - ************************************************************
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:1613 - C++ block utilities loaded successfully
2015-03-05 10:31 (INFO) -- BDM.py:408 - Using the asynchronous/multi-threaded BlockDataManager.
2015-03-05 10:31 (INFO) -- BDM.py:409 - Blockchain operations will happen in the background.
2015-03-05 10:31 (INFO) -- BDM.py:410 - Devs: check TheBDM.getState() before asking for data.
2015-03-05 10:31 (INFO) -- BDM.py:411 - Registering addresses during rescans will queue them for
2015-03-05 10:31 (INFO) -- BDM.py:412 - inclusion after the current scan is completed.
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:3517 - Using settings file: /home/user/.armory/ArmorySettings.txt
2015-03-05 10:31 (INFO) -- announcefetch.py:95 - Reading files in fetcher directory:
2015-03-05 10:31 (INFO) -- announcefetch.py:104 - downloads : 6c50e8c8d8bf9800cf532d4b20bf49da7c13436189f6c1b02fa8b28b38829b83
2015-03-05 10:31 (INFO) -- announcefetch.py:104 - notify : eba491396ce1d9667177a6e298ae3485c1db35d10d84f89ec9cd882bac2faa9a
2015-03-05 10:31 (INFO) -- announcefetch.py:104 - announce : 6e4ddffcac6fd1ee8936361362f9a0ebb71b445b77fdfa35cfd50e9163ef164e
2015-03-05 10:31 (INFO) -- announcefetch.py:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-03-05 10:31 (INFO) -- announcefetch.py:104 - changelog : 21669c17b620503c05580053595dbedda1a9c2146b3fda89122e24444a45dc6b
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2728 - loadWalletsAndSettings
2015-03-05 10:31 (INFO) -- announcefetch.py:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2782 - Loading wallets...
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2841 - Number of wallets read in: 1
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2846 - Wallet (): " " (Encrypted)
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2855 - Loading Multisig Lockboxes
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2290 - Setting up networking...
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2319 - Internet status: 2
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2434 - startBitcoindIfNecessary
2015-03-05 10:31 (INFO) -- ArmoryQt.py:2483 - setSatoshiPaths
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['whereis', 'bitcoind']
2015-03-05 10:31 (INFO) -- SDM.py:453 - "whereis" returned: ['/usr/bin/bitcoind']
2015-03-05 10:31 (INFO) -- SDM.py:321 - Found bitcoind in the following places:
2015-03-05 10:31 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 10:31 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 10:31 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 10:31 (INFO) -- SDM.py:325 - Using: /usr/bin/bitcoind
2015-03-05 10:31 (INFO) -- SDM.py:496 - Reading bitcoin.conf file
2015-03-05 10:31 (INFO) -- SDM.py:536 - Setting permissions on bitcoin.conf
2015-03-05 10:31 (INFO) -- SDM.py:597 - Called startBitcoind
2015-03-05 10:31 (INFO) -- SDM.py:282 - Total size of files in /home/user/.bitcoin/blocks is 29.8 GB
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: [u'/usr/bin/bitcoind', '-datadir=/home/user/.bitcoin']
2015-03-05 10:31 (INFO) -- SDM.py:669 - PID of bitcoind: 5055
2015-03-05 10:31 (INFO) -- SDM.py:670 - PID of armory: 5046
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['python', '/usr/lib/armory-testing/guardian.py', '5046', '5055']
2015-03-05 10:31 (INFO) -- SDM.py:834 - Creating proxy in SDM: host=127.0.0.1, port=8332
2015-03-05 10:31 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2015-03-05 10:31 (INFO) -- ArmoryUtils.py:598 - Executing popen: find /home/user -type f -name "mimeTypes.rdf"
2015-03-05 10:31 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2015-03-05 10:31 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-03-05 10:31 (INFO) -- ArmoryQt.py:1810 - From: Expert
2015-03-05 10:31 (INFO) -- ArmoryQt.py:1818 - To: Expert
2015-03-05 10:31 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2015-03-05 10:31 (INFO) -- Networking.py:65 - Connection initiated. Start handshake
2015-03-05 10:31 (INFO) -- Networking.py:156 - Received version message from peer:
2015-03-05 10:31 (INFO) -- Networking.py:157 - Version: 70002
2015-03-05 10:31 (INFO) -- Networking.py:158 - SubVersion: /Satoshi:0.10.0/
2015-03-05 10:31 (INFO) -- Networking.py:159 - TimeStamp: 1425551507
2015-03-05 10:31 (INFO) -- Networking.py:160 - StartHeight: 346217
2015-03-05 10:31 (INFO) -- Networking.py:356 - Handshake finished, connection open!
2015-03-05 10:32 (INFO) -- Networking.py:215 - Received new block. 00000000000000000e5e1837341808e682af6466c640b47f58d0f62b624aaf29
2015-03-05 10:32 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:33 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:33 (INFO) -- Networking.py:215 - Received new block. 000000000000000015a092aa9fac1304a9dca9fb8d1845afe46e746c70171c4a
2015-03-05 10:33 (INFO) -- Networking.py:215 - Received new block. 0000000000000000009f2ecef22bb79276b61d302e70d5b49018202ee5d0edb7
2015-03-05 10:33 (INFO) -- Networking.py:215 - Received new block. 0000000000000000072e624c77149505b937b86f7fcf1a42cefcc366edc11951
2015-03-05 10:34 (INFO) -- Networking.py:215 - Received new block. 000000000000000006e826db3e421e73e5d7acf0fbcd4f44731c652d0f3b5ac2
2015-03-05 10:34 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:34 (INFO) -- Networking.py:215 - Received new block. 0000000000000000153abc52a59712e60aadf63d61cebd8acc672043acd614d4
2015-03-05 10:34 (INFO) -- Networking.py:215 - Received new block. 000000000000000001f0d0e37c35fac15d8b567e0e7b3a3bd644f38ebab83f5d
2015-03-05 10:34 (INFO) -- Networking.py:215 - Received new block. 0000000000000000177c7490a351c10c3d0a01da8e7fd2a451e1bc614e9429c1
2015-03-05 10:35 (INFO) -- Networking.py:215 - Received new block. 000000000000000016515b256df9dfe0ce96f02194fc4a7f36d25feee4ae0f45
2015-03-05 10:35 (INFO) -- Networking.py:215 - Received new block. 000000000000000004cb7fc2442761872b542872afdd3e916c0c106c8b10dead
2015-03-05 10:35 (INFO) -- Networking.py:215 - Received new block. 000000000000000009a6c5b7b1424cd2130142d414a2b6f2e66bbfff61e384cd
2015-03-05 10:35 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:35 (INFO) -- Networking.py:215 - Received new block. 000000000000000001113686f8a6863af036333c1b3e16de73ec1cbe63e1a94f
2015-03-05 10:35 (INFO) -- Networking.py:215 - Received new block. 00000000000000000a974cfc482012a332aef4615f0a8bcf094b0b9ae6d405ba
2015-03-05 10:36 (INFO) -- Networking.py:215 - Received new block. 00000000000000000ab3391341a268f0877ee7f2afb3b2aadb95f334b6674e6d
2015-03-05 10:36 (INFO) -- Networking.py:215 - Received new block. 00000000000000000f0b44ceb504ccf4fe262b00ef7b69af6991d16e6d7e7486
2015-03-05 10:36 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:36 (INFO) -- Networking.py:215 - Received new block. 00000000000000000ee1ba35093a736f150a113d0231d50c29b37c3f05d1ae62
2015-03-05 10:36 (INFO) -- Networking.py:215 - Received new block. 000000000000000015a63e8f9079306df69699fb948069066886bb19744251b8
2015-03-05 10:36 (INFO) -- Networking.py:215 - Received new block. 00000000000000001202d8231b3b00dfab0c9b5a6235bd3e9100ac2b10526ad0
2015-03-05 10:36 (INFO) -- Networking.py:215 - Received new block. 00000000000000000971af75d2fc457d256613d2a65177e999e8a94e4657e64f
2015-03-05 10:37 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 10:37 (INFO) -- Networking.py:215 - Received new block. 00000000000000000553ec0d51835158bc7cad3b52a48ca3e6f6cffa1b82e227
2015-03-05 10:37 (INFO) -- Networking.py:215 - Received new block. 00000000000000000281165c5195f2eab9dec857185496da5912c4891f7c1a27
2015-03-05 10:38 (INFO) -- Networking.py:215 - Received new block. 0000000000000000006b16691e6ca737acf8c4041074e02296c2fe3e4b1f628c
2015-03-05 10:38 (INFO) -- Networking.py:215 - Received new block. 000000000000000000471b480dd9d7a7d074d2f4c9da01ea31da33781459af9f
2015-03-05 10:38 (INFO) -- ArmoryQt.py:2517 - loadBlockchainIfNecessary
2015-03-05 10:38 (INFO) -- ArmoryQt.py:2538 - Setting netmode: 1
2015-03-05 10:38 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2015-03-05 10:39 (INFO) -- ArmoryQt.py:3140 - Current block number: 346261
2015-03-05 10:40 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2015-03-05 10:40 (INFO) -- SDM.py:683 - Called stopBitcoind
2015-03-05 10:40 (WARNING) -- ArmoryUtils.py:629 - Killing process pid=5055
2015-03-05 10:40 (ERROR) -- Networking.py:365 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2015-03-05 10:40 (WARNING) -- SDM.py:712 - bitcoind exited, bitcoind STDOUT:
2015-03-05 10:40 (WARNING) -- SDM.py:714 -
2015-03-05 10:40 (WARNING) -- SDM.py:715 - bitcoind exited, bitcoind STDERR:
2015-03-05 10:40 (WARNING) -- SDM.py:717 -
2015-03-05 10:40 (INFO) -- ArmoryQt.py:6798 - Attempting to close the main window!
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1074 - C++ block utilities loaded successfully
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: free -m
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['cat', '/proc/cpuinfo']
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1184 -
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1185 -
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1186 -
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1187 - ************************************************************
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1188 - Invoked: /usr/lib/armory-testing/ArmoryQt.py
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1189 - ************************************************************
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1190 - Loading Armory Engine:
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1191 - Armory Version : 0.93.0.70
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1192 - Armory Build: : None
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1193 - PyBtcWallet Version : 1.35
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1194 - Detected Operating system: Linux
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1195 - OS Variant : Fedora-20-Heisenbug
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1196 - User home-directory : /home/user
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1197 - Satoshi BTC directory : /home/user/.bitcoin
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1198 - Armory home dir : /home/user/.armory
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1199 - Detected System Specs :
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1200 - Total Available RAM : 1.28 GB
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1201 - CPU ID string :
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1202 - Number of CPU cores : 4 cores
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1203 - System is 64-bit : True
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1204 - Preferred Encoding : ANSI_X3.4-1968
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1205 - Machine Arch : x86_64
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1206 - Available HDD (ARM) : 124 GB
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1207 - Available HDD (BTC) : 124 GB
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1208 -
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1209 - Network Name: Main Network
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1210 - Satoshi Port: 8333
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1211 - Do wlt check: True
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1212 - Named options/arguments to armoryengine.py:
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - nettimeout : 2
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - rescan : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - ignoreAllZC : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - enableSupernode : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - disableModules : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - port : None
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - interport : 8223
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - skipStatsReport : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - forceWalletCheck: False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - rebuild : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - datadir : /home/user/.armory
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - clearMempool : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - offline : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - coverageOutputDir: None
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - armoryDBDir : DEFAULT
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - satoshiPort : DEFAULT
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - useTorSettings : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - netlog : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - keypool : 100
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - coverageInclude : None
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - forceOnline : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - skipAnnounceCheck: False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - redownload : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - multisigFile : DEFAULT
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - disableTorrent : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - testAnnounceCode: False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - mtdebug : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - logDisable : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - settingsPath : /home/user/.armory/ArmorySettings.txt
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - verbosity : None
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - doDebug : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - enableDetSign : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - testnet : False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - rpcport : DEFAULT
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - satoshiHome : /home/user/.bitcoin
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - satoshiRpcport : DEFAULT
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - logFile : /home/user/.armory/ArmoryQt.py.log.txt
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1214 - disableConfPermis: False
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1215 - Other arguments:
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1218 - ************************************************************
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:1613 - C++ block utilities loaded successfully
2015-03-05 11:15 (INFO) -- BDM.py:408 - Using the asynchronous/multi-threaded BlockDataManager.
2015-03-05 11:15 (INFO) -- BDM.py:409 - Blockchain operations will happen in the background.
2015-03-05 11:15 (INFO) -- BDM.py:410 - Devs: check TheBDM.getState() before asking for data.
2015-03-05 11:15 (INFO) -- BDM.py:411 - Registering addresses during rescans will queue them for
2015-03-05 11:15 (INFO) -- BDM.py:412 - inclusion after the current scan is completed.
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:3517 - Using settings file: /home/user/.armory/ArmorySettings.txt
2015-03-05 11:15 (INFO) -- announcefetch.py:95 - Reading files in fetcher directory:
2015-03-05 11:15 (INFO) -- announcefetch.py:104 - downloads : 6c50e8c8d8bf9800cf532d4b20bf49da7c13436189f6c1b02fa8b28b38829b83
2015-03-05 11:15 (INFO) -- announcefetch.py:104 - notify : eba491396ce1d9667177a6e298ae3485c1db35d10d84f89ec9cd882bac2faa9a
2015-03-05 11:15 (INFO) -- announcefetch.py:104 - announce : 6e4ddffcac6fd1ee8936361362f9a0ebb71b445b77fdfa35cfd50e9163ef164e
2015-03-05 11:15 (INFO) -- announcefetch.py:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-03-05 11:15 (INFO) -- announcefetch.py:104 - changelog : 21669c17b620503c05580053595dbedda1a9c2146b3fda89122e24444a45dc6b
2015-03-05 11:15 (INFO) -- announcefetch.py:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2728 - loadWalletsAndSettings
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2782 - Loading wallets...
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2841 - Number of wallets read in: 1
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2846 - Wallet (): " " (Encrypted)
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2855 - Loading Multisig Lockboxes
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2290 - Setting up networking...
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2319 - Internet status: 2
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2434 - startBitcoindIfNecessary
2015-03-05 11:15 (INFO) -- ArmoryQt.py:2483 - setSatoshiPaths
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['whereis', 'bitcoind']
2015-03-05 11:15 (INFO) -- SDM.py:453 - "whereis" returned: ['/usr/bin/bitcoind']
2015-03-05 11:15 (INFO) -- SDM.py:321 - Found bitcoind in the following places:
2015-03-05 11:15 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 11:15 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 11:15 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-05 11:15 (INFO) -- SDM.py:325 - Using: /usr/bin/bitcoind
2015-03-05 11:15 (INFO) -- SDM.py:496 - Reading bitcoin.conf file
2015-03-05 11:15 (INFO) -- SDM.py:536 - Setting permissions on bitcoin.conf
2015-03-05 11:15 (INFO) -- SDM.py:597 - Called startBitcoind
2015-03-05 11:15 (INFO) -- SDM.py:282 - Total size of files in /home/user/.bitcoin/blocks is 29.8 GB
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: [u'/usr/bin/bitcoind', '-datadir=/home/user/.bitcoin']
2015-03-05 11:15 (INFO) -- SDM.py:669 - PID of bitcoind: 6382
2015-03-05 11:15 (INFO) -- SDM.py:670 - PID of armory: 6373
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['python', '/usr/lib/armory-testing/guardian.py', '6373', '6382']
2015-03-05 11:15 (INFO) -- SDM.py:834 - Creating proxy in SDM: host=127.0.0.1, port=8332
2015-03-05 11:15 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2015-03-05 11:15 (INFO) -- ArmoryUtils.py:598 - Executing popen: find /home/user -type f -name "mimeTypes.rdf"
2015-03-05 11:15 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2015-03-05 11:15 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-03-05 11:15 (INFO) -- ArmoryQt.py:1810 - From: Expert
2015-03-05 11:15 (INFO) -- ArmoryQt.py:1818 - To: Expert
2015-03-05 11:15 (INFO) -- ArmoryQt.py:5876 - Dashboard switched to auto-BadConnection
2015-03-05 11:15 (ERROR) -- announcefetch.py:283 - Specified URL was inaccessible
2015-03-05 11:15 (ERROR) -- announcefetch.py:284 - Tried: https://bitcoinarmory.com/announce.txt
2015-03-05 11:15 (INFO) -- announcefetch.py:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2015-03-05 11:15 (ERROR) -- announcefetch.py:283 - Specified URL was inaccessible
2015-03-05 11:15 (ERROR) -- announcefetch.py:284 - Tried: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2015-03-05 11:15 (WARNING) -- announcefetch.py:297 - Error fetching announce digest
2015-03-05 11:15 (INFO) -- Networking.py:65 - Connection initiated. Start handshake
2015-03-05 11:15 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2015-03-05 11:16 (INFO) -- Networking.py:156 - Received version message from peer:
2015-03-05 11:16 (INFO) -- Networking.py:157 - Version: 70002
2015-03-05 11:16 (INFO) -- Networking.py:158 - SubVersion: /Satoshi:0.10.0/
2015-03-05 11:16 (INFO) -- Networking.py:159 - TimeStamp: 1425554167
2015-03-05 11:16 (INFO) -- Networking.py:160 - StartHeight: 346218
2015-03-05 11:16 (INFO) -- Networking.py:356 - Handshake finished, connection open!
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 000000000000000015a092aa9fac1304a9dca9fb8d1845afe46e746c70171c4a
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 0000000000000000009f2ecef22bb79276b61d302e70d5b49018202ee5d0edb7
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 0000000000000000072e624c77149505b937b86f7fcf1a42cefcc366edc11951
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 000000000000000006e826db3e421e73e5d7acf0fbcd4f44731c652d0f3b5ac2
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 0000000000000000153abc52a59712e60aadf63d61cebd8acc672043acd614d4
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 000000000000000001f0d0e37c35fac15d8b567e0e7b3a3bd644f38ebab83f5d
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 0000000000000000177c7490a351c10c3d0a01da8e7fd2a451e1bc614e9429c1
2015-03-05 11:16 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 11:16 (INFO) -- Networking.py:215 - Received new block. 000000000000000016515b256df9dfe0ce96f02194fc4a7f36d25feee4ae0f45
2015-03-05 11:17 (INFO) -- Networking.py:215 - Received new block. 000000000000000004cb7fc2442761872b542872afdd3e916c0c106c8b10dead
2015-03-05 11:17 (INFO) -- Networking.py:215 - Received new block. 000000000000000009a6c5b7b1424cd2130142d414a2b6f2e66bbfff61e384cd
2015-03-05 11:17 (INFO) -- Networking.py:215 - Received new block. 000000000000000001113686f8a6863af036333c1b3e16de73ec1cbe63e1a94f
2015-03-05 11:17 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 11:17 (INFO) -- Networking.py:215 - Received new block. 00000000000000000a974cfc482012a332aef4615f0a8bcf094b0b9ae6d405ba
2015-03-05 11:18 (INFO) -- Networking.py:215 - Received new block. 00000000000000000ab3391341a268f0877ee7f2afb3b2aadb95f334b6674e6d
2015-03-05 11:18 (INFO) -- Networking.py:215 - Received new block. 00000000000000000f0b44ceb504ccf4fe262b00ef7b69af6991d16e6d7e7486
2015-03-05 11:18 (ERROR) -- ArmoryQt.py:1952 - failed to process alerts from bitcoind
2015-03-05 11:18 (INFO) -- Networking.py:215 - Received new block. 00000000000000000ee1ba35093a736f150a113d0231d50c29b37c3f05d1ae62
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 000000000000000015a63e8f9079306df69699fb948069066886bb19744251b8
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 00000000000000001202d8231b3b00dfab0c9b5a6235bd3e9100ac2b10526ad0
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 00000000000000000971af75d2fc457d256613d2a65177e999e8a94e4657e64f
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 00000000000000000553ec0d51835158bc7cad3b52a48ca3e6f6cffa1b82e227
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 00000000000000000281165c5195f2eab9dec857185496da5912c4891f7c1a27
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 0000000000000000006b16691e6ca737acf8c4041074e02296c2fe3e4b1f628c
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 000000000000000000471b480dd9d7a7d074d2f4c9da01ea31da33781459af9f
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 000000000000000003a646e244532299232cc742351c1412262922a8d239bdfb
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 0000000000000000039f17297dbcf592ab06724d56699a5c0154375d12322bcf
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 000000000000000008596bd7ca15fb534a119cd5d219508df39d95e2272c6b4e
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 00000000000000001218baf83cfa736815ff7f78fd39469695d674ccc2aff63a
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 0000000000000000129b3500e6bd4d167c8f61d7a38922bba73c0d075f93293d
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 0000000000000000152fda2d1ad2ef80fe97a86fdc1dbab53fb2589808b0c50f
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 0000000000000000107dda6fe244d01b791f0da4bd2e8feb7fa5047e6ac81154
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 000000000000000005c9f1f00853fcd9a1626d5159497a87a7947fc1bd89b785
2015-03-05 11:19 (INFO) -- Networking.py:215 - Received new block. 0000000000000000060c240e504b92080b16b2cf25b68774be46c786d5b9e912
2015-03-05 11:19 (INFO) -- ArmoryQt.py:2517 - loadBlockchainIfNecessary
2015-03-05 11:19 (INFO) -- ArmoryQt.py:2538 - Setting netmode: 1
2015-03-05 11:19 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode then cpplog.txt: Log file opened at 1425522507: /home/user/.armory/armorycpplog.txt
-INFO - 1425522550: (BlockUtils.cpp:861) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 1425522550: (BlockUtils.cpp:862) lmdb dir: /home/user/.armory/databases
-INFO - 1425522550: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1425522550: (BlockUtils.cpp:1184) Executing: doInitialSyncOnLoad
-INFO - 1425522550: (BlockUtils.cpp:1255) Total number of blk*.dat files: 239
-INFO - 1425522550: (BlockUtils.cpp:1256) Total blockchain bytes: 32,022,003,769
-INFO - 1425522550: (BlockUtils.cpp:1597) Reading headers from db
-INFO - 1425522556: (BlockUtils.cpp:1623) Found 346228 headers in db
-DEBUG - 1425522556: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425522556: (BlockUtils.cpp:1285) --- Fetching SSH summaries for 573 registered addresses
-INFO - 1425522557: (BlockUtils.cpp:1298) Left off at file 238, offset 111262453
-INFO - 1425522557: (BlockUtils.cpp:1301) Reading headers and building chain...
-INFO - 1425522557: (BlockUtils.cpp:1302) Starting at block file 238 offset 111262453
-INFO - 1425522557: (BlockUtils.cpp:1304) Block height 346224
-DEBUG - 1425522557: (Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1425522557: (BlockUtils.cpp:1339) Looking for first unrecognized block
-INFO - 1425522557: (BlockUtils.cpp:1488) Loading block data... file 238 offset 111262453
-INFO - 1425522557: (BlockUtils.cpp:1356) Wrote blocks to DB in 0.000119s
-WARN - 1425522557: (BlockUtils.cpp:1074) Scanning from 346224 to 346224
-INFO - 1425522557: (BlockUtils.cpp:1450) Scanned Block range in 0.035501s
-INFO - 1425522557: (BlockUtils.cpp:1453) Finished loading at file 238, offset 111262453
-INFO - 1425522557: (BlockDataViewer.cpp:155) Enabling zero-conf tracking
Log file opened at 1425549702: /home/user/.armory/armorycpplog.txt
Log file opened at 1425551462: /home/user/.armory/armorycpplog.txt
-INFO - 1425551897: (BlockUtils.cpp:861) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 1425551897: (BlockUtils.cpp:862) lmdb dir: /home/user/.armory/databases
-INFO - 1425551897: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1425551897: (BlockUtils.cpp:1184) Executing: doInitialSyncOnLoad
-INFO - 1425551897: (BlockUtils.cpp:1255) Total number of blk*.dat files: 239
-INFO - 1425551897: (BlockUtils.cpp:1256) Total blockchain bytes: 32,038,780,985
-INFO - 1425551897: (BlockUtils.cpp:1597) Reading headers from db
-INFO - 1425551902: (BlockUtils.cpp:1623) Found 346228 headers in db
-DEBUG - 1425551902: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425551903: (BlockUtils.cpp:1285) --- Fetching SSH summaries for 573 registered addresses
-WARN - 1425551903: (BlockUtils.cpp:235) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-WARN - 1425551903: (BlockUtils.cpp:288) Inconsistent headers DB, attempting repairs
-INFO - 1425551903: (BlockUtils.cpp:1298) Left off at file 0, offset 0
-INFO - 1425551903: (BlockUtils.cpp:1301) Reading headers and building chain...
-INFO - 1425551903: (BlockUtils.cpp:1302) Starting at block file 0 offset 0
-INFO - 1425551903: (BlockUtils.cpp:1304) Block height 346224
-DEBUG - 1425551969: (Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1425551970: (BlockUtils.cpp:1339) Looking for first unrecognized block
-INFO - 1425551988: (BlockUtils.cpp:1488) Loading block data... file 238 offset 113818726
-ERROR - 1425551988: (BlockUtils.cpp:536) Next block header found at offset 113818734
-INFO - 1425551988: (BlockUtils.cpp:564) Reading raw blocks finished at file 238 offset 125944241
-INFO - 1425551988: (BlockUtils.cpp:1356) Wrote blocks to DB in 0.019708s
-ERROR - 1425551988: (BlockUtils.cpp:1402) Missing block data, attempting to repair the DB
-INFO - 1425551988: (BlockUtils.cpp:2111) BLKDATA DB was repaired successfully
-WARN - 1425551988: (BlockUtils.cpp:1074) Scanning from 346224 to 346261
-INFO - 1425551989: (BlockUtils.cpp:1450) Scanned Block range in 0.600169s
-INFO - 1425551989: (BlockUtils.cpp:1453) Finished loading at file 238, offset 125944241
-INFO - 1425551989: (BlockDataViewer.cpp:155) Enabling zero-conf tracking
Log file opened at 1425554119: /home/user/.armory/armorycpplog.txt
-INFO - 1425554376: (BlockUtils.cpp:861) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 1425554376: (BlockUtils.cpp:862) lmdb dir: /home/user/.armory/databases
-INFO - 1425554376: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1425554376: (BlockUtils.cpp:1184) Executing: doInitialSyncOnLoad
-INFO - 1425554376: (BlockUtils.cpp:1255) Total number of blk*.dat files: 239
-INFO - 1425554376: (BlockUtils.cpp:1256) Total blockchain bytes: 32,038,780,985
-INFO - 1425554376: (BlockUtils.cpp:1597) Reading headers from db
-INFO - 1425554377: (BlockUtils.cpp:1623) Found 346265 headers in db
-DEBUG - 1425554377: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425554378: (BlockUtils.cpp:1285) --- Fetching SSH summaries for 573 registered addresses
-ERROR - 1425554378: (BlockUtils.cpp:614) Next block header found at offset 124517947
-WARN - 1425554378: (BlockUtils.cpp:235) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-ERROR - 1425554378: (BlockUtils.cpp:614) Next block header found at offset 124517947
-ERROR - 1425554436: (BDM_mainthread.cpp:427) BDM thread failed: Failed to find last known top block hash inblk files. Blockchain is corrupt, time for a factory reset! All 3 attempts made in BDM mode. bitcoind seemed to choke on the first attempt, despite 30 minutes running time. Second attempt succeeded. 3rd attempt died, and it did so suggesting it hadn't committed the new block height somehow, as it was indicating the same number of catch up blocks as the 2nd attempt (which was also typical behaviour for 0.93.0)
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 05, 2015, 06:07:59 PM
All 3 attempts made in BDM mode. bitcoind seemed to choke on the first attempt, despite 30 minutes running time. Second attempt succeeded. 3rd attempt died, and it did so suggesting it hadn't committed the new block height somehow, as it was indicating the same number of catch up blocks as the 2nd attempt (which was also typical behaviour for 0.93.0)
I fixed the block catch up issue yesterday. You can pull bugfix if you want to try that. Ima push a change in a few hours to cover for this issue too. Maybe you want to wait till then to try out both changes.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 05, 2015, 06:25:12 PM
That went faster than expected. Try out bugfix, let's see if that covers your issue.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 05, 2015, 09:16:11 PM
Seems a pretty decent fix so far. "Remaining Blocks" count is a little erratic when used with 0.10.0, but I guess that's how parallel block downloading looks on a counter.
I don't know what happens on other platforms, but I get the "Disconnected!" tray balloon dialog as I shut down, which makes perfect sense as a warning at just about every other circumstance! I haven't been using BDM mode regularly for a while, but if that's just a routine part of using BDM, it can look like an error, even when you could argue it's behaving correctly. It's just the whole red cross on the screen thing. Maybe have shutdown as a case that uses a big green tick with "Clean disconnection", or just nothing.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 06, 2015, 12:13:51 AM
Seems a pretty decent fix so far. "Remaining Blocks" count is a little erratic when used with 0.10.0, but I guess that's how parallel block downloading looks on a counter.
Does it try to redownload 100~150 blocks if you shut it down and restart it right away? It may show 1-2 blocks on consecutive restarts but I think that has to do with some corner case handling of the RPC packets Core returns to Armory. Also keep an eye on your top block just to be safe. I haven't been using BDM mode regularly for a while
When you say BDM mode you mean auto bitcoind? That would be SDM mode (satoshi data manager). BDM is the block data manager, i.e. the C++ backend. I don't know what happens on other platforms, but I get the "Disconnected!" tray balloon dialog as I shut down
Ah, obviously. Since I don't shut down the P2P socket before asking bitcoind to stop it can end up thinking bitoind terminated unexpectedly. If only that would have triggered on my machine... T_T. I hate not experiencing the bugs first hand.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 06, 2015, 11:17:03 AM
Seems a pretty decent fix so far. "Remaining Blocks" count is a little erratic when used with 0.10.0, but I guess that's how parallel block downloading looks on a counter.
Does it try to redownload 100~150 blocks if you shut it down and restart it right away? It may show 1-2 blocks on consecutive restarts but I think that has to do with some corner case handling of the RPC packets Core returns to Armory. Also keep an eye on your top block just to be safe. No, that bug seems to be squashed. I once saw "2 blocks remaining" when re-starting straight after a shutdown, but it turned out 2 blocks had been found quickly just after/while I was shutting down. I've been checking against a separate source for the top block height (after all, Core 0.10 is even more optimistic in indicating it's synchonized than previously) I don't know what happens on other platforms, but I get the "Disconnected!" tray balloon dialog as I shut down
Ah, obviously. Since I don't shut down the P2P socket before asking bitcoind to stop it can end up thinking bitoind terminated unexpectedly. If only that would have triggered on my machine... T_T. I hate not experiencing the bugs first hand. As far as I recall, this behaviour always existed with SDM mode on Linux. Overall, SDM makes for a really responsive and solid experience with (pre) 0.93.1. I'm tempted to use SDM more often, the combined improvements of 0.93 and Core 0.10 has made it fluid and predictable to use, I think the shortcoming of both Core 0.9 and Armory 0.92 had me taking the reliability route (running Qt in Node mode before Armory so I can take action when it's stalled blockloading)
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 06, 2015, 12:28:03 PM
Another BDM rebuild error. armorylog.txt: ************************************************************
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1188 - Invoked: /usr/lib/armory-testing/ArmoryQt.py
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1189 - ************************************************************
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1190 - Loading Armory Engine:
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1191 - Armory Version : 0.93.0.70
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1192 - Armory Build: : None
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1193 - PyBtcWallet Version : 1.35
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1194 - Detected Operating system: Linux
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1195 - OS Variant : Fedora-20-Heisenbug
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1196 - User home-directory : /home/user
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1197 - Satoshi BTC directory : /home/user/.bitcoin
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1198 - Armory home dir : /home/user/.armory
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1199 - Detected System Specs :
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1200 - Total Available RAM : 0.43 GB
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1201 - CPU ID string :
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1202 - Number of CPU cores : 4 cores
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1203 - System is 64-bit : True
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1204 - Preferred Encoding : ANSI_X3.4-1968
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1205 - Machine Arch : x86_64
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1206 - Available HDD (ARM) : 124 GB
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1207 - Available HDD (BTC) : 124 GB
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1208 -
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1209 - Network Name: Main Network
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1210 - Satoshi Port: 8333
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1211 - Do wlt check: True
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1212 - Named options/arguments to armoryengine.py:
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - nettimeout : 2
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - rescan : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - ignoreAllZC : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - enableSupernode : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - disableModules : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - port : None
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - interport : 8223
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - skipStatsReport : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - forceWalletCheck: False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - rebuild : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - datadir : /home/user/.armory
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - clearMempool : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - offline : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - coverageOutputDir: None
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - armoryDBDir : DEFAULT
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - satoshiPort : DEFAULT
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - useTorSettings : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - netlog : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - keypool : 100
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - coverageInclude : None
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - forceOnline : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - skipAnnounceCheck: False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - redownload : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - multisigFile : DEFAULT
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - disableTorrent : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - testAnnounceCode: False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - mtdebug : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - logDisable : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - settingsPath : /home/user/.armory/ArmorySettings.txt
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - verbosity : None
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - doDebug : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - enableDetSign : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - testnet : False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - rpcport : DEFAULT
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - satoshiHome : /home/user/.bitcoin
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - satoshiRpcport : DEFAULT
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - logFile : /home/user/.armory/ArmoryQt.py.log.txt
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1214 - disableConfPermis: False
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1215 - Other arguments:
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1218 - ************************************************************
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:1613 - C++ block utilities loaded successfully
2015-03-06 11:45 (INFO) -- BDM.py:408 - Using the asynchronous/multi-threaded BlockDataManager.
2015-03-06 11:45 (INFO) -- BDM.py:409 - Blockchain operations will happen in the background.
2015-03-06 11:45 (INFO) -- BDM.py:410 - Devs: check TheBDM.getState() before asking for data.
2015-03-06 11:45 (INFO) -- BDM.py:411 - Registering addresses during rescans will queue them for
2015-03-06 11:45 (INFO) -- BDM.py:412 - inclusion after the current scan is completed.
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:3517 - Using settings file: /home/user/.armory/ArmorySettings.txt
2015-03-06 11:45 (INFO) -- announcefetch.py:95 - Reading files in fetcher directory:
2015-03-06 11:45 (INFO) -- announcefetch.py:104 - downloads : 6c50e8c8d8bf9800cf532d4b20bf49da7c13436189f6c1b02fa8b28b38829b83
2015-03-06 11:45 (INFO) -- announcefetch.py:104 - notify : eba491396ce1d9667177a6e298ae3485c1db35d10d84f89ec9cd882bac2faa9a
2015-03-06 11:45 (INFO) -- announcefetch.py:104 - announce : 6e4ddffcac6fd1ee8936361362f9a0ebb71b445b77fdfa35cfd50e9163ef164e
2015-03-06 11:45 (INFO) -- announcefetch.py:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-03-06 11:45 (INFO) -- announcefetch.py:104 - changelog : 21669c17b620503c05580053595dbedda1a9c2146b3fda89122e24444a45dc6b
2015-03-06 11:45 (INFO) -- announcefetch.py:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2728 - loadWalletsAndSettings
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2782 - Loading wallets...
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2841 - Number of wallets read in: 1
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2846 - Wallet (): "" (Encrypted)
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2855 - Loading Multisig Lockboxes
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2290 - Setting up networking...
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2319 - Internet status: 2
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2434 - startBitcoindIfNecessary
2015-03-06 11:45 (INFO) -- ArmoryQt.py:2483 - setSatoshiPaths
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['whereis', 'bitcoind']
2015-03-06 11:45 (INFO) -- SDM.py:453 - "whereis" returned: ['/usr/bin/bitcoind']
2015-03-06 11:45 (INFO) -- SDM.py:321 - Found bitcoind in the following places:
2015-03-06 11:45 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-06 11:45 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-06 11:45 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-06 11:45 (INFO) -- SDM.py:325 - Using: /usr/bin/bitcoind
2015-03-06 11:45 (INFO) -- SDM.py:496 - Reading bitcoin.conf file
2015-03-06 11:45 (INFO) -- SDM.py:536 - Setting permissions on bitcoin.conf
2015-03-06 11:45 (INFO) -- SDM.py:597 - Called startBitcoind
2015-03-06 11:45 (INFO) -- SDM.py:282 - Total size of files in /home/user/.bitcoin/blocks is 29.9 GB
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:598 - Executing popen: [u'/usr/bin/bitcoind', '-datadir=/home/user/.bitcoin']
2015-03-06 11:45 (INFO) -- SDM.py:669 - PID of bitcoind: 1331
2015-03-06 11:45 (INFO) -- SDM.py:670 - PID of armory: 1322
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['python', '/usr/lib/armory-testing/guardian.py', '1322', '1331']
2015-03-06 11:45 (INFO) -- SDM.py:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2015-03-06 11:45 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:598 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:598 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2015-03-06 11:45 (INFO) -- ArmoryUtils.py:598 - Executing popen: find /home/user -type f -name "mimeTypes.rdf"
2015-03-06 11:45 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2015-03-06 11:45 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-03-06 11:45 (INFO) -- ArmoryQt.py:1810 - From: Expert
2015-03-06 11:45 (INFO) -- ArmoryQt.py:1818 - To: Expert
2015-03-06 11:45 (INFO) -- ArmoryQt.py:5876 - Dashboard switched to auto-BadConnection
2015-03-06 11:45 (INFO) -- Networking.py:65 - Connection initiated. Start handshake
2015-03-06 11:45 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2015-03-06 11:46 (INFO) -- Networking.py:156 - Received version message from peer:
2015-03-06 11:46 (INFO) -- Networking.py:157 - Version: 70002
2015-03-06 11:46 (INFO) -- Networking.py:158 - SubVersion: /Satoshi:0.10.0/
2015-03-06 11:46 (INFO) -- Networking.py:159 - TimeStamp: 1425642360
2015-03-06 11:46 (INFO) -- Networking.py:160 - StartHeight: 346392
2015-03-06 11:46 (INFO) -- Networking.py:356 - Handshake finished, connection open!
2015-03-06 11:46 (INFO) -- ArmoryQt.py:2517 - loadBlockchainIfNecessary
2015-03-06 11:46 (INFO) -- ArmoryQt.py:2538 - Setting netmode: 1
2015-03-06 11:46 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2015-03-06 11:46 (INFO) -- ArmoryQt.py:3140 - Current block number: 346393
2015-03-06 11:46 (INFO) -- Networking.py:215 - Received new block. 00000000000000001704f6b8cb65238df1fcda4a6ec34c3967879b013b5c5478
2015-03-06 11:46 (INFO) -- ArmoryQt.py:6238 - New Block! : 346394
2015-03-06 11:46 (INFO) -- ArmoryQt.py:6246 - Current block number: 346394
2015-03-06 11:46 (INFO) -- Networking.py:215 - Received new block. 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
2015-03-06 11:46 (INFO) -- Networking.py:215 - Received new block. 0000000000000000148af21b20abc03d84d9a9e038dcd4d007d1cd680c0d9e77
2015-03-06 11:46 (INFO) -- Networking.py:215 - Received new block. 000000000000000008ee6cd1e2e15480088c3e2bda47a68a8d0dcf79dcd598af
2015-03-06 11:46 (INFO) -- Networking.py:215 - Received new block. 000000000000000015c7b2196f5f03fe717171e7748dc60ba823df3ec01d5079
2015-03-06 11:46 (INFO) -- Networking.py:215 - Received new block. 000000000000000003880a75ca8a9730335720c7c121d4fa863f2bae4efedacb
2015-03-06 11:47 (INFO) -- Networking.py:215 - Received new block. 000000000000000006e679325e79ee3b0a1d25f97c745d7c410267f9440ee8c2
2015-03-06 11:47 (INFO) -- Networking.py:215 - Received new block. 00000000000000000f5e4b7b3be52edb6a00c0a616b191f8590a074e317a177f
2015-03-06 11:47 (INFO) -- Networking.py:215 - Received new block. 0000000000000000056125252a197214ee29803926ff92a8e2bde7517da80855
2015-03-06 11:47 (INFO) -- ArmoryQt.py:6238 - New Block! : 346416
2015-03-06 11:47 (INFO) -- ArmoryQt.py:6246 - Current block number: 346416 armorycpplog.txt: Log file opened at 1425642329: /home/user/.armory/armorycpplog.txt
-INFO - 1425642371: (BlockUtils.cpp:866) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 1425642371: (BlockUtils.cpp:867) lmdb dir: /home/user/.armory/databases
-INFO - 1425642371: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1425642371: (BlockUtils.cpp:1187) Executing: doInitialSyncOnLoad
-INFO - 1425642371: (BlockUtils.cpp:1258) Total number of blk*.dat files: 240
-INFO - 1425642371: (BlockUtils.cpp:1259) Total blockchain bytes: 32,105,573,837
-INFO - 1425642371: (BlockUtils.cpp:1600) Reading headers from db
-INFO - 1425642377: (BlockUtils.cpp:1626) Found 346396 headers in db
-DEBUG - 1425642377: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425642378: (BlockUtils.cpp:1288) --- Fetching SSH summaries for 573 registered addresses
-INFO - 1425642378: (BlockUtils.cpp:1301) Left off at file 239, offset 54045043
-INFO - 1425642378: (BlockUtils.cpp:1304) Reading headers and building chain...
-INFO - 1425642378: (BlockUtils.cpp:1305) Starting at block file 239 offset 54045043
-INFO - 1425642378: (BlockUtils.cpp:1307) Block height 346392
-DEBUG - 1425642378: (Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1425642379: (BlockUtils.cpp:1342) Looking for first unrecognized block
-INFO - 1425642379: (BlockUtils.cpp:1491) Loading block data... file 239 offset 54045035
-ERROR - 1425642379: (BlockUtils.cpp:541) Next block header found at offset 54045043
-INFO - 1425642379: (BlockUtils.cpp:569) Reading raw blocks finished at file 239 offset 55144191
-INFO - 1425642379: (BlockUtils.cpp:1359) Wrote blocks to DB in 0.003159s
-WARN - 1425642379: (BlockUtils.cpp:1077) Scanning from 346392 to 346393
-INFO - 1425642379: (BlockUtils.cpp:1453) Scanned Block range in 0.078573s
-INFO - 1425642379: (BlockUtils.cpp:1456) Finished loading at file 239, offset 55144191
-INFO - 1425642379: (BlockDataViewer.cpp:155) Enabling zero-conf tracking
-DEBUG - 1425642381: (Blockchain.cpp:211) Organizing chain
-INFO - 1425642381: (BlockUtils.cpp:1491) Loading block data... file 239 offset 55144191
-INFO - 1425642381: (BlockUtils.cpp:569) Reading raw blocks finished at file 239 offset 55537691
-WARN - 1425642381: (BlockUtils.cpp:1077) Scanning from 346394 to 346394
-DEBUG - 1425642384: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642384: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642385: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642385: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-DEBUG - 1425642385: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642385: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642386: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642386: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-DEBUG - 1425642386: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642386: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642387: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642387: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642387: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642387: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-DEBUG - 1425642387: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642387: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642388: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642388: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642388: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642388: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642388: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642388: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-DEBUG - 1425642388: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642388: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642389: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642389: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642389: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642389: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642389: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642389: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-DEBUG - 1425642389: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642389: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642390: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642390: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642390: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642390: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642390: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642390: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-DEBUG - 1425642391: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642391: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642392: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642392: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642392: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642392: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642392: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642392: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-DEBUG - 1425642392: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642392: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642393: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642393: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642393: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642393: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642393: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642393: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-DEBUG - 1425642393: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642393: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642394: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642394: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642394: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642394: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642394: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642394: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-DEBUG - 1425642394: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642394: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642395: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642395: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642395: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642395: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642395: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642395: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642395: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642395: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642395: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642395: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-DEBUG - 1425642395: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642395: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642396: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642396: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642396: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642396: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642396: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642396: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642396: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642396: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642396: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642396: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-WARN - 1425642396: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642396: (Blockchain.cpp:48) Header Hash: 0000000000000000005bca044d866fccd5f165629a843f4319bb956f08199a5d
-DEBUG - 1425642396: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642396: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642397: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642397: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642397: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642397: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642397: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642397: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642397: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642397: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642397: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642397: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-WARN - 1425642397: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642397: (Blockchain.cpp:48) Header Hash: 0000000000000000005bca044d866fccd5f165629a843f4319bb956f08199a5d
-DEBUG - 1425642397: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642398: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642399: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642399: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642399: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642399: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642399: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642399: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642399: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642399: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642399: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642399: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-WARN - 1425642399: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642399: (Blockchain.cpp:48) Header Hash: 0000000000000000005bca044d866fccd5f165629a843f4319bb956f08199a5d
-WARN - 1425642399: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642399: (Blockchain.cpp:48) Header Hash: 0000000000000000148af21b20abc03d84d9a9e038dcd4d007d1cd680c0d9e77
-DEBUG - 1425642399: (Blockchain.cpp:211) Organizing chain
##
## LOTS OF ITERATIONS OF SIMILAR PATTERN.....
##
-DEBUG - 1425642433: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642433: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 0000000000000000005bca044d866fccd5f165629a843f4319bb956f08199a5d
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 0000000000000000148af21b20abc03d84d9a9e038dcd4d007d1cd680c0d9e77
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 00000000000000000dac54f86b70f14f2e5492d07c177c12da7d53f2109673ab
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 00000000000000000b2acdc668eb996cd2ffd58f4a6de94841f7e17049d2fb44
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 00000000000000000a3d93c411c7b825dcf0883808f5cde0871fd92eac8617a3
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 000000000000000008ee6cd1e2e15480088c3e2bda47a68a8d0dcf79dcd598af
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 000000000000000015c7b2196f5f03fe717171e7748dc60ba823df3ec01d5079
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 000000000000000003880a75ca8a9730335720c7c121d4fa863f2bae4efedacb
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 0000000000000000128ac6d567b10d3949a7e13cf44a9c29e0f3af7534187a1e
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 000000000000000006e679325e79ee3b0a1d25f97c745d7c410267f9440ee8c2
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 000000000000000007e131711c20635275f181fb2a9934e9eefd616661f187d3
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 00000000000000000f5e4b7b3be52edb6a00c0a616b191f8590a074e317a177f
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 0000000000000000056125252a197214ee29803926ff92a8e2bde7517da80855
-WARN - 1425642434: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642434: (Blockchain.cpp:48) Header Hash: 0000000000000000146728ed266799bdbfdcc5364d3fe3bc101c89ed4a4577bf
-DEBUG - 1425642434: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642434: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 0000000000000000005bca044d866fccd5f165629a843f4319bb956f08199a5d
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 0000000000000000148af21b20abc03d84d9a9e038dcd4d007d1cd680c0d9e77
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 00000000000000000dac54f86b70f14f2e5492d07c177c12da7d53f2109673ab
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 00000000000000000b2acdc668eb996cd2ffd58f4a6de94841f7e17049d2fb44
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 00000000000000000a3d93c411c7b825dcf0883808f5cde0871fd92eac8617a3
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 000000000000000008ee6cd1e2e15480088c3e2bda47a68a8d0dcf79dcd598af
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 000000000000000015c7b2196f5f03fe717171e7748dc60ba823df3ec01d5079
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 000000000000000003880a75ca8a9730335720c7c121d4fa863f2bae4efedacb
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 0000000000000000128ac6d567b10d3949a7e13cf44a9c29e0f3af7534187a1e
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 000000000000000006e679325e79ee3b0a1d25f97c745d7c410267f9440ee8c2
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 000000000000000007e131711c20635275f181fb2a9934e9eefd616661f187d3
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 00000000000000000f5e4b7b3be52edb6a00c0a616b191f8590a074e317a177f
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 0000000000000000056125252a197214ee29803926ff92a8e2bde7517da80855
-WARN - 1425642435: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642435: (Blockchain.cpp:48) Header Hash: 0000000000000000146728ed266799bdbfdcc5364d3fe3bc101c89ed4a4577bf
-DEBUG - 1425642436: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642436: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 0000000000000000005bca044d866fccd5f165629a843f4319bb956f08199a5d
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 0000000000000000148af21b20abc03d84d9a9e038dcd4d007d1cd680c0d9e77
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 00000000000000000dac54f86b70f14f2e5492d07c177c12da7d53f2109673ab
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 00000000000000000b2acdc668eb996cd2ffd58f4a6de94841f7e17049d2fb44
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 00000000000000000a3d93c411c7b825dcf0883808f5cde0871fd92eac8617a3
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 000000000000000008ee6cd1e2e15480088c3e2bda47a68a8d0dcf79dcd598af
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 000000000000000015c7b2196f5f03fe717171e7748dc60ba823df3ec01d5079
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 000000000000000003880a75ca8a9730335720c7c121d4fa863f2bae4efedacb
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 0000000000000000128ac6d567b10d3949a7e13cf44a9c29e0f3af7534187a1e
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 000000000000000006e679325e79ee3b0a1d25f97c745d7c410267f9440ee8c2
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 000000000000000007e131711c20635275f181fb2a9934e9eefd616661f187d3
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 00000000000000000f5e4b7b3be52edb6a00c0a616b191f8590a074e317a177f
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 0000000000000000056125252a197214ee29803926ff92a8e2bde7517da80855
-WARN - 1425642437: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642437: (Blockchain.cpp:48) Header Hash: 0000000000000000146728ed266799bdbfdcc5364d3fe3bc101c89ed4a4577bf
-DEBUG - 1425642437: (Blockchain.cpp:211) Organizing chain
-WARN - 1425642437: (BlockUtils.cpp:1543) Found an orphan block in the blockchain. If this message persists, please report it.
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000bfd3b43ca8e853eeb55989e2f137f8664f7f3f846892f7d
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 0000000000000000058939f70f808050c802f2d7b50a81bb2ab0c280ff526aa6
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 0000000000000000125a6766bdc03bc2b633516714ff59099c91c2b2c9712381
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000b59a0fd8d250295b861024e2a566a31e6adb6e7aa6755bd
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000a5c37772b09e625acf8291ba099671de5730b1ec1d9e8f3
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 0000000000000000005bca044d866fccd5f165629a843f4319bb956f08199a5d
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 0000000000000000148af21b20abc03d84d9a9e038dcd4d007d1cd680c0d9e77
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000dac54f86b70f14f2e5492d07c177c12da7d53f2109673ab
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000b2acdc668eb996cd2ffd58f4a6de94841f7e17049d2fb44
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000a3d93c411c7b825dcf0883808f5cde0871fd92eac8617a3
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 000000000000000008ee6cd1e2e15480088c3e2bda47a68a8d0dcf79dcd598af
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 000000000000000015c7b2196f5f03fe717171e7748dc60ba823df3ec01d5079
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 000000000000000003880a75ca8a9730335720c7c121d4fa863f2bae4efedacb
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 0000000000000000128ac6d567b10d3949a7e13cf44a9c29e0f3af7534187a1e
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 000000000000000006e679325e79ee3b0a1d25f97c745d7c410267f9440ee8c2
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 000000000000000007e131711c20635275f181fb2a9934e9eefd616661f187d3
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000f5e4b7b3be52edb6a00c0a616b191f8590a074e317a177f
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 0000000000000000056125252a197214ee29803926ff92a8e2bde7517da80855
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 0000000000000000146728ed266799bdbfdcc5364d3fe3bc101c89ed4a4577bf
-WARN - 1425642438: (Blockchain.cpp:47) Somehow tried to add header that's already in map
-WARN - 1425642438: (Blockchain.cpp:48) Header Hash: 00000000000000000f8b39db8b02020a67efdc8a6450cc64368fd03936e9209b
-DEBUG - 1425642438: (Blockchain.cpp:211) Organizing chain
-INFO - 1425642438: (BlockUtils.cpp:1491) Loading block data... file 239 offset 55537691
-INFO - 1425642438: (BlockUtils.cpp:569) Reading raw blocks finished at file 239 offset 60866477
-WARN - 1425642438: (BlockUtils.cpp:1077) Scanning from 346408 to 346416
-ERROR - 1425642438: (lmdb_wrapper.cpp:1519) Block height exceeds DupID lookup table
-ERROR - 1425642438: (BlockWriteBatcher.cpp:938) No block in DB at height 346409
-ERROR - 1425642438: (BDM_mainthread.cpp:427) BDM thread failed: The scanning process interrupted unexpectedly, Armory will now shutdown. You will have to proceed to "Help -> Rebuild and Rescan" on the next start. If the error persists, contact support. Refer to your log file for more details on the error. This all corresponds to one test run. bitcoind was still running after I Ok'ed the BDM error dialog (prompting Armory to quit).
Title: Re: Users experiencing the BDM error message
Post by: doug_armory on March 06, 2015, 02:35:16 PM
I don't know what happens on other platforms, but I get the "Disconnected!" tray balloon dialog as I shut down
Ah, obviously. Since I don't shut down the P2P socket before asking bitcoind to stop it can end up thinking bitoind terminated unexpectedly. If only that would have triggered on my machine... T_T. I hate not experiencing the bugs first hand. As far as I recall, this behaviour always existed with SDM mode on Linux. I get it all the time in OS X too, although I'm obviously running Bitcoin-Qt manually.
Title: Re: Users experiencing the BDM error message
Post by: zveda2000 on March 06, 2015, 04:00:22 PM
Sometimes when starting up Armory, it will get stuck showing the number of blocks that are left to download. After waiting 20 minutes or so like that, I have to restart Armory for it to actually start downloading. I guess this is some problem with running bitcoind. I have armory 0.93.0.70 and bitcoin 0.10.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 06, 2015, 04:23:19 PM
Another BDM rebuild error.
That one is hitting the block update code. These have unit tests dedicated for headers first behavior, but I guess you just found a corner case. Time to reinforce them. Did restarting fix the DB?
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 06, 2015, 04:41:10 PM
Another BDM rebuild error.
That one is hitting the block update code. These have unit tests dedicated for headers first behavior, but I guess you just found a corner case. Time to reinforce them. Did restarting fix the DB? Seems the Db didn't need rebuilding, I restarted later on with the same Db used for that run, and Armory politely caught up the missing blocks without complaining.
Title: Re: Users experiencing the BDM error message
Post by: matrix01 on March 09, 2015, 04:41:48 AM
JUst to confirm. Once this BDM error is fixed will it be announced in this thread or on some other thread. I just want to make sure I'm checking up on the correct thread. Lastly, will the 93.1 Armory release become available tomorrow?
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 09, 2015, 10:59:56 AM
I'm also managing to provoke "BDM thread failed: std::exception" errors, too. Logs available if anyone wants them.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 09, 2015, 03:11:52 PM
I'm also managing to provoke "BDM thread failed: std::exception" errors, too. Logs available if anyone wants them.
Let's see logs, also try the latest commit in bugfix.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 09, 2015, 04:23:54 PM
"BDM thread failed: std::exception" error logs: armorylog.txt ************************************************************
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1188 - Invoked: /usr/lib/armory-testing/ArmoryQt.py
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1189 - ************************************************************
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1190 - Loading Armory Engine:
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1191 - Armory Version : 0.93.0.70
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1192 - Armory Build: : None
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1193 - PyBtcWallet Version : 1.35
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1194 - Detected Operating system: Linux
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1195 - OS Variant : Fedora-20-Heisenbug
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1196 - User home-directory : /home/user
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1197 - Satoshi BTC directory : /home/user/.bitcoin
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1198 - Armory home dir : /home/user/.armory
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1199 - Detected System Specs :
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1200 - Total Available RAM : 0.82 GB
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1201 - CPU ID string :
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1202 - Number of CPU cores : 4 cores
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1203 - System is 64-bit : True
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1204 - Preferred Encoding : ANSI_X3.4-1968
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1205 - Machine Arch : x86_64
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1206 - Available HDD (ARM) : 123 GB
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1207 - Available HDD (BTC) : 123 GB
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1208 -
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1209 - Network Name: Main Network
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1210 - Satoshi Port: 8333
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1211 - Do wlt check: True
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1212 - Named options/arguments to armoryengine.py:
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - nettimeout : 2
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - rescan : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - ignoreAllZC : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - enableSupernode : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - disableModules : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - port : None
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - interport : 8223
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - skipStatsReport : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - forceWalletCheck: False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - rebuild : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - datadir : /home/user/.armory
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - clearMempool : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - offline : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - coverageOutputDir: None
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - armoryDBDir : DEFAULT
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - satoshiPort : DEFAULT
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - useTorSettings : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - netlog : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - keypool : 100
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - coverageInclude : None
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - forceOnline : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - skipAnnounceCheck: False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - redownload : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - multisigFile : DEFAULT
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - disableTorrent : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - testAnnounceCode: False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - mtdebug : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - logDisable : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - settingsPath : /home/user/.armory/ArmorySettings.txt
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - verbosity : None
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - doDebug : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - enableDetSign : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - testnet : False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - rpcport : DEFAULT
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - satoshiHome : /home/user/.bitcoin
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - satoshiRpcport : DEFAULT
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - logFile : /home/user/.armory/ArmoryQt.py.log.txt
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1214 - disableConfPermis: False
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1215 - Other arguments:
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1218 - ************************************************************
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:1613 - C++ block utilities loaded successfully
2015-03-09 10:35 (INFO) -- BDM.py:408 - Using the asynchronous/multi-threaded BlockDataManager.
2015-03-09 10:35 (INFO) -- BDM.py:409 - Blockchain operations will happen in the background.
2015-03-09 10:35 (INFO) -- BDM.py:410 - Devs: check TheBDM.getState() before asking for data.
2015-03-09 10:35 (INFO) -- BDM.py:411 - Registering addresses during rescans will queue them for
2015-03-09 10:35 (INFO) -- BDM.py:412 - inclusion after the current scan is completed.
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:3517 - Using settings file: /home/user/.armory/ArmorySettings.txt
2015-03-09 10:35 (INFO) -- announcefetch.py:95 - Reading files in fetcher directory:
2015-03-09 10:35 (INFO) -- announcefetch.py:104 - downloads : 6c50e8c8d8bf9800cf532d4b20bf49da7c13436189f6c1b02fa8b28b38829b83
2015-03-09 10:35 (INFO) -- announcefetch.py:104 - notify : eba491396ce1d9667177a6e298ae3485c1db35d10d84f89ec9cd882bac2faa9a
2015-03-09 10:35 (INFO) -- announcefetch.py:104 - announce : 6e4ddffcac6fd1ee8936361362f9a0ebb71b445b77fdfa35cfd50e9163ef164e
2015-03-09 10:35 (INFO) -- announcefetch.py:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-03-09 10:35 (INFO) -- announcefetch.py:104 - changelog : 21669c17b620503c05580053595dbedda1a9c2146b3fda89122e24444a45dc6b
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2728 - loadWalletsAndSettings
2015-03-09 10:35 (INFO) -- announcefetch.py:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2782 - Loading wallets...
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2841 - Number of wallets read in: 1
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2846 - Wallet (): "" (Encrypted)
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2855 - Loading Multisig Lockboxes
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2290 - Setting up networking...
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2319 - Internet status: 2
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2434 - startBitcoindIfNecessary
2015-03-09 10:35 (INFO) -- ArmoryQt.py:2483 - setSatoshiPaths
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['whereis', 'bitcoind']
2015-03-09 10:35 (INFO) -- SDM.py:453 - "whereis" returned: ['/usr/bin/bitcoind']
2015-03-09 10:35 (INFO) -- SDM.py:321 - Found bitcoind in the following places:
2015-03-09 10:35 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-09 10:35 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-09 10:35 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-09 10:35 (INFO) -- SDM.py:325 - Using: /usr/bin/bitcoind
2015-03-09 10:35 (INFO) -- SDM.py:496 - Reading bitcoin.conf file
2015-03-09 10:35 (INFO) -- SDM.py:536 - Setting permissions on bitcoin.conf
2015-03-09 10:35 (INFO) -- SDM.py:597 - Called startBitcoind
2015-03-09 10:35 (INFO) -- SDM.py:282 - Total size of files in /home/user/.bitcoin/blocks is 30.1 GB
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:598 - Executing popen: [u'/usr/bin/bitcoind', '-datadir=/home/user/.bitcoin']
2015-03-09 10:35 (INFO) -- SDM.py:669 - PID of bitcoind: 4165
2015-03-09 10:35 (INFO) -- SDM.py:670 - PID of armory: 4156
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['python', '/usr/lib/armory-testing/guardian.py', '4156', '4165']
2015-03-09 10:35 (INFO) -- SDM.py:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2015-03-09 10:35 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:598 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:598 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2015-03-09 10:35 (INFO) -- ArmoryUtils.py:598 - Executing popen: find /home/user -type f -name "mimeTypes.rdf"
2015-03-09 10:35 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2015-03-09 10:35 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-03-09 10:35 (INFO) -- ArmoryQt.py:1810 - From: Expert
2015-03-09 10:35 (INFO) -- ArmoryQt.py:1818 - To: Expert
2015-03-09 10:35 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2015-03-09 10:36 (INFO) -- Networking.py:65 - Connection initiated. Start handshake
2015-03-09 10:36 (INFO) -- Networking.py:156 - Received version message from peer:
2015-03-09 10:36 (INFO) -- Networking.py:157 - Version: 70002
2015-03-09 10:36 (INFO) -- Networking.py:158 - SubVersion: /Satoshi:0.10.0/
2015-03-09 10:36 (INFO) -- Networking.py:159 - TimeStamp: 1425897380
2015-03-09 10:36 (INFO) -- Networking.py:160 - StartHeight: 346850
2015-03-09 10:36 (INFO) -- Networking.py:356 - Handshake finished, connection open!
2015-03-09 10:36 (INFO) -- ArmoryQt.py:2517 - loadBlockchainIfNecessary
2015-03-09 10:36 (INFO) -- ArmoryQt.py:2538 - Setting netmode: 1
2015-03-09 10:36 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2015-03-09 10:36 (INFO) -- ArmoryQt.py:3140 - Current block number: 346850
2015-03-09 10:45 (INFO) -- ArmoryQt.py:6238 - New Block! : 346851
2015-03-09 10:45 (INFO) -- ArmoryQt.py:6246 - Current block number: 346851
2015-03-09 10:51 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2015-03-09 10:51 (INFO) -- SDM.py:683 - Called stopBitcoind
2015-03-09 10:51 (ERROR) -- Networking.py:365 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2015-03-09 10:51 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window!
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1074 - C++ block utilities loaded successfully
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: free -m
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['cat', '/proc/cpuinfo']
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1184 -
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1185 -
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1186 -
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1187 - ************************************************************
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1188 - Invoked: /usr/lib/armory-testing/ArmoryQt.py
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1189 - ************************************************************
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1190 - Loading Armory Engine:
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1191 - Armory Version : 0.93.0.70
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1192 - Armory Build: : None
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1193 - PyBtcWallet Version : 1.35
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1194 - Detected Operating system: Linux
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1195 - OS Variant : Fedora-20-Heisenbug
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1196 - User home-directory : /home/user
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1197 - Satoshi BTC directory : /home/user/.bitcoin
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1198 - Armory home dir : /home/user/.armory
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1199 - Detected System Specs :
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1200 - Total Available RAM : 0.85 GB
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1201 - CPU ID string :
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1202 - Number of CPU cores : 4 cores
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1203 - System is 64-bit : True
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1204 - Preferred Encoding : ANSI_X3.4-1968
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1205 - Machine Arch : x86_64
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1206 - Available HDD (ARM) : 124 GB
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1207 - Available HDD (BTC) : 124 GB
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1208 -
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1209 - Network Name: Main Network
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1210 - Satoshi Port: 8333
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1211 - Do wlt check: True
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1212 - Named options/arguments to armoryengine.py:
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - nettimeout : 2
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - rescan : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - ignoreAllZC : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - enableSupernode : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - disableModules : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - port : None
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - interport : 8223
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - skipStatsReport : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - forceWalletCheck: False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - rebuild : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - datadir : /home/user/.armory
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - clearMempool : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - offline : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - coverageOutputDir: None
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - armoryDBDir : DEFAULT
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - satoshiPort : DEFAULT
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - useTorSettings : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - netlog : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - keypool : 100
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - coverageInclude : None
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - forceOnline : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - skipAnnounceCheck: False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - redownload : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - multisigFile : DEFAULT
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - disableTorrent : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - testAnnounceCode: False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - mtdebug : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - logDisable : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - settingsPath : /home/user/.armory/ArmorySettings.txt
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - verbosity : None
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - doDebug : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - enableDetSign : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - testnet : False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - rpcport : DEFAULT
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - satoshiHome : /home/user/.bitcoin
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - satoshiRpcport : DEFAULT
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - logFile : /home/user/.armory/ArmoryQt.py.log.txt
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1214 - disableConfPermis: False
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1215 - Other arguments:
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1218 - ************************************************************
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:1613 - C++ block utilities loaded successfully
2015-03-09 10:51 (INFO) -- BDM.py:408 - Using the asynchronous/multi-threaded BlockDataManager.
2015-03-09 10:51 (INFO) -- BDM.py:409 - Blockchain operations will happen in the background.
2015-03-09 10:51 (INFO) -- BDM.py:410 - Devs: check TheBDM.getState() before asking for data.
2015-03-09 10:51 (INFO) -- BDM.py:411 - Registering addresses during rescans will queue them for
2015-03-09 10:51 (INFO) -- BDM.py:412 - inclusion after the current scan is completed.
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:3517 - Using settings file: /home/user/.armory/ArmorySettings.txt
2015-03-09 10:51 (INFO) -- announcefetch.py:95 - Reading files in fetcher directory:
2015-03-09 10:51 (INFO) -- announcefetch.py:104 - downloads : 6c50e8c8d8bf9800cf532d4b20bf49da7c13436189f6c1b02fa8b28b38829b83
2015-03-09 10:51 (INFO) -- announcefetch.py:104 - notify : eba491396ce1d9667177a6e298ae3485c1db35d10d84f89ec9cd882bac2faa9a
2015-03-09 10:51 (INFO) -- announcefetch.py:104 - announce : 6e4ddffcac6fd1ee8936361362f9a0ebb71b445b77fdfa35cfd50e9163ef164e
2015-03-09 10:51 (INFO) -- announcefetch.py:104 - bootstrap : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2015-03-09 10:51 (INFO) -- announcefetch.py:104 - changelog : 21669c17b620503c05580053595dbedda1a9c2146b3fda89122e24444a45dc6b
2015-03-09 10:51 (INFO) -- announcefetch.py:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2728 - loadWalletsAndSettings
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2782 - Loading wallets...
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2841 - Number of wallets read in: 1
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2846 - Wallet (): "" (Encrypted)
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2855 - Loading Multisig Lockboxes
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2290 - Setting up networking...
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2319 - Internet status: 2
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2434 - startBitcoindIfNecessary
2015-03-09 10:51 (INFO) -- ArmoryQt.py:2483 - setSatoshiPaths
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['whereis', 'bitcoind']
2015-03-09 10:51 (INFO) -- SDM.py:453 - "whereis" returned: ['/usr/bin/bitcoind']
2015-03-09 10:51 (INFO) -- SDM.py:321 - Found bitcoind in the following places:
2015-03-09 10:51 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-09 10:51 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-09 10:51 (INFO) -- SDM.py:323 - /usr/bin/bitcoind
2015-03-09 10:51 (INFO) -- SDM.py:325 - Using: /usr/bin/bitcoind
2015-03-09 10:51 (INFO) -- SDM.py:496 - Reading bitcoin.conf file
2015-03-09 10:51 (INFO) -- SDM.py:536 - Setting permissions on bitcoin.conf
2015-03-09 10:51 (INFO) -- SDM.py:597 - Called startBitcoind
2015-03-09 10:51 (INFO) -- SDM.py:282 - Total size of files in /home/user/.bitcoin/blocks is 30.1 GB
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: [u'/usr/bin/bitcoind', '-datadir=/home/user/.bitcoin']
2015-03-09 10:51 (INFO) -- SDM.py:669 - PID of bitcoind: 5776
2015-03-09 10:51 (INFO) -- SDM.py:670 - PID of armory: 5767
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: ['python', '/usr/lib/armory-testing/guardian.py', '5767', '5776']
2015-03-09 10:51 (INFO) -- SDM.py:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2015-03-09 10:51 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2015-03-09 10:51 (INFO) -- ArmoryUtils.py:598 - Executing popen: find /home/user -type f -name "mimeTypes.rdf"
2015-03-09 10:51 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2015-03-09 10:51 (INFO) -- ArmoryQt.py:1809 - Changing usermode:
2015-03-09 10:51 (INFO) -- ArmoryQt.py:1810 - From: Expert
2015-03-09 10:51 (INFO) -- ArmoryQt.py:1818 - To: Expert
2015-03-09 10:51 (INFO) -- ArmoryQt.py:5876 - Dashboard switched to auto-BadConnection
2015-03-09 10:52 (INFO) -- Networking.py:65 - Connection initiated. Start handshake
2015-03-09 10:52 (INFO) -- ArmoryQt.py:5887 - Dashboard switched to auto-InitSync
2015-03-09 10:52 (INFO) -- Networking.py:156 - Received version message from peer:
2015-03-09 10:52 (INFO) -- Networking.py:157 - Version: 70002
2015-03-09 10:52 (INFO) -- Networking.py:158 - SubVersion: /Satoshi:0.10.0/
2015-03-09 10:52 (INFO) -- Networking.py:159 - TimeStamp: 1425898363
2015-03-09 10:52 (INFO) -- Networking.py:160 - StartHeight: 346851
2015-03-09 10:52 (INFO) -- Networking.py:356 - Handshake finished, connection open!
2015-03-09 10:52 (INFO) -- ArmoryQt.py:2517 - loadBlockchainIfNecessary
2015-03-09 10:52 (INFO) -- ArmoryQt.py:2538 - Setting netmode: 1
2015-03-09 10:52 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode armorycpplog.txt Log file opened at 1425897343: /home/user/.armory/armorycpplog.txt
-INFO - 1425897390: (BlockUtils.cpp:866) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 1425897390: (BlockUtils.cpp:867) lmdb dir: /home/user/.armory/databases
-INFO - 1425897390: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1425897390: (BlockUtils.cpp:1187) Executing: doInitialSyncOnLoad
-INFO - 1425897390: (BlockUtils.cpp:1258) Total number of blk*.dat files: 241
-INFO - 1425897390: (BlockUtils.cpp:1259) Total blockchain bytes: 32,272,964,249
-INFO - 1425897390: (BlockUtils.cpp:1600) Reading headers from db
-INFO - 1425897395: (BlockUtils.cpp:1626) Found 346855 headers in db
-DEBUG - 1425897395: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425897396: (BlockUtils.cpp:1288) --- Fetching SSH summaries for 573 registered addresses
-INFO - 1425897396: (BlockUtils.cpp:1301) Left off at file 240, offset 90369067
-INFO - 1425897396: (BlockUtils.cpp:1304) Reading headers and building chain...
-INFO - 1425897396: (BlockUtils.cpp:1305) Starting at block file 240 offset 90369067
-INFO - 1425897396: (BlockUtils.cpp:1307) Block height 346850
-DEBUG - 1425897396: (Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1425897397: (BlockUtils.cpp:1342) Looking for first unrecognized block
-INFO - 1425897397: (BlockUtils.cpp:1491) Loading block data... file 240 offset 90369067
-INFO - 1425897397: (BlockUtils.cpp:1359) Wrote blocks to DB in 6.3e-05s
-WARN - 1425897397: (BlockUtils.cpp:1077) Scanning from 346850 to 346850
-INFO - 1425897397: (BlockUtils.cpp:1453) Scanned Block range in 0.039933s
-INFO - 1425897397: (BlockUtils.cpp:1456) Finished loading at file 240, offset 90369067
-INFO - 1425897397: (BlockDataViewer.cpp:155) Enabling zero-conf tracking
-DEBUG - 1425897944: (Blockchain.cpp:211) Organizing chain
-INFO - 1425897944: (BlockUtils.cpp:1491) Loading block data... file 240 offset 90369067
-INFO - 1425897944: (BlockUtils.cpp:569) Reading raw blocks finished at file 240 offset 91118264
-WARN - 1425897944: (BlockUtils.cpp:1077) Scanning from 346851 to 346851
-DEBUG - 1425897985: (Blockchain.cpp:211) Organizing chain
-INFO - 1425897985: (BlockUtils.cpp:1491) Loading block data... file 240 offset 91118264
-INFO - 1425897985: (BlockUtils.cpp:569) Reading raw blocks finished at file 240 offset 92021417
-WARN - 1425897985: (BlockUtils.cpp:1580) Block data did not extend the main chain!
Log file opened at 1425898315: /home/user/.armory/armorycpplog.txt
-INFO - 1425898374: (BlockUtils.cpp:866) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 1425898374: (BlockUtils.cpp:867) lmdb dir: /home/user/.armory/databases
-INFO - 1425898374: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1425898374: (BlockUtils.cpp:1187) Executing: doInitialSyncOnLoad
-INFO - 1425898374: (BlockUtils.cpp:1258) Total number of blk*.dat files: 241
-INFO - 1425898374: (BlockUtils.cpp:1259) Total blockchain bytes: 32,272,964,249
-INFO - 1425898374: (BlockUtils.cpp:1600) Reading headers from db
-INFO - 1425898379: (BlockUtils.cpp:1626) Found 346857 headers in db
-DEBUG - 1425898379: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1425898380: (BlockUtils.cpp:1288) --- Fetching SSH summaries for 573 registered addresses
-INFO - 1425898380: (BlockUtils.cpp:1301) Left off at file 240, offset 92021417
-INFO - 1425898380: (BlockUtils.cpp:1304) Reading headers and building chain...
-INFO - 1425898380: (BlockUtils.cpp:1305) Starting at block file 240 offset 92021417
-INFO - 1425898380: (BlockUtils.cpp:1307) Block height 346851
-DEBUG - 1425898380: (Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1425898381: (BlockUtils.cpp:1342) Looking for first unrecognized block
-INFO - 1425898381: (ReorgUpdater.h:257) Reassessing Tx validity after reorg
-INFO - 1425898381: (ReorgUpdater.h:180) Invalidating old-chain transactions...
-ERROR - 1425898381: (BDM_mainthread.cpp:427) BDM thread failed: std::exception I thought the logs from the previous run had some unusual output too, they're before the "BDM thread failed: std::exception" run
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 09, 2015, 05:15:48 PM
Is the error deterministic? Does it happen with latest commit?
Edit: Actually I expect the error to be deterministic. Armory was closed while it was on a fork. It's trying to get back on the main chain at start but since the block update code didn't handle things properly in the previous run it won't recover from this. The new code should prevent the bad state from happening in the first place.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 09, 2015, 05:28:02 PM
I'll be giving the latest git (bugfix-0.93) a spin fairly soon. And no, it's not deterministic. Armory runs inits properly most of the test tuns. There are a few different variations of patterns in the errors so far, so doesn't seem like necessarily the same error to someone who doesn't know the code.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 09, 2015, 05:41:38 PM
I'll be giving the latest git (bugfix-0.93) a spin fairly soon. And no, it's not deterministic. Armory runs inits properly most of the test tuns. There are a few different variations of patterns in the errors so far, so doesn't seem like necessarily the same error to someone who doesn't know the code.
Thanks for the help, it's really appreciated. Can I ask how you are testing this? I can't reproduce any of these bugs so I can't progress in fixing them without your log files currently. If I could experience them first hand, the fixing would be a lot faster.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 09, 2015, 06:22:01 PM
Can I ask how you are testing this?
Hardware/software?
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 09, 2015, 06:30:37 PM
Can I ask how you are testing this?
Hardware/software? Software.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 09, 2015, 06:52:45 PM
Can I ask how you are testing this?
Hardware/software? Software. http://qubes-os.org It's not so informative ATM, they're switching to a new wiki backend ("decentralised" on account of, presumably, licensing and being all git signing based stuff) In essence, Qubes OS is a Xen hypervisor implementation but with the desktop as a target and security the focus. You use a separate VM for everything/anything, as the PV template based approach gives you a lot of HDD space to play with to make dozens of VM's. I'm using vanilla Fedora 20 as the template to start with, then adding everything I need to run Bitcoin Core and build Armory (Fedora 20 is currently the only OS supported as standard, soon to be joined by Debian, Ubuntu, Arch and Whonix) My guess is that there's probably enough added latency at the disk and networking level due to all the virtualisation that I'm getting performance characteristics that you perhaps don't see with your setup. To make it totally clear: there is no supervising OS in this setup, it's like using VMWare ESXi, everything's a VM except the hypervisor layer.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 10, 2015, 10:21:32 AM
try the latest commit in bugfix.
It's looking good so far. No BDM errors at all. Will continue trying to stress it out later today.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 11, 2015, 12:36:30 AM
Still looking good. No BDM errors or activity in logs. Seems like my class of BDM error has been fixed by Monday's commits.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 11, 2015, 12:46:57 AM
Still looking good. No BDM errors or activity in logs. Seems like my class of BDM error has been fixed by Monday's commits.
Glad to hear that. This version will get a build tomorrow, after some Core socket layer issues get fixed.
Title: Re: Users experiencing the BDM error message
Post by: TimS on March 11, 2015, 05:57:42 PM
I'm getting a BDM error now: https://i.imgur.com/IsYuK6m.png (http://imgur.com/IsYuK6m) Was using 0.93.0.70 supernode, Win 7 x64. After restarting computer and trying to start Armory as usual, Armory showed "missing txio" error message (above) and crashed. Tried to update to latest 0.93-bugfix branch (0.93.0.80, build 66702e78f5), and run from ArmoryQt.py, and had same error. This is preventing me from running Armory at all. Do I need to rebuild/rescan, wait for new version, or something else? Sent logs via https://support.bitcoinarmory.com/ site.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 11, 2015, 07:53:31 PM
I'm getting a BDM error now: https://i.imgur.com/IsYuK6m.png (http://imgur.com/IsYuK6m) Was using 0.93.0.70 supernode, Win 7 x64. After restarting computer and trying to start Armory as usual, Armory showed "missing txio" error message (above) and crashed. Tried to update to latest 0.93-bugfix branch (0.93.0.80, build 66702e78f5), and run from ArmoryQt.py, and had same error. This is preventing me from running Armory at all. Do I need to rebuild/rescan, wait for new version, or something else? Sent logs via https://support.bitcoinarmory.com/ site. For supernode stability you'll have to wait on the next installment of DB changes. You can rebuild and rescan to fix this error if you want but there is no guarantee the current version will not run into that same issue again. If you want to make this more stable for now, you can keep a copy of a freshly scanned supernode DB on the side and overwrite bad ones with that to cut on the rescan time. I'm not going after the error directly because it is too convoluted, and the upcoming changes fix that. I'll merge the new stuff in dev sometimes this week then you're welcomed to try that instead. Both build&scan time and stability will be improved.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 11, 2015, 08:25:53 PM
Buggy happenings in 0.93.0.80 (SDM on):
Consistent disconcerting startups. "Armory is disconnected" page remains up for several minutes, and "Blocks remaining" never appears, not even "0 Blocks remaining". Also noticeably more sluggish to shutdown than any of the builds of 93.0.70
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 11, 2015, 09:54:40 PM
Buggy happenings in 0.93.0.80 (SDM on):
Consistent disconcerting startups. "Armory is disconnected" page remains up for several minutes, and "Blocks remaining" never appears, not even "0 Blocks remaining". Also noticeably more sluggish to shutdown than any of the builds of 93.0.70
These are being worked on as we speak
Title: Re: Users experiencing the BDM error message
Post by: etotheipi on March 12, 2015, 01:59:30 AM
And here it is. This should resolve a few more little issues, and has a reworking of some of the logic that was causing trouble for Carlton Banks:
Use the secure downloader to get 0.93.0.80 (only use the below links if necessary):
Armory 0.93.0.80-testing for Windows XP, Vista, 7, 8+ (64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_winAll.exe)
Armory 0.93.0.80-testing for MacOSX 10.7+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_osx.tar.gz)
Armory 0.93.0.80-testing for Ubuntu 12.04+ (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_ubuntu-32bit.deb)
Armory 0.93.0.80-testing for Ubuntu 12.04+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_ubuntu-64bit.deb)
Armory 0.93.0.80-testing for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_raspbian-armhf.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for Ubuntu 12.04 exact (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_offline_ubuntu_12.04-32.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for Ubuntu 12.04 exact (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_offline_ubuntu_12.04-64.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_rpi_bundle.tar.gz)
Armory 0.93.0.80-testing: Signed hashes of all installers (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_sha256sum.txt.asc)
Title: Re: Users experiencing the BDM error message
Post by: matrix01 on March 12, 2015, 04:04:34 AM
My sincere thanks to the entire team that worked on this release. I will be installing it tomorrow. However, can anyone in this forum please clarify the following:
Do I need to completely wipe out Armory version 0.93, Bitcoin QT version 10, and my entire blockchain data from my hard drive?
In other words do I need to start from scratch with a new bootstrap file for the blockchain and the latest versions of Armory and Bitcoin QT?
I ask because I was getting all the BDM errors that were plaguing Armory version 0.93.
Lastly, when will the 93.0.80 links shown above be posted in the Armory download site below? :
https://bitcoinarmory.com/download/ (https://bitcoinarmory.com/download/)
Again, thanks to everybody that worked on this new Armory release.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 12, 2015, 10:12:54 AM
Do I need to completely wipe out Armory version 0.93, Bitcoin QT version 10, and my entire blockchain data from my hard drive?
In other words do I need to start from scratch with a new bootstrap file for the blockchain and the latest versions of Armory and Bitcoin QT?
Can't tell without better details, but as a generalisation, Bitcoin Core 0.10.0 is more robust than Armory at this current stage. The likelihood is that an Armory Db rebuild will be the most you'll need.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 12, 2015, 10:20:29 AM
And here it is. This should resolve a few more little issues, and has a reworking of some of the logic that was causing trouble for Carlton Banks:
Use the secure downloader to get 0.93.0.80 (only use the below links if necessary):
Armory 0.93.0.80-testing for Windows XP, Vista, 7, 8+ (64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_winAll.exe)
Armory 0.93.0.80-testing for MacOSX 10.7+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_osx.tar.gz)
Armory 0.93.0.80-testing for Ubuntu 12.04+ (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_ubuntu-32bit.deb)
Armory 0.93.0.80-testing for Ubuntu 12.04+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_ubuntu-64bit.deb)
Armory 0.93.0.80-testing for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_raspbian-armhf.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for Ubuntu 12.04 exact (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_offline_ubuntu_12.04-32.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for Ubuntu 12.04 exact (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_offline_ubuntu_12.04-64.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_rpi_bundle.tar.gz)
Armory 0.93.0.80-testing: Signed hashes of all installers (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_sha256sum.txt.asc)
Just to be clear, the impeded communication between bitcoind and Armory is a definite issue in 0.93.0.80. Doesn't cause any functional issues, but when you're looking at "Armory is offline" for upwards of 2 or 3 minutes, it's tempting to quit what looks like a failed startup attempt (despite the difficulties, Armory does launch bitcoind, so if you quit when it's not connected to bitcoind... you guys know the rest)
Title: Re: Users experiencing the BDM error message
Post by: Romance on March 12, 2015, 10:30:42 AM
I am experiencing this starting today. I tried bitcoind with no problems but cannot get armory to start up properly. So far I have tried restarting my computer, and looking through the armory support and wasn't able to find anything. I am new to armory and do not know what to do from here. It happens 100% of the time. http://s11.postimg.org/d7a8c82eb/armoryerror.jpghelp? Edit: This happens even with 93.0.80 testing Edit #2: Re-scanning database seemed to have fix this problem for now.
Title: Re: Users experiencing the BDM error message
Post by: crazyivan on March 12, 2015, 01:06:44 PM
And here it is. This should resolve a few more little issues, and has a reworking of some of the logic that was causing trouble for Carlton Banks:
Use the secure downloader to get 0.93.0.80 (only use the below links if necessary):
Armory 0.93.0.80-testing for Windows XP, Vista, 7, 8+ (64-bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_winAll.exe)
Armory 0.93.0.80-testing for MacOSX 10.7+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_osx.tar.gz)
Armory 0.93.0.80-testing for Ubuntu 12.04+ (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_ubuntu-32bit.deb)
Armory 0.93.0.80-testing for Ubuntu 12.04+ (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_ubuntu-64bit.deb)
Armory 0.93.0.80-testing for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_raspbian-armhf.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for Ubuntu 12.04 exact (32bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_offline_ubuntu_12.04-32.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for Ubuntu 12.04 exact (64bit) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_offline_ubuntu_12.04-64.tar.gz)
Armory 0.93.0.80-testing Offline Bundle for RaspberryPi (armhf) (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_rpi_bundle.tar.gz)
Armory 0.93.0.80-testing: Signed hashes of all installers (https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.93.0.80-testing_sha256sum.txt.asc)
This one does not work for me at all. Just gets stuck in the middle of the process and stays there.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 12, 2015, 02:08:59 PM
A little console output: [user@fedora-20-x64 ~]$ python /usr/lib/armory-testing/ArmoryQt.py
/usr/lib/armory-testing/armoryengine/Transaction.py:2675: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
Unhandled Error
Traceback (most recent call last):
File "/usr/lib/armory-testing/ArmoryQt.py", line 7168, in <module>
os._exit(QAPP.exec_())
File "/usr/lib/armory-testing/qt4reactor.py", line 231, in _iterate
self.runUntilCurrent()
--- <exception caught here> ---
File "/usr/lib64/python2.7/site-packages/twisted/internet/base.py", line 800, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/usr/lib/armory-testing/ArmoryQt.py", line 6421, in Heartbeat
self.processAlerts()
File "/usr/lib/armory-testing/ArmoryQt.py", line 1944, in processAlerts
armoryClient = factory.getProto()
exceptions.AttributeError: 'NoneType' object has no attribute 'getProto'
-INFO - 1426169030: (BlockUtils.cpp:894) blkfile dir: /home/user/.bitcoin/blocks
-INFO - 1426169030: (BlockUtils.cpp:895) lmdb dir: /home/user/.armory/databases
-INFO - 1426169030: (lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1426169030: (BlockUtils.cpp:1226) Executing: doInitialSyncOnLoad
-INFO - 1426169030: (BlockUtils.cpp:1297) Total number of blk*.dat files: 243
-INFO - 1426169030: (BlockUtils.cpp:1298) Total blockchain bytes: 32,473,844,077
-INFO - 1426169030: (BlockUtils.cpp:1671) Reading headers from db
-INFO - 1426169035: (BlockUtils.cpp:1697) Found 347316 headers in db
-DEBUG - 1426169035: (Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1426169036: (BlockUtils.cpp:1327) --- Fetching SSH summaries for 573 registered addresses
-INFO - 1426169037: (BlockUtils.cpp:1340) Left off at file 242, offset 23860797
-INFO - 1426169037: (BlockUtils.cpp:1343) Reading headers and building chain...
-INFO - 1426169037: (BlockUtils.cpp:1344) Starting at block file 242 offset 23860797
-INFO - 1426169037: (BlockUtils.cpp:1346) Block height 347309
-DEBUG - 1426169037: (Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1426169037: (BlockUtils.cpp:1381) Looking for first unrecognized block
-INFO - 1426169037: (BlockUtils.cpp:1532) Loading block data... file 242 offset 23860797
-INFO - 1426169037: (BlockUtils.cpp:1398) Wrote blocks to DB in 7.1e-05s
-INFO - 1426169037: (BlockUtils.cpp:1415) Checking dupIDs from 347308 onward
-WARN - 1426169037: (BlockUtils.cpp:1116) Scanning from 347309 to 347309
-INFO - 1426169037: (BlockUtils.cpp:1494) Scanned Block range in 0.033637s
-INFO - 1426169037: (BlockUtils.cpp:1497) Finished loading at file 242, offset 23860797
-INFO - 1426169037: (BlockDataViewer.cpp:155) Enabling zero-conf tracking
-DEBUG - 1426169040: (Blockchain.cpp:211) Organizing chain
-INFO - 1426169040: (BlockUtils.cpp:1532) Loading block data... file 242 offset 23860797
-INFO - 1426169040: (BlockUtils.cpp:589) Reading raw blocks finished at file 242 offset 24386534
-WARN - 1426169040: (BlockUtils.cpp:1116) Scanning from 347310 to 347310
New Block: 347310
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 12, 2015, 03:52:57 PM
This one does not work for me at all. Just gets stuck in the middle of the process and stays there.
Log files
Title: Re: Users experiencing the BDM error message
Post by: CircusPeanut on March 12, 2015, 05:38:33 PM
My bad. I tried to make a last minute fix to an issue with processAlerts, and ended up causing an unrecoverable exception whenever processAlerts (called every minute) is called before the network connection is set up.
We are working on fixing this ASAP.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 12, 2015, 06:09:17 PM
Checkout bugfix, should be fixed now
Title: Re: Users experiencing the BDM error message
Post by: matrix01 on March 12, 2015, 07:09:30 PM
Just to clarify.
Because of this latest bugfix we should avoid installing 0.93.0.80 for now and wait for a different revision number to be releaed.
Am I correct?
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 12, 2015, 07:20:14 PM
Just to clarify.
Because of this latest bugfix we should avoid installing 0.93.0.80 for now and wait for a different revision number to be releaed.
Am I correct?
Avoid auto bitcoind in .0.80
Title: Re: Users experiencing the BDM error message
Post by: btchris on March 12, 2015, 08:08:47 PM
FYI I ran into... something. Running 67759a9 (will upgrade to the most recent now). I just now noticed that Armory wasn't running, it apparently crashed this morning. -DEBUG - 1426162994: (..\Blockchain.cpp:211) Organizing chain
-INFO - 1426162994: (..\BlockUtils.cpp:1531) Loading block data... file 242 offset 74249660
-INFO - 1426162994: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 242 offset 74606873
-WARN - 1426162994: (..\BlockUtils.cpp:1116) Scanning from 347295 to 347295
-DEBUG - 1426163115: (..\Blockchain.cpp:211) Organizing chain
-DEBUG - 1426163116: (..\Blockchain.cpp:211) Organizing chain
-WARN - 1426163116: (..\Blockchain.cpp:317) Reorg detected!
-DEBUG - 1426163116: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-INFO - 1426163117: (..\BlockUtils.cpp:1531) Loading block data... file 242 offset 74606873
-INFO - 1426163117: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 242 offset 75038837
-WARN - 1426163117: (..\BlockUtils.cpp:1633) Blockchain Reorganization detected!
-INFO - 1426163117: (c:\bitcoinarmory\cppforswig\ReorgUpdater.h:257) Reassessing Tx validity after reorg
-INFO - 1426163117: (c:\bitcoinarmory\cppforswig\ReorgUpdater.h:180) Invalidating old-chain transactions...
-ERROR - 1426163117: (..\BlockUtils.cpp:1658) Error adding block data: Cannot get undo data for block because not full!
-DEBUG - 1426163138: (..\Blockchain.cpp:211) Organizing chain
-INFO - 1426163138: (..\BlockUtils.cpp:1531) Loading block data... file 242 offset 75038837
-INFO - 1426163138: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 242 offset 75080650
-WARN - 1426163138: (..\BlockUtils.cpp:1116) Scanning from 347297 to 347297
-DEBUG - 1426163193: (..\Blockchain.cpp:211) Organizing chain
-INFO - 1426163193: (..\BlockUtils.cpp:1531) Loading block data... file 242 offset 75080650
-INFO - 1426163193: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 242 offset 75098598
-WARN - 1426163193: (..\BlockUtils.cpp:1116) Scanning from 347298 to 347298
-DEBUG - 1426163215: (..\Blockchain.cpp:211) Organizing chain
-INFO - 1426163215: (..\BlockUtils.cpp:1531) Loading block data... file 242 offset 75098598
-INFO - 1426163215: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 242 offset 75098810
-WARN - 1426163215: (..\BlockUtils.cpp:1116) Scanning from 347299 to 347299
-DEBUG - 1426164532: (..\Blockchain.cpp:211) Organizing chain
-INFO - 1426164532: (..\BlockUtils.cpp:1531) Loading block data... file 242 offset 75098810
-INFO - 1426164532: (..\BlockUtils.cpp:589) Reading raw blocks finished at file 242 offset 75906414
-WARN - 1426164532: (..\BlockUtils.cpp:1116) Scanning from 347300 to 347300
2015-03-12 08:23 (INFO) -- Networking.py:215 - Received new block. 0000000000000000142c8fa8984becbe71c90658c89c3f77490bc40ad2b9be0b
2015-03-12 08:23 (INFO) -- ArmoryQt.py:6242 - New Block! : 347295
2015-03-12 08:23 (INFO) -- ArmoryQt.py:6250 - Current block number: 347295
2015-03-12 08:25 (INFO) -- ArmoryQt.py:6242 - New Block! : 347296
2015-03-12 08:25 (INFO) -- ArmoryQt.py:6250 - Current block number: 347296
2015-03-12 08:25 (INFO) -- Networking.py:215 - Received new block. 000000000000000006a4096ac98c907a3354fdf2dae617739c588a80bf0b54d4
2015-03-12 08:25 (INFO) -- ArmoryQt.py:6242 - New Block! : 347297
2015-03-12 08:25 (INFO) -- ArmoryQt.py:6250 - Current block number: 347297
2015-03-12 08:26 (INFO) -- ArmoryQt.py:6242 - New Block! : 347298
2015-03-12 08:26 (INFO) -- ArmoryQt.py:6250 - Current block number: 347298
2015-03-12 08:26 (INFO) -- Networking.py:215 - Received new block. 0000000000000000018a2949009fe75921bb6737cb2c1bc887a8ea6bf5ce056f
2015-03-12 08:26 (INFO) -- ArmoryQt.py:6242 - New Block! : 347299
2015-03-12 08:26 (INFO) -- ArmoryQt.py:6250 - Current block number: 347299
2015-03-12 08:29 (INFO) -- announcefetch.py:271 - Fetching: https://bitcoinarmory.com/announce.txt
2015-03-12 08:48 (INFO) -- ArmoryQt.py:6242 - New Block! : 347300
2015-03-12 08:48 (INFO) -- ArmoryQt.py:6250 - Current block number: 347300
Title: Re: Users experiencing the BDM error message
Post by: matrix01 on March 13, 2015, 04:47:05 AM
Goatpig,
Is the plan for a new release to come out? In other words, will version 0.93.0.90 be coming out soon to replace version 0.93.0.80 ? Or is the new fix going to be amended to 0.93.0.80 ?
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 13, 2015, 10:58:43 AM
Checkout bugfix, should be fixed now
Had to do a little playing around to get Armory out of a buggy RPC related state that made it seem like all that was fixed was the error output on the console, but managed to make it normal again (quit while RPC wasn't connected, launching .80 with bitcoind still running, end bitcoind process, restart SDM mode from Armory dashboard...) Seems to be resilient to not re-setting that state so far. Sluggish bitcoind disconnection on Shutdown seems improved also.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 13, 2015, 11:28:17 AM
Seems to be resilient to not re-setting that state so far.
...until the VM is shutdown that is. Armory gets stuck on "Armory is offline" dashboard page, unable to talk to bitcoind over RPC. The "quiting while RPC is out" trick consistently makes RPC/feedback in the Armory GUI return.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 13, 2015, 12:53:57 PM
So, I've discovered that if you quit Armory when it reports "Bitcoin Engine Initializing", Armory doesn't end the bitcoind process at all. Even if the progress bar is active and the number of remaining blocks is shown.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 13, 2015, 03:30:08 PM
So, I've discovered that if you quit Armory when it reports "Bitcoin Engine Initializing", Armory doesn't end the bitcoind process at all. Even if the progress bar is active and the number of remaining blocks is shown.
That's weird, guardian should be handling that. It's specifically meant to kill instances of bitcoind that have survived the parent Armory process. I'll investigate.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 13, 2015, 04:03:15 PM
To clarify, there's nothing predictable about this. I thought otherwise earlier, but it was apparent non-random patterns of the bug appearing that turned out to be random as I tested more.
Another quirk with this bug: the progress bars get displayed at different lengths/resolutions for "Armory is offline" and "Bitcoin Engine Initializing" notifications. That's normal behaviour (for my Armory, anyway). The progress bars for "Armory is offline" ordinarily do not fill though, they disappear and are replaced with shorter ones before they fill (alongside "Bitcoin Engine Initializing" notification). It's noticeable, as when this happens "Armory is offline" remains on dash while bitcoind syncs to the top block, and it is only then (when the top block is downloading) do you get to see anything in the progress bar, or a number of remaining blocks. Edit: just witnessed the undisplaced/un-resized progress bar indicate 18 blocks, so scratch that last part
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 15, 2015, 12:27:05 PM
Just to update, still getting problems with RPC connection and BDM errors using SDM mode on 93.0.82. The BDM errors are reduced to a rare event, but still occasionally happen (1 so far since testing .82).
I'm fairly sure all/most of these BDM are false positives, as the BDM reports zero problems on subsequent runs whether you re-build Db or not. It'd be good to hear ATI's opinion on that. I'm fairly certain that the old Armory Db would fail deterministically once an error was detected.
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 15, 2015, 05:05:51 PM
Just to update, still getting problems with RPC connection and BDM errors using SDM mode on 93.0.82. The BDM errors are reduced to a rare event, but still occasionally happen (1 so far since testing .82).
I'm fairly sure all/most of these BDM are false positives, as the BDM reports zero problems on subsequent runs whether you re-build Db or not. It'd be good to hear ATI's opinion on that. I'm fairly certain that the old Armory Db would fail deterministically once an error was detected.
I think we're not gonna touch the RPC comm layer any furter for now. It needs to be reworked to a certain extend and that's too disruptive for the class of fixes we are aiming to ship in this version. I personally think the remaining RPC errors aren't deal breakers, and that our users will have the good grace to endure them until I come up with a rework of that 2 years old code (instead of band aid patches here and there, which haven't played up to expectation). As for the BDM errors, I dialed down the error message because I expect all left over issues are false positives. The BDM error just shuts down Armory now (rebuild and rescan isn't checked by default in the error message), and the next start will just repair the issue (if there is one indeed) until I get to the bottom of it. I did push a tiny but significant change a couple days ago which should fix some latent BDM errors.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 15, 2015, 06:32:42 PM
Sounds like a good plan.
I don't currently use SDM anyway, just trying to help clear your workload so you can develop the features I'm more interested in (reduced DB, input level coin control, BIP32 based wallet format)
Title: Re: Users experiencing the BDM error message
Post by: goatpig on March 15, 2015, 08:18:10 PM
Sounds like a good plan.
I don't currently use SDM anyway, just trying to help clear your workload so you can develop the features I'm more interested in (reduced DB, input level coin control, BIP32 based wallet format)
And I'm grateful for that. BIP32 is etotheipi's task, that's not dependent on anything I do =P.
Title: Re: Users experiencing the BDM error message
Post by: Carlton Banks on March 16, 2015, 12:01:49 AM
Sounds like a good plan.
I don't currently use SDM anyway, just trying to help clear your workload so you can develop the features I'm more interested in (reduced DB, input level coin control, BIP32 based wallet format)
And I'm grateful for that. BIP32 is etotheipi's task, that's not dependent on anything I do =P. Not holding my breath for BIP32, I expect Alan will want to be super considered about doing that task. I am looking forward to the fine grained coin control *ahem* ;D Seriously though, the gratitude is more than reciprocated. I'm really happy with how the Armory project is turning out, and it always needed a team of developers to help Alan focus on the visionary part. You guys are the standard, and that's really going to get driven home this year IMO. Soon as these two big foundation components (DB & wallet 2.0) are done, then that's the basis to attract more users and for the feature set to become even more diverse.
|
