snapshot stale RPC errors #3270
Description
Hello,
We're seeing some amount of RPC eth_call errors on Mainnet with following error messages
{"code":-32000,"message":"getStateObject (fffffffffffffffffffffffffffffffffffffffe) error: snapshot stale"}
{"code":-32000,"message":"snapshot stale"}
I've noticed these errors at least from late May 2025, but it may appear earlier.
bsc:1.5.19, cli args are following
--config=/config/config.toml
--datadir=/data
--syncmode=full
--gcmode=full
--maxpeers=99
--cache=8000
--snapshot=true
--port=30311
--rpc.allow-unprotected-txs
--history.transactions=90000
--cache.preimages
--tries-verify-mode=none
--pruneancient=true
--nodiscover
--netrestrict=...
--metrics
--pprof
--pprof.addr=0.0.0.0
--pprof.port=6060
--state.scheme=path
--db.engine=pebble
--rpc.gascap=150000000
Full geth snapshot from 48club is used
What does this error mean ? How to debug it further ?
Metadata
Metadata
Assignees
Labels
No labels