Skip to content

Add Peer Using Holesky Testnet #30607

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

Closed
Jinwon-Dev opened this issue Oct 16, 2024 · 5 comments
Closed

Add Peer Using Holesky Testnet #30607

Jinwon-Dev opened this issue Oct 16, 2024 · 5 comments

Comments

@Jinwon-Dev
Copy link

Jinwon-Dev commented Oct 16, 2024

Hi, I built 3 nodes on 3 different servers using geth and holesky testnet.

After that, for interworking with each other, after finding the enode value with "admin.nodeInfo.enode", I try to connect the nodes through the "admin.addPeer()" command, but when I input it, "true" is output, but when I check with "admin.peers" on other nodes, it cannot be confirmed.

The same Genesis block was used, and the network id was the same and all environments were the same.

All ports, firewalls, ip, etc. between each other are open.

If I use holesky testnet, can only the nodes that have already been determined be connected as peers in dns list, and can't the nodes that I built customly be connected?

Plz help me 😭

@MariusVanDerWijden
Copy link
Member

You can use debug.vmodule("p2p=5") in the console to increase the debug level for the network and see why the nodes are refusing to connect (look for staticdial)

@Jinwon-Dev
Copy link
Author

Jinwon-Dev commented Oct 16, 2024

INFO [10-16|18:30:01.771] Chain head was updated                   number=2,544,011 hash=48f3e4..5f48bb root=78f5be..794ce9 elapsed=3.49548ms
TRACE[10-16|18:30:08.875] Dial error                               id=60154aefbc2ee184 addr=59.31.206.161:30303                 conn=staticdial err="i/o timeout"
INFO [10-16|18:30:13.210] Imported new potential chain segment     number=2,544,012 hash=0088a2..230542 blocks=1         txs=46         mgas=10.079  elapsed=105.080ms   mgasps=95.913  snapdiffs=3.34MiB    triediffs=61.24MiB  triedirty=50.03MiB
DEBUG[10-16|18:30:13.452] Resolved node                            id=60154aefbc2ee184 addr=59.31.206.161:30303
INFO [10-16|18:30:13.610] Chain head was updated                   number=2,544,012 hash=0088a2..230542 root=1f5e83..bf385a elapsed=4.288667ms
TRACE[10-16|18:30:15.347] Dial error                               id=16eb476dd1fe4f21 addr=59.31.206.161:30303                 conn=staticdial err="i/o timeout"
TRACE[10-16|18:30:15.347] Starting p2p dial                        id=5706d02337594e72 ip=59.31.206.161   flag=staticdial
INFO [10-16|18:30:25.478] Imported new potential chain segment     number=2,544,013 hash=b78987..aff0a9 blocks=1         txs=75         mgas=18.761  elapsed=122.257ms   mgasps=153.452 snapdiffs=3.35MiB    triediffs=61.45MiB  triedirty=50.12MiB
INFO [10-16|18:30:25.824] Chain head was updated                   number=2,544,013 hash=b78987..aff0a9 root=8a66c4..9cdb7f elapsed=4.849268ms
TRACE[10-16|18:30:28.453] Dial error                               id=60154aefbc2ee184 addr=59.31.206.161:30303                 conn=staticdial err="i/o timeout"
TRACE[10-16|18:30:28.453] Starting p2p dial                        id=b9242c01f38bd105 ip=65.109.97.47    flag=dyndial
TRACE[10-16|18:30:29.025] Failed p2p handshake                     id=b9242c01f38bd105 addr=65.109.97.47:30303 conn=dyndial err="too many peers"
TRACE[10-16|18:30:29.025] Starting p2p dial                        id=60154aefbc2ee184 ip=59.31.206.161   flag=staticdial
TRACE[10-16|18:30:30.348] Dial error                               id=5706d02337594e72 addr=59.31.206.161:30303                 conn=staticdial err="i/o timeout"
INFO [10-16|18:30:37.924] Imported new potential chain segment     number=2,544,014 hash=d2554f..88949b blocks=1         txs=47         mgas=10.810  elapsed=112.852ms   mgasps=95.792  snapdiffs=3.36MiB    triediffs=61.53MiB  triedirty=50.22MiB
INFO [10-16|18:30:38.203] Chain head was updated                   number=2,544,014 hash=d2554f..88949b root=d314f0..e83b8d elapsed=4.033088ms
DEBUG[10-16|18:30:39.244] Resolved node                            id=5706d02337594e72 addr=59.31.206.161:30303
TRACE[10-16|18:30:44.026] Dial error                               id=60154aefbc2ee184 addr=59.31.206.161:30303                 conn=staticdial err="i/o timeout"
TRACE[10-16|18:30:44.026] Starting p2p dial                        id=16eb476dd1fe4f21 ip=59.31.206.161   flag=staticdial
INFO [10-16|18:30:49.341] Imported new potential chain segment     number=2,544,015 hash=1ad830..ca23c7 blocks=1         txs=78         mgas=16.374  elapsed=126.235ms   mgasps=129.708 snapdiffs=3.38MiB    triediffs=61.49MiB  triedirty=50.42MiB
INFO [10-16|18:30:49.696] Chain head was updated                   number=2,544,015 hash=1ad830..ca23c7 root=39f9cf..49286a elapsed=5.220629ms
TRACE[10-16|18:30:54.245] Dial error                               id=5706d02337594e72 addr=59.31.206.161:30303                 conn=staticdial err="i/o timeout"
TRACE[10-16|18:30:54.245] Starting p2p dial                        id=5706d02337594e72 ip=59.31.206.161   flag=staticdial`

There are "i/o timeout" error. what should I do? Is it related to the network?
😭

@Jinwon-Dev
Copy link
Author

also, these errors found.

TRACE[10-16|18:49:45.321] Failed p2p handshake id=3781021005775b43 addr=18.184.232.202:31005 conn=dyndial err="too many peers" TRACE[10-16|18:49:45.322] Discarding dial candidate id=9a4302864752ac58 ip=194.33.40.130 reason="already connected" TRACE[10-16|18:49:45.322] Starting p2p dial id=ed29a73f5eb74971 ip=18.203.116.239 flag=dyndial TRACE[10-16|18:49:48.069] Failed RLPx handshake addr=18.203.116.239:30303 conn=dyndial err=EOF TRACE[10-16|18:49:48.069] Starting p2p dial id=16eb476dd1fe4f21 ip=59.31.206.161 flag=staticdial INFO [10-16|18:49:49.211] Imported new potential chain segment number=2,544,103 hash=e017de..5a3bee blocks=1 txs=29 mgas=7.846 elapsed=99.752ms mgasps=78.658 snapdiffs=4.51MiB triediffs=66.30MiB triedirty=61.43MiB INFO [10-16|18:49:49.698] Chain head was updated number=2,544,103 hash=e017de..5a3bee root=db8b69..6b1fcf elapsed=3.456489ms DEBUG[10-16|18:49:55.847] Couldn't get external IP err="no UPnP or NAT-PMP router discovered" interface="UPnP or NAT-PMP" TRACE[10-16|18:49:55.848] Attempting port mapping proto=TCP extport=30303 intport=30303 interface="UPnP or NAT-PMP" DEBUG[10-16|18:49:55.848] Couldn't add port mapping proto=TCP extport=30303 intport=30303 interface="UPnP or NAT-PMP" err="no UPnP or NAT-PMP router discovered" TRACE[10-16|18:49:55.848] Attempting port mapping proto=UDP extport=30303 intport=30303 interface="UPnP or NAT-PMP" DEBUG[10-16|18:49:55.848] Couldn't add port mapping proto=UDP extport=30303 intport=30303 interface="UPnP or NAT-PMP" err="no UPnP or NAT-PMP router discovered" TRACE[10-16|18:49:57.165] Dial error id=60154aefbc2ee184 addr=59.31.206.161:30303 conn=staticdial err="i/o timeout" DEBUG[10-16|18:50:02.676] Resolved node id=60154aefbc2ee184 addr=59.31.206.161:30303 TRACE[10-16|18:50:03.070] Dial error id=16eb476dd1fe4f21 addr=59.31.206.161:30303 conn=staticdial err="i/o timeout" DEBUG[10-16|18:50:08.079] Resolved node id=16eb476dd1fe4f21 addr=59.31.206.161:30303 INFO [10-16|18:50:15.674] Imported new potential chain segment number=2,544,104 hash=0beae9..b4ed91 blocks=1 txs=13 mgas=1.027 elapsed=93.127ms mgasps=11.031 snapdiffs=4.51MiB triediffs=65.76MiB triedirty=61.59MiB INFO [10-16|18:50:16.025] Chain head was updated number=2,544,104 hash=0beae9..b4ed91 root=016679..ebc01d elapsed=3.262281ms TRACE[10-16|18:50:17.677] Dial error id=60154aefbc2ee184 addr=59.31.206.161:30303 conn=staticdial err="i/o timeout" TRACE[10-16|18:50:17.677] Starting p2p dial id=5706d02337594e72 ip=59.31.206.161 flag=staticdial TRACE[10-16|18:50:23.080] Dial error id=16eb476dd1fe4f21 addr=59.31.206.161:30303 conn=staticdial err="i/o timeout" TRACE[10-16|18:50:23.080] Starting p2p dial id=16eb476dd1fe4f21 ip=59.31.206.161 flag=staticdial

@MariusVanDerWijden
Copy link
Member

Hmm maybe @fjl knows why we get i/o timeout errors on staticdial?

@fjl
Copy link
Contributor

fjl commented Apr 3, 2025

The log messages about timeout just mean it cannot reach the node on the IP/port that it announces. This can be a firewall issue, or just a slow network.

@fjl fjl closed this as completed Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants
@fjl @gballet @MariusVanDerWijden @Jinwon-Dev and others