forked from erigontech/erigon
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archive Node is never up to date. #217
Comments
It seems you can't connect stable p2p node |
All our nodes end up this way, too. We're running v1.1.9 4b352f6 Generally, our nodes are always about 3 minutes behind. When new blocks come in, we catch up almost immediately. Then it's a waiting game again for about 3 minutes. We run with the following:
Peers:
|
Use the latest commit in devel branch. #234 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Erigon version: 1.1.9-dev-4b352f69
OS & Version: Ubuntu 22.04
Commit hash: 4b352f6
Erigon Command (with flags/config):
./build/bin/erigon --sentry.drop-useless-peers --p2p.protocol=66 --txpool.disable --metrics.addr=0.0.0.0 --log.console.verbosity=dbug --db.pagesize=16k --datadir=mainnet --chain=bsc --port=30305 --http.addr=0.0.0.0 --http.port=8546 --authrpc.port=8552 --torrent.port=42070 --private.api.addr=127.0.0.1:9095 --pruning=archive --http --ws --http.api=eth,debug,net,trace,web3,erigon,txpool
Concensus Layer: N/A
Concensus Layer Command (with flags/config): N/A
Chain/Network: BSC
Expected behaviour
Always up to date with the latest block
Actual behaviour
always a few minutes behind by 15+ blocks
Steps to reproduce the behaviour
Sync from snapshot found here https://github.com/48Club/bsc-snapshots
The text was updated successfully, but these errors were encountered: