kubectl: Unable to connect to the server: dial tcp i/o timeout #1234

norbert-yoimo · 2017-03-10T11:36:16Z

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report

Minikube version (use minikube version): minikube version: v0.17.1
Environment:

OS (e.g. from /etc/os-release): Arch linux
VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): virtualbox
ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): minikube-v1.0.7.iso
Install tools:
Others:

What happened:
$ ./minikube-linux-amd64 start

Starting local Kubernetes cluster...
Starting VM...
SSH-ing files into VM...
Setting up certs...
Starting cluster components...
Connecting to cluster...
Setting up kubeconfig...
Kubectl is now configured to use the cluster.

$ kubectl get pods

Unable to connect to the server: dial tcp 192.168.99.100:8443: i/o timeout

What you expected to happen:
Get an empty list of pods

How to reproduce it (as minimally and precisely as possible):

Anything else do we need to know:
Output of minikube ssh systemctl status localkube:

● localkube.service - Localkube
   Loaded: loaded (/lib/systemd/system/localkube.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2017-03-06 14:09:08 UTC; 14min ago
     Docs: https://github.com/kubernetes/minikube/tree/master/pkg/localkube
 Main PID: 3271 (localkube)
    Tasks: 16 (limit: 4915)
   Memory: 141.8M
      CPU: 1min 54.669s
   CGroup: /system.slice/localkube.service
           ├─3271 /usr/local/bin/localkube --generate-certs=false --logtostderr=true --enable-dns=false --node-ip=192.168.99.100 --apiserver-name=minikubeCA
           └─3350 journalctl -k -f

Mar 06 14:19:12 minikube localkube[3271]: I0306 14:19:12.296016    3271 replication_controller.go:322] Observed updated replication controller kubernetes-dashboard. Desired pod count change: 1->1
Mar 06 14:19:12 minikube localkube[3271]: I0306 14:19:12.296150    3271 replication_controller.go:322] Observed updated replication controller kube-dns-v20. Desired pod count change: 1->1
Mar 06 14:19:17 minikube localkube[3271]: I0306 14:19:17.895294    3271 operation_executor.go:917] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/8357ed5c-0276-11e7-9885-0800272e2447-default-token-77nfr" (spec.Name: "default-token-77nfr") pod "8357ed5c-0276-11e7-9885-0800272e2447" (UID: "8357ed5c-0276-11e7-9885-0800272e2447").
Mar 06 14:20:30 minikube localkube[3271]: I0306 14:20:30.883835    3271 operation_executor.go:917] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/836b1214-0276-11e7-9885-0800272e2447-default-token-77nfr" (spec.Name: "default-token-77nfr") pod "836b1214-0276-11e7-9885-0800272e2447" (UID: "836b1214-0276-11e7-9885-0800272e2447").
Mar 06 14:20:47 minikube localkube[3271]: I0306 14:20:47.820727    3271 operation_executor.go:917] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/8357ed5c-0276-11e7-9885-0800272e2447-default-token-77nfr" (spec.Name: "default-token-77nfr") pod "8357ed5c-0276-11e7-9885-0800272e2447" (UID: "8357ed5c-0276-11e7-9885-0800272e2447").
Mar 06 14:21:02 minikube localkube[3271]: apply entries took too long [11.765144ms for 1 entries]
Mar 06 14:21:02 minikube localkube[3271]: avoid queries with large range/delete range!
Mar 06 14:21:09 minikube localkube[3271]: E0306 14:21:09.826764    3271 repair.go:132] the node port 30000 for service kubernetes-dashboard/kube-system is not allocated; repairing
Mar 06 14:21:57 minikube localkube[3271]: I0306 14:21:57.895042    3271 operation_executor.go:917] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/836b1214-0276-11e7-9885-0800272e2447-default-token-77nfr" (spec.Name: "default-token-77nfr") pod "836b1214-0276-11e7-9885-0800272e2447" (UID: "836b1214-0276-11e7-9885-0800272e2447").
Mar 06 14:21:58 minikube localkube[3271]: I0306 14:21:58.899802    3271 operation_executor.go:917] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/8357ed5c-0276-11e7-9885-0800272e2447-default-token-77nfr" (spec.Name: "default-token-77nfr") pod "8357ed5c-0276-11e7-9885-0800272e2447" (UID: "8357ed5c-0276-11e7-9885-0800272e2447").

