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

dispersal/retrieval socket is UNREACHABLE #137

Open
nivshitrit opened this issue Jul 11, 2024 · 0 comments
Open

dispersal/retrieval socket is UNREACHABLE #137

nivshitrit opened this issue Jul 11, 2024 · 0 comments

Comments

@nivshitrit
Copy link

Issue Summary

After delegating 32 ankrETH to my operator, i then tried to run eigenDA
The logs look good, and on eigenDA i can see that my operator has opted in, but im getting the error that reachability check fails
i tried to curl into the dispersal & retrieval addresses from my own laptop to rule out access issues from my node, and even from my laptop i get a timeout for these addresses.

Environment

testnet

  • EigenDA version: 0.7.4
  • Operating System: alpine
  • Node configuration (if applicable):
  • Any specific settings or modifications:

Steps to Reproduce

  1. Leave all reachability values in .env as default values
    2.launch eigenDA

Expected Behavior

Reachability should be reached. curl into this address does work : https://dataapi-holesky.eigenda.xyz/api/v1/operators-info/port-check?operator_id=8634db3ba195738e2bff9fe7bc23b7ec3c7b4f1c63e5ec128932a956d62d80fd

Actual Behavior

getting this in the logs:

DBG node/node.go:506 Calling reachability check component=Node url="https://dataapi-holesky.eigenda.xyz/api/v1/operators-info/port-check?operator_id=8634db3ba195738e2bff9fe7bc23b7ec3c7b4f1c63e5ec128932a956d62d80fd"

 ERR node/node.go:542 Reachability check - dispersal socket is UNREACHABLE component=Node socket=3.212.86.26:32005

ERR node/node.go:549 Reachability check - retrieval socket is UNREACHABLE component=Node socket=3.212.86.26:32004

Possible Solution

.

Additional Context

running the node in a k8s cluster, the node has other procesess that are able to reach the public web, so i dont think its a firewall/security group 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

No branches or pull requests

1 participant