Bitcoin Core software stuck, need help

[crypto_Madmax]

Hello,

 its been a long time since I wanted to have my own full Bitcoin node, never tried before, so looked it up online the minimum hardware requirements, and found that a somewhat older Mac mini that I had as spare would work just fine, plus added 512gb SSD drive.

 Decided to do a fresh OS X re-Install since this would be a dedicated full node,

 Next I downloaded Bitcoin Core v20, installed and run.

 At first the Sync looks faster than I expected, after all I have a dedicated 1gbps up/down fiber link. after few minutes it stops at 2.81% progress and its been the same for 3 days.

  Anyways, tough the software was unresponsive so decided to reinstall Bitcoin core byremoving the Bitcoin core software and reinstalling, it seems that the data still remains and always start the process from 2.81% progress. therefore decided to reformat the hard drive and reinstall OS X and Bitcoin core software. the same thing is happening right now, after few minutes it stops at 2.81% syncing progress and stayed like it for a couple of days now.

Is there a bug on this version of the software for Mac ?

how to bypass this 2.81% stuck ? almost makes me think that there is a corrupt data in the block around 2.81%.

 Please help!

thank you,

Please see Screen Shot below

https://prnt.sc/u6zw4l

[1715297350]

1715297350

[1715297350]

1715297350

[BitMaxz]

Can you try to turn off the modem/internet and then turn on, after that try to reopen the bitcoin core again.

If it doesn't work try to change your Mac DNS to Google DNS 8.8.8.8 and 8.8.4.4.


If still doesn't work take and copy the text on the debug.log and paste it here
You can find it under "~/.bitcoin"

[crypto_Madmax]

thanks for the reply, since the file is too large I am going to paste the last part of it. witch I believe it could tell what the problem is.

2020-08-27T18:50:53Z Peer=25414 is stalling block download, disconnecting
2020-08-27T18:50:56Z Peer=25415 is stalling block download, disconnecting
2020-08-27T18:50:58Z Peer=25416 is stalling block download, disconnecting
2020-08-27T18:51:05Z New outbound peer connected: version: 70015, blocks=645577, peer=25418 (full-relay)
2020-08-27T18:51:05Z New outbound peer connected: version: 70015, blocks=645577, peer=25419 (full-relay)
2020-08-27T18:51:07Z Peer=25417 is stalling block download, disconnecting
2020-08-27T18:51:09Z Peer=25418 is stalling block download, disconnecting
2020-08-27T18:51:11Z New outbound peer connected: version: 70015, blocks=645577, peer=25420 (full-relay)
2020-08-27T18:51:12Z New outbound peer connected: version: 70015, blocks=645577, peer=25421 (full-relay)
2020-08-27T18:51:13Z Peer=25419 is stalling block download, disconnecting
2020-08-27T18:51:16Z Peer=25420 is stalling block download, disconnecting
2020-08-27T18:51:43Z New outbound peer connected: version: 70015, blocks=645577, peer=25422 (full-relay)
2020-08-27T18:51:44Z New outbound peer connected: version: 70015, blocks=645577, peer=25423 (full-relay)
2020-08-27T18:51:45Z New outbound peer connected: version: 70015, blocks=645577, peer=25424 (full-relay)
2020-08-27T18:51:45Z New outbound peer connected: version: 70015, blocks=645577, peer=25425 (full-relay)
2020-08-27T18:51:46Z New outbound peer connected: version: 70015, blocks=645577, peer=25426 (full-relay)
2020-08-27T18:51:47Z Peer=25422 is stalling block download, disconnecting
2020-08-27T18:51:47Z New outbound peer connected: version: 70015, blocks=645577, peer=25427 (full-relay)
2020-08-27T18:51:47Z New outbound peer connected: version: 70015, blocks=645577, peer=25428 (full-relay)
2020-08-27T18:51:49Z Peer=25423 is stalling block download, disconnecting
2020-08-27T18:51:51Z Peer=25424 is stalling block download, disconnecting
2020-08-27T18:51:53Z Peer=25425 is stalling block download, disconnecting
2020-08-27T18:51:53Z New outbound peer connected: version: 70015, blocks=645577, peer=25429 (full-relay)
2020-08-27T18:51:54Z New outbound peer connected: version: 70015, blocks=645577, peer=25430 (full-relay)
2020-08-27T18:51:55Z Peer=25426 is stalling block download, disconnecting
2020-08-27T18:51:57Z Peer=25427 is stalling block download, disconnecting
2020-08-27T18:52:00Z Peer=25428 is stalling block download, disconnecting
2020-08-27T18:52:02Z Peer=25429 is stalling block download, disconnecting
2020-08-27T18:52:06Z New outbound peer connected: version: 70015, blocks=645577, peer=25431 (full-relay)
2020-08-27T18:52:08Z Peer=25430 is stalling block download, disconnecting
2020-08-27T18:52:36Z New outbound peer connected: version: 70015, blocks=645577, peer=25432 (full-relay)
2020-08-27T18:52:38Z Peer=25431 is stalling block download, disconnecting
2020-08-27T18:52:54Z New outbound peer connected: version: 70015, blocks=645577, peer=25433 (full-relay)
2020-08-27T18:52:54Z New outbound peer connected: version: 70015, blocks=645577, peer=25434 (full-relay)

