Bitcoin-qt stuck at block 332082 #6275

Related to #5645 I'm sure as it's the same block number.

The debug.log shows:- 2015-06-12 09:33:02 received(8,40) block 00000000000000001b02953d79004a6e9da88fd4fe8e76ca7c58d69eb85f8ad9 (height:322083) peer=103 (26) size=34234 2015-06-12 09:33:02 ERROR: CScriptCheck() : 971b4d9d20553ed5183e807a5aebba036599189b20a6b9a831c7f2c402654552:0 VerifySignature failed: Script evaluated without error but finished with a false/empty top stack element 2015-06-12 09:33:02 Misbehaving: peer=103 (0 -> 100) BAN THRESHOLD EXCEEDED 2015-06-12 09:33:02 InvalidChainFound: invalid block=00000000000000001b02953d79004a6e9da88fd4fe8e76ca7c58d69eb85f8ad9 height=322083 log2_work=80.793972 date=2014-09-22 22:45:12 2015-06-12 09:33:02 InvalidChainFound: current best=00000000000000001e6da8c11a8669fa7353cb5f56d5679591b10072f49e5cd2 height=322082 log2_work=80.793884 date=2014-09-22 22:26:14 2015-06-12 09:33:02 ERROR: ConnectTip() : ConnectBlock 00000000000000001b02953d79004a6e9da88fd4fe8e76ca7c58d69eb85f8ad9 failed 2015-06-12 09:33:02 InvalidChainFound: invalid block=00000000000000001b02953d79004a6e9da88fd4fe8e76ca7c58d69eb85f8ad9 height=322083 log2_work=80.793972 date=2014-09-22 22:45:12 2015-06-12 09:33:02 InvalidChainFound: current best=00000000000000001e6da8c11a8669fa7353cb5f56d5679591b10072f49e5cd2 height=322082 log2_work=80.793884 date=2014-09-22 22:26:14

Bitcoin-qt is compiled from source, following intructions given.

debug.log headers:-

2015-06-08 19:38:32 Bitcoin version v0.9.99.0-2d03f60 (2014-12-21 17:43:47 +0800) 2015-06-08 19:38:32 Using OpenSSL version OpenSSL 1.0.1 14 Mar 2012 2015-06-08 19:38:32 Using BerkeleyDB version Berkeley DB 5.1.25: (January 28, 2011)

Surely bitcoin source from only a few months back should still work, right?

Problems at that block are related to a change in OpenSSL which forks the chain. If you use 0.9.x you should upgrade to at least 0.9.4 (or cherry-pick 037bfef), or use 0.10.x, or 0.11.0rc1. Current master also has the problem fixed. Pre-built executables also don't have the issue because they link OpenSSL statically.

@laanwj Perhaps I should raise a separate issue for this, but even after upgrading to the current master, the node is still stuck. Can a check be added so that it re-checks the last the last block that was found to be invalid? This would save the user from ever needing to perform a manual reindex.

Do invalidateblock then reconsiderblock

Thanks @laanwj . Is it worth having bitcoin core automatically reconsider blocks upon startup to save users from having to run this manually?