zombieslayer9099 (OP)
Full Member
 Offline
Activity: 120
Merit: 100
Java Coder
|
 |
April 07, 2015, 12:21:44 AM |
|
-ERROR - 1428364614: (BDM_mainthread.cpp:429) BDM thread failed: Block file '/Users/admin/Library/Application Support/Bitcoin/blocks/blk00253.dat' is the wrong network! File: 00000000, expecting f9beb4d9 What does this mean? I pray that I don't need to rebuild my Core database. |
Did you know there are 1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976 possible bitcoin addresses? To put that into perspective, that's greater than the width of the universe in zeptometers (10^-21 meter). ▁ ▂ ▄ ▅ ▆ Cloudmining 101: how to avoid scams ▆ ▅ ▄ ▂ ▁ |
|
|
|
|
|
|
|
|
|
The trust scores you see are subjective; they will change depending on who you have in your trust list. |
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
doug_armory
|
|
April 07, 2015, 01:00:26 AM |
|
Looks like, for some reason, there's a chunk of data in the file that has 0x00000000 instead of a mainnet block's "magic bytes." Not sure offhand why this would happen. Somebody else will have to comment.
|
Senior Developer - Armory Technologies, Inc.
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3654
Merit: 1345
Armory Developer
|
|
April 07, 2015, 01:35:27 AM |
|
Look at the file content yourself, is it leading 0s?
|
|
|
|
zombieslayer9099 (OP)
Full Member
Offline
Activity: 120
Merit: 100
Java Coder
|
|
April 07, 2015, 02:14:57 AM |
|
"f9 be b4 d9" are the first bytes, I think that may have just been a weird bug in Armory
|
Did you know there are 1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976 possible bitcoin addresses? To put that into perspective, that's greater than the width of the universe in zeptometers (10^-21 meter). ▁ ▂ ▄ ▅ ▆ Cloudmining 101: how to avoid scams ▆ ▅ ▄ ▂ ▁ |
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3654
Merit: 1345
Armory Developer
|
|
April 07, 2015, 02:19:38 AM |
|
"f9 be b4 d9" are the first bytes, I think that may have just been a weird bug in Armory
It's possible Armory looked at the file right when Core created it but before anything was written to it, so it read a bunch of 0s instead. |
|
|
|
helgabutters
Newbie
Offline
Activity: 43
Merit: 0
|
|
April 25, 2015, 12:05:40 AM
Last edit: April 25, 2015, 07:22:19 AM by helgabutters |
|
I am having this issue consistently in 0.93.1 Linux.
I leave armory running 24/7 and check on it every few days. Most of the time I'll find this error which means it hasn't been keeping the database updated so it crashes armory and I need to restart and wait for it to catch up.
|
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3654
Merit: 1345
Armory Developer
|
|
April 25, 2015, 08:12:53 AM |
|
The issue isn't so much that this situation happens but that Armory considers it's a fatal throw and kills the main backend thread as a result (instead of ignoring this error). Will be fixed in the upcoming version.
|
|
|
|
|