[BitMaxz]

~snip~

What I see here is that your peers keep disconnecting there might be something blocking Bitcoin core from downloading blocks that's why it keeps accepting new peers.

Try to do the first thing that I suggested above by rebooting the internet source/modem and then change the DNS.


If it doesn't work try what suggested from this post below.
- https://bitcointalk.org/index.php?topic=1666725.msg16738036#msg16738036

Let me ask another thing can you post the full specs of your mac here?


Just added this it worth reading and you can find few solutions there to fix this issue.
https://github.com/bitcoin/bitcoin/issues/11037
I don't know if this will work on Mainnet but worth trying.

[crypto_Madmax]

while I am shutting down Bitcoin core, here is my specs :

https://prnt.sc/u73bca

https://prnt.sc/u73dma

[crypto_Madmax]

rebooted router / restarted bitcoin core, deleted peers.data but still stalling 

2020-08-27T20:38:21Z New outbound peer connected: version: 70015, blocks=645589, peer=8 (full-relay)
2020-08-27T20:38:22Z Peer=5 is stalling block download, disconnecting
2020-08-27T20:38:24Z Peer=6 is stalling block download, disconnecting
2020-08-27T20:38:24Z New outbound peer connected: version: 70015, blocks=645589, peer=11 (full-relay)
2020-08-27T20:38:26Z Peer=7 is stalling block download, disconnecting
2020-08-27T20:38:28Z Peer=8 is stalling block download, disconnecting
2020-08-27T20:38:42Z New outbound peer connected: version: 70015, blocks=645589, peer=12 (full-relay)
2020-08-27T20:38:43Z New outbound peer connected: version: 70015, blocks=645589, peer=13 (full-relay)
2020-08-27T20:38:44Z Peer=11 is stalling block download, disconnecting
2020-08-27T20:38:45Z New outbound peer connected: version: 70015, blocks=645589, peer=14 (full-relay)
2020-08-27T20:38:46Z Peer=12 is stalling block download, disconnecting
2020-08-27T20:38:49Z Peer=13 is stalling block download, disconnecting
2020-08-27T20:39:09Z New outbound peer connected: version: 70015, blocks=645589, peer=16 (full-relay)
2020-08-27T20:39:11Z Peer=14 is stalling block download, disconnecting
2020-08-27T20:39:55Z New outbound peer connected: version: 70015, blocks=

[HCP]

The only similar issues I've seen were from 3 or 4 years ago... it seems that, for whatever reason, your connections to the peers are "stalling" and you're not receiving any blocks. You're possibly either connected to bad peers or something on your network is preventing the data from arriving.

You could try and set your -maxconnections=1 (on commandline) or in bitcoin.conf as maxconnections=1... so you connect to one peer to start with, so it has a longer time to respond and start sending data before the system disconnects it.

Once it has started syncing up a few blocks and you have made it past the 2.81%... you could try shutting down and starting again without the maxconnection limit and see if it is working OK.

[crypto_Madmax]

The only similar issues I've seen were from 3 or 4 years ago... it seems that, for whatever reason, your connections to the peers are "stalling" and you're not receiving any blocks. You're possibly either connected to bad peers or something on your network is preventing the data from arriving.

You could try and set your -maxconnections=1 (on commandline) or in bitcoin.conf as maxconnections=1... so you connect to one peer to start with, so it has a longer time to respond and start sending data before the system disconnects it.

Once it has started syncing up a few blocks and you have made it past the 2.81%... you could try shutting down and starting again without the maxconnection limit and see if it is working OK.

I will try this

[gmaxwell]

My best guess (and it's just a guess) is that you're being some kind of (national?, local?) firewall or anti-virus that is censoring or otherwise corrupting the transmission of a particular block.  Unfortunately, Bitcoin P2P is still not encrypted which makes it vulnerable to being screwed up by random censorware in the network.

Can you post what your current best block hash is?  It'll be the bestblockhash field in the getblockchaininfo output.

We could try getting you past that block by giving you a hex copy of it over https then you could submit it via the rpc.

If would also be useful to add logips=1 to the configuration so you can make sure that it's not connecting to the same peers over and over again (and we could try fetching the block in question from a peer that failed for you).

[DaveF]

My best guess (and it's just a guess) is that you're being some kind of (national?, local?) firewall or anti-virus that is censoring or otherwise corrupting the transmission of a particular block.  Unfortunately, Bitcoin P2P is still not encrypted which makes it vulnerable to being screwed up by random censorware in the network.

Can you post what your current best block hash is?  It'll be the bestblockhash field in the getblockchaininfo output.

We could try getting you past that block by giving you a hex copy of it over https then you could submit it via the rpc.

If would also be useful to add logips=1 to the configuration so you can make sure that it's not connecting to the same peers over and over again (and we could try fetching the block in question from a peer that failed for you).

If you don't mind revealing it, where are you located and who is your provider?
Might help to see if others in that area / on that provider are also having issues.

Same note, do you have another machine you can test with? You don't even have to download the entire blockchain, just have it on the same network and get it past the point you are now on this machine.
Also never underestimate the possibility of bad hardware causing strange issues.

-Dave