If I SSH in, I can see that there is 1 failed systemd unit, no idea if it matters or not:

$ systemctl status systemd-networkd-wait-online.service
● systemd-networkd-wait-online.service - Wait for Network to be Configured
   Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2017-03-06 14:09:08 UTC; 18min ago
     Docs: man:systemd-networkd-wait-online.service(8)
  Process: 3241 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE)
 Main PID: 3241 (code=exited, status=1/FAILURE)

Mar 06 14:07:08 minikube systemd[1]: Starting Wait for Network to be Configured...
Mar 06 14:07:08 minikube systemd-networkd-wait-online[3241]: ignoring: lo
Mar 06 14:09:08 minikube systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Mar 06 14:09:08 minikube systemd[1]: Failed to start Wait for Network to be Configured.
Mar 06 14:09:08 minikube systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
Mar 06 14:09:08 minikube systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.

The text was updated successfully, but these errors were encountered:

donspaulding · 2017-03-13T20:08:21Z

@norbert-yoimo I think I'm seeing a similar issue to you. Is the kube API server flapping up and down? I mean, are you able to run kubectl get pods at some times, and then within a few seconds, it returns the dial tcp error?

norbert-yoimo · 2017-03-14T10:49:55Z

I just tried a few times, but I could never get it to connect.

aaron-prindle · 2017-03-16T17:49:01Z

Can you post the output of minkube ssh journalctl and minikube logs?

bvdeenen · 2017-03-20T13:29:06Z

Hi, I have the same issue

minikube.log.txt
journalctl.txt

My OS is Void Linux, with VirtualBox 5.1.14.

Oh I checked that from the vm (via minikube ssh) I can access the world:

docker run -ti alpine  /bin/sh

And both from the vm and from the just started alpine docker.

curl https://www.xs4all.nl/index.html

gtirloni · 2017-03-23T14:42:46Z

The failed systemd-networkd-wait-online.service is a red herring for this issue. See #1277.

norbert-yoimo · 2017-04-11T15:40:11Z

Tried again with 0.18.0, still the same problem, attaching the requested files:

journalctl
logs

vadimio · 2017-04-20T18:59:09Z

Same problem

RaananHadar · 2017-04-22T19:50:47Z

same problem on ubuntu 17.04

david1983 · 2017-05-05T21:20:04Z

@RaananHadar I found the solution for ubuntu 17.04 the problem is in the docker version in the Ubuntu repo, you need to uninstall docker docker-engine and install docker-ce.
Here are the steps that I've done:

$sudo apt-get remove docker docker-engine

follow the steps to install docker-ce but you need to change the sources from zesty to xenial because the repo for zesty does not exist yet (tricky bit).

$ sudo apt-get update

$ sudo apt-get install
linux-image-extra-$(uname -r)
linux-image-extra-virtual

$ sudo apt-get install
apt-transport-https
ca-certificates
curl
software-properties-common

$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

$ sudo apt-key fingerprint 0EBFCD88
the key should be equal to this : 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88.

IMPORTANT!!!!
add the repository using xenial instead of zesty
$ sudo add-apt-repository
"deb [arch=amd64] https://download.docker.com/linux/ubuntu xenial stable"

$ sudo apt-get update

$ sudo apt-get install docker-ce

at this point run minikube
$ minikube start

and check the status
$minikube status
minikubeVM: Running
localkube: Running

Now you should be able to run kubectl cluster-info

mdmarek · 2017-05-23T00:55:15Z

@david1983 I tried the instructions above but in the end got the same network error, like @RaananHadar I was trying this on Ubuntu 17.04.

journalctl
logs

jpmolinamatute · 2017-05-29T17:21:48Z

