Subject: BSC Node Syncing Issue – Current Block Ahead of Highest Block

[osizadmin]

I am experiencing an issue with my Binance Smart Chain (BSC) full node while syncing. Below are the details of my setup and the issue encountered:

System Information
Geth version: Geth/v1.4.16-2df94c37-20241125/linux-amd64/go1.21.13
OS & Version: Linux (Ubuntu 22.04)
Commit hash: (if applicable)

Expected Behaviour
The node should sync properly, with the currentBlock value progressing until it matches the highestBlock.

Actual Behaviour
The currentBlock is ahead of the highestBlock, which is causing an unexpected sync state.

Command Output:

eth.syncing.highestBlock - eth.syncing.currentBlock
-120
Syncing Details:

{
currentBlock: 46012765,
highestBlock: 46012644,
startingBlock: 46012642,
syncedAccounts: 0,
txIndexFinishedBlocks: 603136,
txIndexRemainingBlocks: 45409630
}

Steps to Reproduce the Behaviour

restarted bnb core

Observed the block difference using eth.syncing.
Checked peer count with admin.peers.length (90 peers connected).

Also we are facing this error: InvalidResponseError: Returned error: transaction indexing is in progress

[osizadmin]

Now:

{
currentBlock: 46018991,
healedBytecodeBytes: 0,
healedBytecodes: 0,
healedTrienodeBytes: 0,
healedTrienodes: 0,
healingBytecode: 0,
healingTrienodes: 0,
highestBlock: 46016654,
startingBlock: 46016653,
syncedAccountBytes: 0,
syncedAccounts: 0,
syncedBytecodeBytes: 0,
syncedBytecodes: 0,
syncedStorage: 0,
syncedStorageBytes: 0,
txIndexFinishedBlocks: 609362,
txIndexRemainingBlocks: 45409630
}

eth.syncing.highestBlock - eth.syncing.currentBlock
-2341
eth.syncing.highestBlock - eth.syncing.currentBlock
-2367

Also we are facing this error: InvalidResponseError: Returned error: transaction indexing is in progress

[STdevK]

@osizadmin what's your node start up command?

[osizadmin]

node start up command:

./opt/bsc/geth_linux --cache=16000 --config /opt/bsc/config.toml --datadir /opt/bsc/node --rpc.allow-unprotected-txs --http --maxpeers=500 --ws --syncmode=snap --history.transactions=0 --allow-insecure-unlock --tries-verify-mode=none --db.engine=pebble