Topic: Wrong network? (Read 1103 times)
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.
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.
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.
"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.
"f9 be b4 d9" are the first bytes, I think that may have just been a weird bug in Armory
Look at the file content yourself, is it leading 0s?
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.
Code:
-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.
Jump to: