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

Bad bootstrap node when running a localnet #847

Closed
mpaulucci opened this issue Oct 14, 2024 · 0 comments · Fixed by #987
Closed

Bad bootstrap node when running a localnet #847

mpaulucci opened this issue Oct 14, 2024 · 0 comments · Fixed by #987
Assignees
Labels
bug Something isn't working

Comments

@mpaulucci
Copy link
Collaborator

  INFO [10-14|16:20:38.926] Gasprice oracle is ignoring threshold set threshold=2
  WARN [10-14|16:20:38.926] Engine API enabled                       protocol=eth
  INFO [10-14|16:20:38.926] Starting peer-to-peer node               instance=Geth/v1.14.9-unstable-e9467eec-20240829/linux-arm64/go1.23.0
  Fatal: Error starting protocol stack: bad bootstrap node "enode://8e7f762ec60d6e63c2010fa68d041de02420a2d885a451351da996855358add14180cfe95024cb443528cc8ee4c487edc343ca1acd9a4253394509c11da21c40@0.0.0.0:30303": invalid IP (multicast/unspecified)
  Fatal: Error starting protocol stack: bad bootstrap node "enode://8e7f762ec60d6e63c2010fa68d041de02420a2d885a451351da996855358add14180cfe95024cb443528cc8ee4c487edc343ca1acd9a4253394509c11da21c40@0.0.0.0:30303": invalid IP (multicast/unspecified)

This can be reproduced when adding ethereum_rust as the first participant in the localnet:

participants:
  - el_type: ethereumrust
    cl_type: lighthouse
    count: 1
  - el_type: geth
    cl_type: lighthouse
    count: 1
@mpaulucci mpaulucci added the bug Something isn't working label Oct 14, 2024
@mpaulucci mpaulucci added this to the 4 - P2P Network milestone Oct 14, 2024
github-merge-queue bot pushed a commit that referenced this issue Oct 28, 2024
**Motivation**

Running in any position of the `network_params.yaml` except the last
generates an error for the following node when checking our enode url

**Description**

When setting up the `Node` struct, we were using `0.0.0.0` instead of
the actual ip, this PR maps `0.0.0.0` to the local ip there.
This force us to specify the IP of the node in case of using a public
one. The local IP is used due to it being the one needed in Kurtosis. If
this could be an issue for other common forms of running the Node
outside of the CI checks we'll need to go with a more complex solution
using nat for example.

Also if we prefer to not use a crate and obtain it by ourselves I could
go that path!

_Note regarding `tx_spammer`: Unfortunately `tx_spammer` is not working
as we expected, being the first node in the configuration file
completely removed transactions from the kurtosis run (no nodes have
them now), we need to create another issue and investigate that
further._

Resolves #847
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
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants