Quote from: genjix on March 16, 2014, 11:59:14 AM

Quote from: gwlloyd on March 16, 2014, 12:39:01 AM

I'm now on my fifth attempt using 2 different servers (one a pretty much clean Debian VM and one an established server).. every time I get nearly to the end of the blockchain sync it just seems to sit around not receiving new blocks and spewing reams of errors such as below. I'm assuming blockchain database corruption but it always seems to be somewhere in the 27#### block range (I've just noticed this). Is this normal? Is there maybe something about this range of blocks, was that when someone was spamming the blockchain? Getting a bit frustrated here sapping so much time and bandwidth and still haven't got a sync'd copy to play with. I don't want to download a torrent copy.

WARNING: Error storing memory pool transaction c0c958698d61b260a885115a7e2ccec1a25c8a121c0da9ec6165f0ce11920c9b: Spent input not found

Nope it looks fine. Those errors aren't a problem. Example: memory pool isn't full yet and there's txs depending on other txs in the mempool that aren't yours. It's normal. I'll make the wording sound less extreme.

Important is that you're able to run 'sx fetch-last-height' and the block height matches blockchain.info or somewhere else.

I need to document these tools better. Sorry about that. I'll be making efforts towards that goal as documentation is important.

The docs aren't that bad and the error does make sense - if it hasn't got the full blockchain then there are going to be transactions that don't make sense to it, so it can't store them.

It's sticking on block 278746 every time and once it gets to that block it is still using CPU but nowhere near the levels it normally uses when sync'ing. Looking up the blocks around this time it doesn't seem to be a gorilla block. Any ideas? Perhaps start fresh without my local bitcoind as one of the manual nodes.. is there any way my bitcoind could have a bad blockchain and not know about it?