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

fix: port-forward socat getaddrinfo: Name or service not known #44

Closed
andrewrynhard opened this issue Apr 3, 2018 · 0 comments · Fixed by #54
Closed

fix: port-forward socat getaddrinfo: Name or service not known #44

andrewrynhard opened this issue Apr 3, 2018 · 0 comments · Fixed by #54
Assignees
Milestone

Comments

@andrewrynhard
Copy link
Member

Terminal 1

kubectl port-forward etcd-master-0 2379:2379 -n kube-system
Forwarding from 127.0.0.1:2379 -> 2379

Terminal 2

curl localhost:2379/v2
curl: (52) Empty reply from server

Terminal 1

kubectl port-forward etcd-master-0 2379:2379 -n kube-system
Forwarding from 127.0.0.1:2379 -> 2379
Handling connection for 2379
E0402 21:26:31.026140   78292 portforward.go:331] an error occurred forwarding 2379 -> 2379: error forwarding port 2379 to pod 67354788607ba8b9caad4f69c7a4256581b46655281b6fd182ec0fd21ef0591c, uid : exit status 1: 2018/04/03 04:26:29 socat[11867] E getaddrinfo("localhost", "NULL", {1,2,1,6}, {}): Name or service not known
@andrewrynhard andrewrynhard added this to the v0.1.0 milestone Apr 3, 2018
@andrewrynhard andrewrynhard self-assigned this Apr 3, 2018
@andrewrynhard andrewrynhard modified the milestones: v0.1.0-alpha.16, v0.1 Jun 20, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant