1

I have bitcoin core version 25 and the blockchain is fully synchronized. Every 2-3 days I open up core to sync with the newest blocks. When i am syncing the newest blocks from the past few days the block just gets stuck randomly almost like core freezes. I don't get the spinning circle and if I quit core and reopen it the blocks end up syncing. It usually freezes two times before succesfully synching to most recent block. I used to be able to do this without it ever freezing like this.

What could be causing this issue?

I looked into the debug log. There is a part after the last block that synced it says the following: skipped DNS seeding, dnsseed thread exit. Imported mempool transactions from disk: 2876 succeeded, 359 failed, 0 already there, 0 waiting for installation broadcast. Does this help anyone?

This is the only thing I see In debug log after every freeze. Only thing that is different is number of failed or successes from disk.

Also important to note I have core running on an ssd and I had to switch the format from ExFAT to APFS after mac sonoma update a few months back. Not sure if that has anything to do with it.

Should I try redownloading most recent bitcoin core? Not sure what to do and this is making me not want to run a node at all...

Also if I have to start from scratch and delete core from sdd and start all over from genesis block am I safe to delete everything off sdd? I have everything on a hardware wallet so I'm not using core wallet.

Any assistance here from a pro would be greatly appreciated. I'm not a coder or computer science person so this is already cumbersome for me but I'm trying. I posted a few days ago but never got a resolution and this thread is a bit more detailed.

12
  • bitcoind (command-line) or bitcoin-qt (GUI)? Does it hang completely, or does it just not make progress syncing? Have you tried waiting, if so, for how long? Do you have any open connections to the network? Dec 30, 2023 at 17:40
  • @PieterWuille what do you mean by bitcoind or bitcoin qt? I am on version 25 looking at the debug log. I've tried waiting a few minutes but not long. I guess my thought process would be why wait any longer then a few minutes if all other blocks are syncing fast. As far as connection I usually have 10 or more connections looks like debug log shows connected to peers
    – John
    Dec 30, 2023 at 18:16
  • Sometimes a peer stalls, and it takes a few minutes for bitcoin core to decide to kick it and switch to another peer. Are you using the user interface (like, do you have a Bitcoin Core visual window you see), or the command line interface (as in on a terminal, in text mode)? Dec 30, 2023 at 18:23
  • 1
    Does this answer your question? Bitcoin core synchronizing gets stuck on block Dec 30, 2023 at 18:41
  • 1
    @PieterWuille waiting about 10min resolved the issue
    – John
    Dec 31, 2023 at 17:00

1 Answer 1

1

A node that is very close to the current chaintip (no more than 200 minutes behind the current chaintip) will immediately start downloading blocks.

Nodes that have fallen further behind from the current chaintip, will behave just like for initial synchronization. Such a node will first acquire descriptions of its peers’ best chaintips, then synchronize the block header chain from a single peer, and finally download the block data from multiple peers in parallel.

Since you say you only bring your node online every few days, you may have had bad luck with the first peer that you requested the block header chain from. If that peer is providing data slowly, it may seem like nothing is happening for a while.

As Pieter suggested in the comments on your question, just waiting a bit longer (10-20 minutes instead of one minute) will likely resolve any sort of issues with slow peers.

1
  • Extremely helpful, thank you!
    – John
    Jan 3 at 11:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.