Skip to content
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

Looking for peers with hundreds peercount #2362

Closed
daron4ever opened this issue Apr 1, 2024 · 10 comments
Closed

Looking for peers with hundreds peercount #2362

daron4ever opened this issue Apr 1, 2024 · 10 comments
Assignees

Comments

@daron4ever
Copy link

daron4ever commented Apr 1, 2024

System information

Geth version: v1.3.13
OS & Version: Linux
Commit hash : (if develop)

I have more than 300 peerCount and the block is not on the time sync becuse of "Looking for peers".
For eth.syncing: false

./geth_linux --config ./config.toml --datadir ./node --syncmode snap --cache 60000 --metrics --verbosity 3 --rpc.allow-unprotected-txs --history.transactions 0 --ws.origins "*" --rpc.txfeecap 0 --maxpeers 500 --ws --ws.api net,web3,eth,admin,debug --snapshot=false --pipecommit

Screenshot 2024-04-02 at 01 46 21

[backtrace]

When submitting logs: please submit them as text and not screenshots.

@STdevK
Copy link

STdevK commented Apr 2, 2024

Are you syncing the node with a snapshot? If yes, which snapshot did you use?

@weiihann
Copy link
Contributor

weiihann commented Apr 2, 2024

The log seems normal to me, what's the issue here?

The log Looking for peers could appear as your maximum number of dialed peers have not been reached yet, so it will continue to look for peers.

eth.syncing is false is normal behaviour, it means that your node is up to date and is currently not syncing.

@daron4ever
Copy link
Author

Are you syncing the node with a snapshot? If yes, which snapshot did you use?

I used snapshot last year so i dont remember exact version and maintain the sync with pruning.

@daron4ever
Copy link
Author

The log seems normal to me, what's the issue here?

The log Looking for peers could appear as your maximum number of dialed peers have not been reached yet, so it will continue to look for peers.

eth.syncing is false is normal behaviour, it means that your node is up to date and is currently not syncing.

The latest block is few block behind even eth.syicing is false. If you see the timestamp, it has a long latency with new block sync.

[ update]
After I tried to remove /geth/nodes and restart node, i didnt see any peerCount. it showed 0 peerCount.
So I added a staticnode and it sync well with the staticnode only.

However, I still dont see any peerCount. It is 1 peerCount now.

Screenshot 2024-04-02 at 15 37 21

@weiihann
Copy link
Contributor

weiihann commented Apr 2, 2024

Wait for a bit (1 or 2 hours) and see if the peer count increases. Do update us here again.

@daron4ever
Copy link
Author

Wait for a bit (1 or 2 hours) and see if the peer count increases. Do update us here again.

I still got 1 static peerCount.

@weiihann
Copy link
Contributor

weiihann commented Apr 3, 2024

It might be due to this:
image
Check the FAQ here.

Try creating a new nodekey file following the instruction and see if it works for you.

@weiihann weiihann self-assigned this Apr 3, 2024
@daron4ever
Copy link
Author

It might be due to this: image Check the FAQ here.

Try creating a new nodekey file following the instruction and see if it works for you.

Thanks. I removed nodekey but still 1 peerCount.

@weiihann
Copy link
Contributor

weiihann commented Apr 8, 2024

Then it might be caused by some P2P networking issues.

@daron4ever
Copy link
Author

Then it might be caused by some P2P networking issues.

peercount is coming back after i updated version v1.4.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants