I am attempting to sync from scratch a full node (v0.15.1) on a linux machine (Linux Mint running Ubuntu precise 12.04.1 LTS). The sync grinds to a halt on block #338818. From examining debug.log I can see the issue is the next block #338819 being deemed invalid. Here is an excerpt from debug.log demonstrating that:
2018-02-02 16:36:52 ERROR: AcceptBlockHeader: block 0000000000000000159e7d66c954312bccb5f12de808f2991b3859205665c442 is marked invalid 2018-02-02 16:36:52 ERROR: invalid header received 2018-02-02 16:36:52 ProcessMessages(headers, 162003 bytes) FAILED peer=217
bitcoin-qt continues to ask peers for the block header and keeps rejecting it as invalid, even though this block seems to be valid as part of the main chain, at least according to all known nodes that I checked (e.g. blockchain.info, blocktrail and several others).
I googled for this block # and found nothing, so I assume nobody else has this problem. What is going on? What should I do to continue with the sync?