BSC testnet No block headers to write in this log period block number

[mikolajsobolewski]

System information

Erigon version: ./erigon --version erigon/v2.27.0-stable-6d8b304e/linux-amd64/go1.19.2

OS & Version: Linux

Commit hash : 6d8b304e

Expected behaviour

Syncing to the last block

Actual behaviour

A lot of messages and node not syncing

INFO] [10-11|09:53:23.708] [2/16 Headers] Inserting headers         progress=858177 queue=1
[INFO] [10-11|09:53:27.751] [parlia] snapshots build, gather headers block=900000
[INFO] [10-11|09:53:27.751] [parlia] snapshots build, recover from headers block=900000
[INFO] [10-11|09:53:37.469] [parlia] snapshots build, gather headers block=1000000
[INFO] [10-11|09:53:37.469] [parlia] snapshots build, recover from headers block=1000000
[INFO] [10-11|09:53:43.708] [2/16 Headers] Wrote block headers       number=1010003 blk/second=20471.350 alloc=204.1MB sys=1.6GB
[INFO] [10-11|09:54:03.708] [2/16 Headers] No block headers to write in this log period block number=1010003 blk/second=0.000
[INFO] [10-11|09:54:23.692] [p2p] GoodPeers                          eth66=1
[INFO] [10-11|09:54:23.697] [txpool] stat                            block=0 pending=0 baseFee=0 queued=0 alloc=208.4MB sys=1.6GB
[INFO] [10-11|09:54:23.708] [2/16 Headers] No block headers to write in this log period block number=1010003 blk/second=0.000
[INFO] [10-11|09:54:43.708] [2/16 Headers] No block headers to write in this log period block number=1010003 blk/second=0.000
[INFO] [10-11|09:55:03.707] [2/16 Headers] No block headers to write in this log period block number=1010003 blk/second=0.000
```

#### Steps to reproduce the behaviour
run with config ````erigon --chain=chapel --port=30303 --private.api.addr=127.0.0.1:9090 --http --http.addr=0.0.0.0 --http.vhosts=* --http.port=8545 --http.api=eth,debug,net,trace,web3,er
igon --snapshots=false --ws --datadir=/data````

[a26nine]

#5703

[PolarSyncZ]

I had this same issue, with a new node I was spinning up from snapshots. I tried all sorts of things and was finally able to resolve it by deleting all of the snapshot files and restarting erigon then letting them re-download and index etc. It took about 24 hours but it solved the issue and my node is now functioning normally.

[runatyr1]

I think this can be closed as duplicate to https://github.com/ledgerwatch/erigon/issues/5703

[github-actions[bot]]

This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.