Bitcoin-abc: Node won't sync past block 556767

[kocho]

Describe the issue

The node won't sync past block 556767

Expected behaviour

Sync till the end..

Actual behaviour

Stops at 556767.

What version of bitcoin-abc are you using?

Bitcoin ABC version v0.18.5.0-d1d091ba7

Any extra information that might be useful in the debugging process.

This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

2018-12-07 08:00:55 connect() to 34.244.54.146:8333 failed after select(): Connection refused (111)
2018-12-07 08:01:01 receive version message: [101.53.138.221:8333] /Bitcoin ABC:0.18.4(EB32.0)/: version 70015, blocks=559762, us=31.15.133.130:35086, peer=11
2018-12-07 08:01:38 ERROR: AcceptBlockHeader: block 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b is marked invalid
2018-12-07 08:01:38 ERROR: invalid header received
2018-12-07 08:01:38 ProcessMessages(headers, 162003 bytes) FAILED peer=1
2018-12-07 08:01:38 ERROR: AcceptBlockHeader: block 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b is marked invalid
2018-12-07 08:01:38 ERROR: invalid header received
2018-12-07 08:01:38 ProcessMessages(headers, 162003 bytes) FAILED peer=3
2018-12-07 08:01:44 ERROR: AcceptBlockHeader: block 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b is marked invalid
2018-12-07 08:01:44 ERROR: invalid header received
2018-12-07 08:01:44 ProcessMessages(headers, 162003 bytes) FAILED peer=2
2018-12-07 08:01:47 receive version message: [158.69.167.93:8333] /Bitcoin SV:0.1.0(EB128.0)/: version 70015, blocks=559740, us=31.15.$

[markblundeberg]

You may need to run bitcoin-cli reconsiderblock 0000000000000000004626ff6e3b936941d341c5932ece4357eeccac44e6d56c.

The block 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b that it is talking about is the first SV post-fork block and it's indeed invalid on ABC.

Another possibility is that you don't have any post-fork peers, but your debug.log seems to indicate you have at least one of them.

[kocho]

You may need to run bitcoin-cli reconsiderblock 0000000000000000004626ff6e3b936941d341c5932ece4357eeccac44e6d56c.

The block 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b that it is talking about is the first SV post-fork block and it's indeed invalid on ABC.

Another possibility is that you don't have any post-fork peers, but your debug.log seems to indicate you have at least one of them.

Thanx, running the reconsiderblock command solved the issue!

Cheers!