Bitcoin-abc: Errors after update to 0.19.5

[vladyslavstartsev]

Describe the issue

Hi! I get those errors after update

2019-05-15T18:39:34Z New outbound peer connected: version: 70015, blocks=582502, peer=0
2019-05-15T18:39:35Z ERROR: ContextualCheckBlockHeader: rejected by checkpoint lock-in at 556767
2019-05-15T18:39:35Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b, checkpoint mismatch (code 67)
2019-05-15T18:39:35Z Misbehaving: 3.120.108.75:8333 peer=0 (0 -> 100) reason: checkpoint mismatch BAN THRESHOLD EXCEEDED
2019-05-15T18:39:35Z ERROR: invalid header received
2019-05-15T18:39:39Z Loading addresses from DNS seeds (could take a while)
2019-05-15T18:39:42Z 29 addresses found from DNS seeds
2019-05-15T18:39:42Z dnsseed thread exit
2019-05-15T18:39:42Z New outbound peer connected: version: 80003, blocks=582711, peer=3
2019-05-15T18:39:42Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:39:42Z ERROR: invalid header received
2019-05-15T18:39:54Z New outbound peer connected: version: 70015, blocks=556767, peer=5
2019-05-15T18:40:01Z New outbound peer connected: version: 80003, blocks=582711, peer=7
2019-05-15T18:40:01Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:40:01Z ERROR: invalid header received
2019-05-15T18:40:01Z New outbound peer connected: version: 70015, blocks=582502, peer=8
2019-05-15T18:40:02Z ERROR: ContextualCheckBlockHeader: rejected by checkpoint lock-in at 556767
2019-05-15T18:40:02Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b, checkpoint mismatch (code 67)
2019-05-15T18:40:02Z Misbehaving: 107.155.94.22:8333 peer=8 (0 -> 100) reason: checkpoint mismatch BAN THRESHOLD EXCEEDED
2019-05-15T18:40:02Z ERROR: invalid header received
2019-05-15T18:40:18Z connect() to 196.52.84.9:8333 failed after select(): Connection refused (111)
2019-05-15T18:40:19Z connect() to [2607:1c00:a:6:3c1c:1b0d:ba4:8ea9]:8333 failed: Network is unreachable (101)
2019-05-15T18:40:26Z New outbound peer connected: version: 70015, blocks=582711, peer=11
2019-05-15T18:40:26Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:40:26Z ERROR: invalid header received
2019-05-15T18:40:39Z New outbound peer connected: version: 70015, blocks=582680, peer=15
2019-05-15T18:40:46Z New outbound peer connected: version: 70015, blocks=582680, peer=16
2019-05-15T18:40:46Z connect() to [2a02:810d:4bbf:f1c8:caa0:b2dd:4762:c5cc]:8333 failed: Network is unreachable (101)
2019-05-15T18:40:46Z New outbound peer connected: version: 70015, blocks=556767, peer=17
2019-05-15T18:40:47Z ERROR: ContextualCheckBlockHeader: rejected by checkpoint lock-in at 556767
2019-05-15T18:40:47Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000000000000000067d19fc7aba2667b4676a4c84c2fb0d4da7043469601ed, checkpoint mismatch (code 67)
2019-05-15T18:40:47Z Misbehaving: 77.120.105.164:8333 peer=17 (0 -> 100) reason: checkpoint mismatch BAN THRESHOLD EXCEEDED
2019-05-15T18:40:47Z ERROR: invalid header received
2019-05-15T18:40:47Z New outbound peer connected: version: 70015, blocks=582680, peer=18
2019-05-15T18:40:53Z New outbound peer connected: version: 70015, blocks=582502, peer=19
2019-05-15T18:40:55Z ERROR: ContextualCheckBlockHeader: rejected by checkpoint lock-in at 556767
2019-05-15T18:40:55Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b, checkpoint mismatch (code 67)
2019-05-15T18:40:55Z Misbehaving: 110.173.58.138:8333 peer=19 (0 -> 100) reason: checkpoint mismatch BAN THRESHOLD EXCEEDED
2019-05-15T18:40:55Z ERROR: invalid header received
2019-05-15T18:41:05Z New outbound peer connected: version: 70015, blocks=582711, peer=20
2019-05-15T18:41:05Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:41:05Z ERROR: invalid header received
2019-05-15T18:41:11Z New outbound peer connected: version: 70015, blocks=582711, peer=21
2019-05-15T18:41:12Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:41:12Z ERROR: invalid header received
2019-05-15T18:41:23Z New outbound peer connected: version: 70015, blocks=582711, peer=22
2019-05-15T18:41:23Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:41:23Z ERROR: invalid header received
2019-05-15T18:41:23Z connect() to 159.203.171.147:8333 failed after select(): Connection refused (111)
2019-05-15T18:41:30Z New outbound peer connected: version: 70015, blocks=582680, peer=24
2019-05-15T18:41:31Z connect() to [2a02:1205:c6ae:3c30:5fd5:b8ea:e6b4:87cf]:8333 failed: Network is unreachable (101)
2019-05-15T18:41:37Z New outbound peer connected: version: 70015, blocks=582502, peer=25
2019-05-15T18:41:42Z ERROR: ContextualCheckBlockHeader: rejected by checkpoint lock-in at 556767
2019-05-15T18:41:42Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b, checkpoint mismatch (code 67)
2019-05-15T18:41:42Z Misbehaving: 43.229.135.100:8333 peer=25 (0 -> 100) reason: checkpoint mismatch BAN THRESHOLD EXCEEDED
2019-05-15T18:41:42Z ERROR: invalid header received
2019-05-15T18:41:44Z connect() to 85.10.200.30:8333 failed after select(): Connection refused (111)
2019-05-15T18:41:45Z connect() to 83.135.153.66:8333 failed after select(): No route to host (113)
2019-05-15T18:41:51Z connect() to [2a02:587:3a05:9e5:1c0:d9b2:244f:8b16]:8333 failed: Network is unreachable (101)
2019-05-15T18:41:57Z New outbound peer connected: version: 70015, blocks=582680, peer=28
2019-05-15T18:42:10Z connect() to 180.199.222.12:8333 failed after select(): Connection refused (111)
2019-05-15T18:42:10Z connect() to [2a02:8108:2340:1c18:f9bb:5c8a:fa0f:fbc5]:8333 failed: Network is unreachable (101)
2019-05-15T18:42:16Z New outbound peer connected: version: 70015, blocks=582711, peer=30
2019-05-15T18:42:16Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:42:16Z ERROR: invalid header received
2019-05-15T18:42:17Z New outbound peer connected: version: 70015, blocks=582680, peer=31
2019-05-15T18:42:17Z New outbound peer connected: version: 70015, blocks=582711, peer=32
2019-05-15T18:42:18Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:42:18Z ERROR: invalid header received
2019-05-15T18:42:20Z New outbound peer connected: version: 70015, blocks=354818, peer=34
2019-05-15T18:42:41Z connect() to 134.209.255.124:8333 failed after select(): Connection refused (111)
2019-05-15T18:42:42Z New outbound peer connected: version: 70015, blocks=582711, peer=35
2019-05-15T18:42:42Z ERROR: AcceptBlockHeader: block 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 is marked invalid
2019-05-15T18:42:42Z ERROR: invalid header received
2019-05-15T18:42:55Z connect() to 141.223.82.131:8333 failed after select(): Connection refused (111)
2019-05-15T18:43:18Z New outbound peer connected: version: 70015, blocks=582680, peer=39

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

no

Expected behaviour

Tell us what should happen

the node should sync as expected

the blocks should sync and be up to date

Actual behaviour

Tell us what happens instead

it is stopped at 582680 and not moving

What version of bitcoin-abc are you using?

List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
Bitcoin ABC version v0.19.5.0-ab16e612d - official binary

Machine specs:

docker container

• OS: ubuntu 16

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.
I've updated the the node, which was staying for long time without update (approx. from February)

---

You guys should have some guides for updating node and stuff like that, I was not sure how to do it

[N7DTM]

bitcoin-cli invalidateblock 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18
bitcoin-cli reconsiderblock 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18

[drsaluml]

Thanks N7DTM

[DaSpawn]

I just noticed my node was stuck also, first block I seen in debug.log with error was 000000000000000001304365b292ced9ce6a538862a399fa0e37545541f2008e so I did the invalidateblock/reconsiderblock block on that and my node caught right back up

Shortly after that I seen errors about 000000000000000001d956714215d96ffc00e0afda4cd0a96c96f8d802b1662b, so had to do the same to that block also