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

Invalid name resolution #427

Closed
Exca-DK opened this issue Dec 31, 2023 · 1 comment · Fixed by #428
Closed

Invalid name resolution #427

Exca-DK opened this issue Dec 31, 2023 · 1 comment · Fixed by #428

Comments

@Exca-DK
Copy link

Exca-DK commented Dec 31, 2023

The example provided in the repository doesn't work. Containers are trying to hit mev-boost0 but the actual container is under mev-boost-0-lighthouse-geth--someuuid

Logs:

<cl-1-lighthouse-geth--d444f6707ab74652a7599604d1334849>
2023-12-31 17:17:39 Dec 31 16:17:39.012 WARN Relay error when registering validator(s), error: HttpClient(url: http://mev-boost0:18550/, kind: request, detail: error trying to connect: dns error: failed to lookup address information: Temporary failure in name resolution), num_registrations: 64

<cl-1-lighthouse-geth-validator--af56c146b5a84f9a88c9a2b7f12b5478>
2023-12-31 17:24:03 Dec 31 16:24:03.103 WARN Unable to publish validator registrations to the builder network, error: Some endpoints failed, num_failed: 1 http://172.16.0.11:4000/ => RequestFailed(ServerMessage(ErrorMessage { code: 500, message: "INTERNAL_SERVER_ERROR: HttpClient(url: http://mev-boost0:18550/, kind: request, detail: error trying to connect: dns error: failed to lookup address information: Temporary failure in name resolution)", stacktraces: [] })), service: preparation

<mev-boost-0-lighthouse-geth--4b2679276ab34b378ea0ab0416194f80>
2023-12-31 16:58:53 time="2023-12-31T15:58:53.316Z" level=info msg="starting mev-boost" version=v1.6
2023-12-31 16:58:53 time="2023-12-31T15:58:53.316Z" level=info msg="using genesis fork version: 0x10000038" version=v1.6
2023-12-31 16:58:53 time="2023-12-31T15:58:53.316Z" level=info msg="using 1 relays" version=v1.6
2023-12-31 16:58:53 time="2023-12-31T15:58:53.316Z" level=info msg="relay #1: http://0xa55c1285d84ba83a5ad26420cd5ad3091e49c55a813eee651cd467db38a8c8e63192f47955e9376f6b42f6d190571cb5@172.16.0.20:9062" version=v1.6
2023-12-31 16:58:53 time="2023-12-31T15:58:53.316Z" level=info msg="listening on 0.0.0.0:18550" version=v1.6

Network config

cmd:

$ kurtosis run --enclave my-testnet github.com/kurtosis-tech/ethereum-package "$(cat network_params.yaml)"
@Exca-DK
Copy link
Author

Exca-DK commented Jan 1, 2024

Seems that this pr broke the network

dif
- mev_boost_service_name = "{0}{1}".format(
+ mev_boost_service_name = "{0}-{1}-{2}-{3}".format(

but this formatting is unchanged for new behaviour.

@barnabasbusa barnabasbusa linked a pull request Jan 2, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant