-
Notifications
You must be signed in to change notification settings - Fork 45
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
WARN logs #245
Comments
These are warning msg. Pls keep it running for some time and see how the progress is. |
Show your rpc commad |
I tried some requests looking causing the error : Request to my node :
Response is :
Same request to differents external providers :
We can see that there is some differences in the transactions list. So my node looks to have incorrect datas. Is there a way to "repair" it ? |
My dev node is same as the later one. You have the incorrect datas. |
Thanks @blxdyx for the answer. Do you know how many time my node will be unavailable for the stage_headers reset ? |
Sorry to hear that. But it's the faster way to fix this problem. I tried several times. First, stop the node. Then run this command as a background process. It will take hours, don't interrupt it before it's finish. Most time it fix in my local machine. |
@blxdyx I just tried to do the reset, but I have this error :
|
this bug fixed in latest commit in devel branch. #262 |
@blxdyx the process just finished, but the response is still the same (first response in my initial message), so not correct. Any other idea ? |
You snapshots are broken. You can delete all the snapshots and download from here: https://github.com/bnb-chain/bsc-snapshots#erigon_snapshots_20231130tarlz4 |
It worked, thanks ! |
System information
Erigon version:
erigon version 1.1.9-dev-4b352f69
OS & Version: Linux
Commit hash:
Erigon Command (with flags/config):
erigon --rpc.batch.limit=10000 --datadir=/data/erigon/ --private.api.addr=0.0.0.0:9090 --chain bsc --http.addr=0.0.0.0 --http.vhosts=* --http.corsdomain=* --http.api=eth,erigon,web3,net,debug,trace,txpool --db.pagesize=16kb --maxpeers=1000 --p2p.protocol=66 --torrent.download.rate=100mb --bodies.cache=214748364800 --batchSize=4096M --sentry.drop-useless-peers --db.size.limit 8TB
Chain/Network: BSC
Actual behaviour
I have this kind of logs spamming :
My node looks responding properly, but I have these logs spamming.
The text was updated successfully, but these errors were encountered: