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

Testnet Node Unable to Find Peers #52

Open
andreclaro opened this issue Nov 7, 2024 · 6 comments
Open

Testnet Node Unable to Find Peers #52

andreclaro opened this issue Nov 7, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@andreclaro
Copy link

andreclaro commented Nov 7, 2024

Description

Our testnet node is sometimes unable to find peers and we are observing that issue again now.

Logs

besu[942757]: 2024-11-07 11:33:32.714+00:00 | EthScheduler-Timer-0 | INFO  | FullSyncTargetManager | Unable to find sync target. Waiting for 1 peers minimum. Currently checking 0 peers for usefulness

Versions

https://github.com/Consensys/linea-besu/releases/tag/24.11-delivery37

We build the software from source.

Config

config.toml:

# data
data-path="/var/lib/linea/data/execution/besu"
# Sync mode and data layer implementation
sync-mode="FAST"
data-storage-format="FOREST"
# genesis file
genesis-file="/var/lib/linea/data/execution/genesis.json"
# Boot nodes
bootnodes = ["enode://[6f20afbe4397e51b717a7c1ad3095e79aee48c835eebd9237a3e8a16951ade1fe0e66e981e30ea269849fcb6ba03d838da37f524fabd2a557474194a2e2604fa@18.221.100.27](mailto:6f20afbe4397e51b717a7c1ad3095e79aee48c835eebd9237a3e8a16951ade1fe0e66e981e30ea269849fcb6ba03d838da37f524fabd2a557474194a2e2604fa@18.221.100.27):31002","enode://[ce1e0d8e0500cb5c0ac56bdcdafb2d6320c3a2c5125b5ccf12f5dfc9b47ee74acbcafc32559017613136c9c36a0ce74ba4f83b7fb8244f099f3b15708d9d3129@3.23.75.47](mailto:ce1e0d8e0500cb5c0ac56bdcdafb2d6320c3a2c5125b5ccf12f5dfc9b47ee74acbcafc32559017613136c9c36a0ce74ba4f83b7fb8244f099f3b15708d9d3129@3.23.75.47):31000","enode://[1b026a5eb0ae74300f58987d235ef0e3a550df963345cb3574be3b0b54378bd11f14dfd515a8976f2c2d2826090e9507b8ccc24f896a9ffffffcabcfd996a733@3.129.120.128](mailto:1b026a5eb0ae74300f58987d235ef0e3a550df963345cb3574be3b0b54378bd11f14dfd515a8976f2c2d2826090e9507b8ccc24f896a9ffffffcabcfd996a733@3.129.120.128):31001"]
# Min gas price
min-gas-price=1000
# Host white list
host-whitelist=["*"]
# rpc
rpc-http-enabled=true
rpc-http-host="0.0.0.0"
rpc-http-port=8545
rpc-http-api=["ADMIN","NET","ETH","WEB3","TXPOOL"]
rpc-http-cors-origins=["all"]
rpc-http-max-active-connections=20000
# ws
rpc-ws-enabled=true
rpc-ws-api=["NET","ETH","WEB3"]
rpc-ws-host="0.0.0.0"
rpc-ws-port=8546
# p2p
p2p-port=30303
fast-sync-min-peers=1
Xeth-capability-max=67
# metrics
metrics-enabled=true
metrics-host="0.0.0.0"
metrics-port=6060
# Plugin Configuration
plugins=["L1FinalizationTagUpdaterPlugin"]
# L1FinalizationTagUpdaterPlugin
plugin-linea-l1-smart-contract-address="0xB218f8A4Bc926cF1cA7b3423c154a0D627Bdb7E5"
plugin-linea-l1-rpc-endpoint="http://ENDPOINT_L1"
@andreclaro andreclaro added the bug Something isn't working label Nov 7, 2024
@andreclaro
Copy link
Author

Restart solved the issue! But I think there is something that can be improved on the client to avoid restarting the client.

@andreclaro
Copy link
Author

andreclaro commented Nov 7, 2024

This is happening again and again... and the restart does not always solve the issue.

@andreclaro
Copy link
Author

we are using the following bootnodes:
- "enode://6f20afbe4397e51b717a7c1ad3095e79aee48c835eebd9237a3e8a16951ade1fe0e66e981e30ea269849fcb6ba03d838da37f524fabd2a557474194a2e2604fa@18.221.100.27:31002"
- "enode://ce1e0d8e0500cb5c0ac56bdcdafb2d6320c3a2c5125b5ccf12f5dfc9b47ee74acbcafc32559017613136c9c36a0ce74ba4f83b7fb8244f099f3b15708d9d3129@3.23.75.47:31000"
- "enode://1b026a5eb0ae74300f58987d235ef0e3a550df963345cb3574be3b0b54378bd11f14dfd515a8976f2c2d2826090e9507b8ccc24f896a9ffffffcabcfd996a733@3.129.120.128:31001"

@andreclaro
Copy link
Author

Do you have new or more bootnodes for testnet?

https://docs.linea.build/developers/guides/run-a-node/bootnodes

@andreclaro
Copy link
Author

Our node is still unable to find peers...

@andreclaro
Copy link
Author

andreclaro commented Nov 8, 2024

The node was able to recovered by itself.

Anyway, support asked me to try to change sync-mode from FAST to SNAP and "If it works, I believe the issue was that your node already had some blockchain data stored locally, which prevented FAST sync from being enabled — it fell back to full sync. You can either sync using SNAP or clear your local blockchain data then restart your node using FAST. " - I did not try this. I will give it a try if the issue happens again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant