Users experiencing the BDM error message

[goatpig]

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 =)

[1715666172]

1715666172

[justusranvier]

Compiles, indexes blockchain and runs.

So far, so good.

[goatpig]

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.

[crazyivan]

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.

[doug_armory]

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?

[crazyivan]

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.

[btchris]

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

[doug_armory]

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.

[goatpig]

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.

[goatpig]

updated the fix some more, people running this fix please pull and build again.

[btchris]

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

[btchris]

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.

[goatpig]

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.

[btchris]

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.

[goatpig]

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

[goatpig]

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?

[btchris]

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:

Code:

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

[goatpig]

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?

[btchris]

Is it displaying the correct top block now?

Yes.

[goatpig]

bump