-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
My node is so slowly syncs!!! #980
Comments
|
hi, if I restart the node it is catching... but there is something I noticed: if I start send requests to the node I starting to lose sync... this is ridiculous... how do I solve this problem? thank you |
could you provide more details or screenshot? |
hi, If I send the requests over as WS or HTTP , the node falling behind... if I stop sending request I don't have sync problem. I guess, this is happening due to request limits. this happened after the 1.1.11 release... also my machine cpu & ram load that's like: |
Sorry for missing that, have you fixed this issue ? |
Me too |
My node has the same problem. It was fine for months, and one week ago it started to falling behind the current block (10-60 min behind). I updated geth-bsc to the latest release, started for a fresh snapshot, but the difficulty persisted. I have several other nodes (fantom, eth, avax) running on the same computer and everything work well. |
closing due to inactivity |
Hello everyone,
my node so slowly sync after last release.
my starter parameter
./geth --config xxxconfig.toml --datadir xxx --metrics --pprof --pprof.addr 0.0.0.0 --maxpeers 1000 --cache 18000 --http --http.addr 0.0.0.0 --http.port xxx --http.corsdomain "*" --ws --ws.origins="*" --ws.addr 0.0.0.0 --allow-insecure-unlock --diffsync --rpc.allow-unprotected-txs --txlookuplimit 0 --snapshot=false --rpcvhosts=*
what is the problem?
what can I do for solve this subject?
thank you
The text was updated successfully, but these errors were encountered: