Topic: Syncing Headers (Read 166 times)

Thanks mate, it solved the problem!!!

Use the command "reconsiderblock" to remove the invalidity status of that particular block hash (it's actually valid), if you're using the GUI, enter it in the console (Window->Console).
You can copy-paste this command:

Here is part of today's log:

2021-04-01T04:31:21Z New outbound peer connected: version: 70016, blocks=677251, peer=0 (block-relay)
2021-04-01T04:31:22Z New outbound peer connected: version: 70016, blocks=677251, peer=1 (block-relay)
2021-04-01T04:31:22Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:22Z Disconnecting and discouraging peer 0!
2021-04-01T04:31:23Z New outbound peer connected: version: 70016, blocks=677251, peer=2 (full-relay)
2021-04-01T04:31:24Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:24Z Disconnecting and discouraging peer 1!
2021-04-01T04:31:24Z New outbound peer connected: version: 70015, blocks=677251, peer=3 (full-relay)
2021-04-01T04:31:25Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:25Z Disconnecting and discouraging peer 2!
2021-04-01T04:31:25Z New outbound peer connected: version: 70015, blocks=677251, peer=5 (full-relay)
2021-04-01T04:31:26Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:26Z Disconnecting and discouraging peer 3!
2021-04-01T04:31:26Z New outbound peer connected: version: 70015, blocks=677251, peer=6 (full-relay)
2021-04-01T04:31:27Z New outbound peer connected: version: 70016, blocks=677251, peer=7 (full-relay)
2021-04-01T04:31:28Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:28Z Disconnecting and discouraging peer 6!
2021-04-01T04:31:28Z New outbound peer connected: version: 70015, blocks=677251, peer=8 (full-relay)
2021-04-01T04:31:29Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:29Z Disconnecting and discouraging peer 7!
2021-04-01T04:31:34Z New outbound peer connected: version: 70016, blocks=677251, peer=9 (full-relay)
2021-04-01T04:31:35Z ERROR: AcceptBlockHeader: block 00000000000000000000570cd87702ae5d9979f17543b38ca62937f2858bc091 is marked invalid
2021-04-01T04:31:35Z Disconnecting and discouraging peer 9!
2021-04-01T04:31:51Z New outbound peer connected: version: 70016, blocks=677251, peer=11 (full-relay)
2021-04-01T04:31:52Z New outbound peer connected: version: 70015, blocks=677251, peer=12 (full-relay)
2021-04-01T04:31:53Z P2P peers available. Skipped DNS seeding.
2021-04-01T04:31:53Z dnsseed thread exit
2021-04-01T04:32:10Z New outbound peer connected: version: 70015, blocks=677251, peer=13 (full-relay)
2021-04-01T04:32:10Z New outbound peer connected: version: 70015, blocks=677251, peer=14 (full-relay)
2021-04-01T04:32:22Z New outbound peer connected: version: 70015, blocks=677251, peer=15 (full-relay)
2021-04-01T04:32:23Z New outbound peer connected: version: 70015, blocks=677251, peer=16 (full-relay)
2021-04-01T04:32:29Z New outbound peer connected: version: 70015, blocks=677251, peer=17 (full-relay)
2021-04-01T04:32:35Z New outbound peer connected: version: 70015, blocks=677251, peer=18 (full-relay)
2021-04-01T04:32:42Z New outbound peer connected: version: 70015, blocks=677251, peer=19 (full-relay)
2021-04-01T04:32:42Z New outbound peer connected: version: 70015, blocks=677251, peer=20 (block-relay)
2021-04-01T04:32:49Z New outbound peer connected: version: 70016, blocks=677251, peer=21 (full-relay)
2021-04-01T04:32:55Z New outbound peer connected: version: 70015, blocks=677251, peer=22 (block-relay)
2021-04-01T04:32:56Z New outbound peer connected: version: 70015, blocks=677251, peer=23 (block-relay)
2021-04-01T04:33:05Z New outbound peer connected: version: 70015, blocks=677251, peer=24 (block-relay)
2021-04-01T04:33:07Z New outbound peer connected: version: 70015, blocks=677251, peer=25 (block-relay)

Did you have any previous unclean shutdown or reindex? I've had this problem when I was reindexing and it got stuck at ~70% and just synchronized the header and freezes all the time. Resource constraint was not an issue; problem solved by deleting the entire data directory to synchronize again as I suspected a corruption with the blocks.

Can you check if the height of the headers of your peers and if they're constantly getting disconnected? Debug.log should give you some insight, go to Window>Information and click the open button under the debug log file text.

Layman answer but have you tried stopping and restarting Core again? Perhaps the GUI (it sounds like you're using that and not bitcoind) froze while it was synchronizing and instead of downloading blocks, it's busy swapping memory to and from the disk.

Check your memory usage, and also if you see any spikes of network activity using Task Manager or iftop. Bitcoin's block downloads are in concentrated spikes so if you don't see any of those then it means that something's wrong with your network and it's not receiving blocks or transactions.

For the last 9 days my computer is trying to update blocks; I can see 18 active connections to Bitcoin Network, but my machine is stuck at 95.54% ...
Any suggestion on how to force it to update itself to the current date?