same problem here :-(

dfredell · 2017-07-20T16:14:00Z

For others that run into this problem. #1224 (comment) solved it for me.

fejta-bot · 2018-01-01T07:30:37Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

fejta-bot · 2018-01-31T07:38:33Z

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

fejta-bot · 2018-03-02T08:24:15Z

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

editaxz · 2019-04-22T01:57:27Z

/reopen
Hi, I had this issue:

Then I check the minikube: "minikubeis not running"

Then I restarted minikube and It started to works.

I hope this will be useful to us.

jturi · 2020-02-04T13:45:22Z

In my case use-context was not set:

Use this if you have kubernetes running with Docker for Desktop:

kubectl config use-context docker-for-desktop

Use this if you have kubernetes running with minikube:

kubectl config use-context minikube

If you run into problems with Minikube, the best is to remove and start it over again:

minikube stop; minikube delete
rm /usr/local/bin/minikube
rm -rf ~/.minikube
minikube start

Gauravjaitly · 2020-09-29T22:26:02Z

In my case, my minikube wasnt active. had to start it by "minikube start"

priyawadhwa · 2020-09-30T18:23:45Z

Hey @editaxz did restarting the cluster via

minikube delete
minikube start

fix it for you? I'd suggest upgrading to the latest version of minikube, v1.13.1, as well.

tstromberg · 2020-10-07T02:40:35Z

Closing as this is due to speaking to a stopped cluster, but opened #9410 to make this less confusing for users.

r2d4 added the kind/bug Categorizes issue or PR as related to a bug. label Mar 12, 2017

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 1, 2018

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 31, 2018

k8s-ci-robot closed this as completed Mar 2, 2018

medyagh mentioned this issue Jun 8, 2020

Enable support for offline kic #8417

Merged

priyawadhwa reopened this Sep 30, 2020

priyawadhwa added the triage/needs-information Indicates an issue needs more information in order to work on it. label Sep 30, 2020

tstromberg changed the title ~~Unable to connect to the server: dial tcp i/o timeout~~ kubectl: Unable to connect to the server: dial tcp i/o timeout Oct 7, 2020

tstromberg closed this as completed Oct 7, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

kubectl: Unable to connect to the server: dial tcp i/o timeout #1234

kubectl: Unable to connect to the server: dial tcp i/o timeout #1234

norbert-yoimo commented Mar 10, 2017

donspaulding commented Mar 13, 2017

norbert-yoimo commented Mar 14, 2017

aaron-prindle commented Mar 16, 2017

bvdeenen commented Mar 20, 2017 •

edited

Loading

gtirloni commented Mar 23, 2017

norbert-yoimo commented Apr 11, 2017

vadimio commented Apr 20, 2017

RaananHadar commented Apr 22, 2017

david1983 commented May 5, 2017 •

edited

Loading

mdmarek commented May 23, 2017 •

edited

Loading

jpmolinamatute commented May 29, 2017

dfredell commented Jul 20, 2017

fejta-bot commented Jan 1, 2018

fejta-bot commented Jan 31, 2018

fejta-bot commented Mar 2, 2018

editaxz commented Apr 22, 2019 •

edited

Loading

jturi commented Feb 4, 2020

Gauravjaitly commented Sep 29, 2020

priyawadhwa commented Sep 30, 2020

tstromberg commented Oct 7, 2020

kubectl: Unable to connect to the server: dial tcp i/o timeout #1234

kubectl: Unable to connect to the server: dial tcp i/o timeout #1234

Comments

norbert-yoimo commented Mar 10, 2017

donspaulding commented Mar 13, 2017

norbert-yoimo commented Mar 14, 2017

aaron-prindle commented Mar 16, 2017

bvdeenen commented Mar 20, 2017 • edited Loading

gtirloni commented Mar 23, 2017

norbert-yoimo commented Apr 11, 2017

vadimio commented Apr 20, 2017

RaananHadar commented Apr 22, 2017

david1983 commented May 5, 2017 • edited Loading

mdmarek commented May 23, 2017 • edited Loading

jpmolinamatute commented May 29, 2017

dfredell commented Jul 20, 2017

fejta-bot commented Jan 1, 2018

fejta-bot commented Jan 31, 2018

fejta-bot commented Mar 2, 2018

editaxz commented Apr 22, 2019 • edited Loading

jturi commented Feb 4, 2020

Gauravjaitly commented Sep 29, 2020

priyawadhwa commented Sep 30, 2020

tstromberg commented Oct 7, 2020

bvdeenen commented Mar 20, 2017 •

edited

Loading

david1983 commented May 5, 2017 •

edited

Loading

mdmarek commented May 23, 2017 •

edited

Loading

editaxz commented Apr 22, 2019 •

edited

Loading