Users experiencing the BDM error message

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: goatpig on March 15, 2015, 03:18:10 PM

Quote from: Carlton Banks on March 15, 2015, 01: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)

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* Grin

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.

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Quote from: Carlton Banks on March 15, 2015, 01: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)

And I'm grateful for that. BIP32 is etotheipi's task, that's not dependent on anything I do =P.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

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)

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Quote from: Carlton Banks on March 15, 2015, 07:27:05 AM

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.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

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.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

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

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Quote from: Carlton Banks on March 13, 2015, 07:53:57 AM

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.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

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.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: Carlton Banks on March 13, 2015, 05:58:43 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.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: goatpig on March 12, 2015, 01:09:17 PM

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.

matrix01

member

Activity: 65

Merit: 30

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 ?

btchris

hero member

Activity: 672

Merit: 504

a.k.a. gurnec on GitHub

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.

Code:

-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

Code:

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

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Quote from: matrix01 on March 12, 2015, 02: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?

Avoid auto bitcoind in .0.80

matrix01

member

Activity: 65

Merit: 30

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?

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Checkout bugfix, should be fixed now

CircusPeanut

full member

Activity: 123

Merit: 100

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.

goatpig

legendary

Activity: 3738

Merit: 1360

Armory Developer

Quote from: crazyivan on March 12, 2015, 08:06:44 AM

This one does not work for me at all. Just gets stuck in the middle of the process and stays there.

Log files

Carlton Banks

legendary

Activity: 3430

Merit: 3080

A little console output:

Code:

[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 
    os._exit(QAPP.exec_())
  File "/usr/lib/armory-testing/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
---  ---
  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

crazyivan

legendary

Activity: 1652

Merit: 1007

DMD Diamond Making Money 4+ years! Join us!

Quote from: etotheipi on March 11, 2015, 08:59:30 PM

This one does not work for me at all. Just gets stuck in the middle of the process and stays there.

Romance

newbie

Activity: 23

Merit: 0

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.jpg

help?

Edit: This happens even with 93.0.80 testing

Edit #2: Re-scanning database seemed to have fix this problem for now.

Topic: Users experiencing the BDM error message (Read 5801 times)