bsc node not syncing after version release of 1.5.12

[dipuyadav]

our bsc nodes were working fine from last few months but suddenly all got stopped. we regularly keep updating the nodes to latest versions. But this time it is not syncing and showing the below error.

lvl=warn msg="Synchronisation failed, dropping peer" peer=85fd4b8d1ca2eedd1ca18d2bb17a9fc55ab92f9e0e1eb83223aa6137765acfd6 name=Geth/v1.5.12-d60167c... td=96987006 err="retrieved hash chain is invalid: invalid gas used (remote: 10898586 local: 10898653)"
t=2025-04-29T17:18:38+0800 lvl=info msg="Looking for peers" peercount=0 tried=71 static=0

what should we do ?

[kosdp]

experiencing same error

[EthanBlockson]

same

t=2025-04-29T14:29:12+0000 lvl=info msg="Importing sidechain segment" start=48773577 end=48775223
t=2025-04-29T14:29:13+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=a0b1369dd7374c44125288f9318c3312396f1d3c4891b6a85f25c512d9a054da name=Geth/v1.5.12-94e8217... td=97011710 err="retrieved hash chain is invalid: pruned ancestor"
t=2025-04-29T14:29:17+0000 lvl=warn msg="find a too slow peer" id=6517c138905e3bf355a7e13fbb385f4d0e0dbf9dd943049816b52be5a4d6fcf3 peer=44.201.162.2:55128 latency=867
t=2025-04-29T14:29:20+0000 lvl=warn msg="find a too slow peer" id=62b255d111cf9b074fca7de2dbf8091ff7dc0926a4d1bd85307c0d0965c9f585 peer=38.145.199.6:30311 latency=975
t=2025-04-29T14:30:45+0000 lvl=warn msg="find a too slow peer" id=7e7c9b640229e0bbe614b7b6b2c7b91ec543c339f857cafa3f594eaa57dea79b peer=223.72.35.107:34294 latency=4255
t=2025-04-29T14:30:48+0000 lvl=info msg="Importing sidechain segment" start=48773577 end=48775253
t=2025-04-29T14:30:48+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=f702fc575695b05ecc5665a564a87d35f8815d23af610909772a9b676f60da17 name=Geth/v1.5.11-5735d8a... td=97011844 err="retrieved hash chain is invalid: pruned ancestor"
t=2025-04-29T14:31:04+0000 lvl=warn msg="find a too slow peer" id=213df79c510d41e06a7616d5623229c903971dbdbd675f7d40a54210801343fc peer=3.93.212.175:55128 latency=552
t=2025-04-29T14:31:04+0000 lvl=warn msg="find a too slow peer" id=76006edd06084367c58a982e7400cae9687b862ffd548e432a87e2da4c5b8387 peer=47.243.57.58:53224 latency=799
t=2025-04-29T14:31:14+0000 lvl=warn msg="find a too slow peer" id=bf97616945cdff00e8b09580667bd4f3d0bc0be0eeda138f56410e13c97a82b0 peer=208.91.109.78:30303 latency=672

[zzzckck]

Hi @dipuyadav @kosdp @EthanBlockson may I know more about your issue?

• which bsc-snapshot did you use? Is it based the fast snapshot provided by 48club?
• did you run your node with: --tries-verify-mode none ?
• did you upgrade your node to v1.5.12 before the Lorentz hard fork or after the Lorentz hard fork?

[EthanBlockson]

• ive started from 48Club snapshot few months ago, so yes it was, but i was fully synced and running before hard fork
• yes
• upgraded to v1.5.12 after Lorentz hard fork, ±8 hrs later (but ive been running on pre <1.5.x which i installed to be ready for Lorentz, didnt know that one more geth update will be required)

sorry didnt have much time trying to solve it out, so restarted from scratch using 48Club snapshot again, now syncing

i think the problem is in corruption of database, nearly at hard fork block, that prevent node from syncing forward

[emailtovamos]

@dipuyadav
Which version were you using at the time of hardfork (2025-04-29 05:05:00 AM UTC)?
If it is an older version, then that would have lead to consensus mismatch between your node and peers leading to syncing failure.

[B1Q]

what's the solution? have to resync?

[zzzckck]

what's the solution? have to resync?
@B1Q you can have a try to rewind a few block, as the hard fork is on block: 48773576(0x2E839C8), you may try to rewind 8 blocks, by setHead to 0x2E839C0.

geth --exec "debug.setHead('0x2E839C0')" attach  <datadir>/geth.ipc

[zzzckck]

@emailtovamos better if BSC can automatically to the previous block and sync again.

[h6dworker]

I've been reading these issues, but I'm still not fully understanding the situation. In my case, the eth.syncing command continues to return a response without ever returning false. However, interestingly, I was able to make transactions from some of my nodes.

Here are the details of my nodes:

• Using BNB Chain nodes with Geth version v1.5.12
• Operating multiple nodes, and despite having the same configuration, some nodes can send transactions while others cannot
• All nodes have the --history.transactions 0 flag set

I seem to be facing similar issues as other users, but I'm puzzled by the fact that some of my nodes can still make transactions. I would appreciate any recommended settings or procedures to resolve this issue.

[emailtovamos]

Hi @h6dworker ,
Just to be clear, you are getting the Synchronisation failed, dropping peer error on all your nodes ? Or on only the ones that can't make transactions?

[h6dworker]

Thank you for your question.@emailtovamos
I don't see the "Synchronisation failed, dropping peer" error message in any of my nodes. All nodes (both those that can and cannot make transactions) only show the following messages:

"Failed to decode block body" warnings (occurring in the specific block range 48634055-48634070)
"Indexed transactions" messages (tx=0, tail=48634071)
Normal block synchronization with "Imported new chain segment"

All nodes appear to be synchronizing new blocks properly, and there don't seem to be any issues with that process.

[emailtovamos]

Hi @h6dworker ,

There have been 2 points to tackle the original issue which have been discussed in this thread:

1. Manual resetting of the local head: geth --exec "debug.setHead('0x2E839C0')" attach <datadir>/geth.ipc
2. Simply restarting from scratch

Let us know if you still get the not syncing error even after doing any of the above.

If you are encountering something different (as it seems by your mention of syncing Nodes being able to make transactions), then I encourage you to create another issue with details on what you are encountering and how to reproduce your issue so that it will be easier to keep track of it and work on fixing it.