Nope, this is a bug that I've tried to fix a couple times, and I have some pretty brutal unit-tests to try to squeeze it out (which pass, by the way), but it still fails on the actual network.

I would spend more time to fix it, but it's actually going to become irrelevant in a couple weeks.  When I get the persistent blockchain utilities implemented, I won't even be reading block files any more and this won't be a problem (I will use it for full scans, but not for each block update).

This is also why I haven't spent much time on armoryd... because it's not very useful as a server if it's just going to crash like that every few days