Failure fetching input transaction

[evoskuil]

08:04:43.777374 WARNING [validate] Failure fetching input transaction.
08:04:43.778380 WARNING [validate] Invalid input [cb57c8ee6d29c8343bb3c783bd068edb6a3d75489b8ba16d1431b3884b389881:464]
08:04:43.791376 WARNING [validate] Invalid block [000000000000000005a91d4e72303f6b112af30ebc40262d404826c07feeb772] validation of inputs failed
08:04:43.791376 ERROR [poller] Error storing block [000000000000000005a91d4e72303f6b112af30ebc40262d404826c07feeb772] validation of inputs failed

[evoskuil]

This look similar in behavior to #118 but could not share the same cause.

[evoskuil]

This problem reproduces on Windows without-consensus and does not affect Linux with-consensus builds.

[evoskuil]

I added the hash of the transaction to debug output, and stepped through the failure in a debugger. The code is behaving properly but the transaction is not found in the blockchain. BX confirms this when directed at this server:

$ bx fetch-tx 6f765bff6e4f5496702edb7ee5c66f45c9119a80d2c5fb2e2c352f09151507eb
object does not exist

When directed at the production (Airbitz) server the transaction is returned, and block explorers confirm the tx at height 360073. Given that the problem server is synced through block 391384 the blockchain is clearly missing this transaction.

There is no conditional code that would cause this behavior to vary between Windows and Linux, so this reinforces the conclusion that the blockchain is corrupt on this server. This is rare but it is known to be possible. This particular server had at least one hard shutdown (due to libbitcoin/libbitcoin-server#145).

[evoskuil]

I re-synced with the same build and this issue did not recur.