Minikube: none: Error restarting cluster: waiting for apiserver: apiserver process never appeared

Created on 16 Oct 2019  ยท  10Comments  ยท  Source: kubernetes/minikube

The command:
minikube start

The output of the command that failed:
๐Ÿ˜„ minikube v1.4.0 sur Ubuntu 18.04
๐Ÿ’ก Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
๐Ÿƒ Using the running none "minikube" VM ...
โŒ› Waiting for the host to be provisioned ...
๐Ÿณ Configuring environment for Kubernetes v1.16.0 on Docker 18.06.1-ce...
โ–ช kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
๐Ÿ”„ Relaunching Kubernetes using kubeadm ...

๐Ÿ’ฃ Error restarting cluster: waiting for apiserver: apiserver process never appeared

๐Ÿ˜ฟ Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
๐Ÿ‘‰ https://github.com/kubernetes/minikube/issues/new/choose

The operating system version:
Ubuntu 18.04.3

capiserver cnone-driver kinsupport

Most helpful comment

I had the same issue
๐Ÿ’ฃ Error restarting cluster: waiting for apiserver: apiserver process never appeared
When i ran _minikube start_

I solved this by running
minikube delete
And running minkube startagain . And it worked.

All 10 comments

This issue appears to be a duplicate of #5451, do you mind if we move the conversation there?

This way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using /reopen. If you have additional information to share, please add it to the new issue.

Thank you for reporting this!

/reopen

@GrimaudNathan: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hey @GrimaudNathan, could you please provide some more information so that we can assist in resolving this issue:

  • The full output of minikube logs

Thanks!

@GrimaudNathan Could you provide more details so we can debug your issue further:

  • Whether the issue occurs with the latest minikube release
  • The full output of the minikube start command, preferably with --alsologtostderr -v=3 for extra logging.

    • The full output of minikube logs

My Logs following this:

Nov 03 14:05:26 localhost kubelet[19965]: E1103 14:05:26.036199   19965 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused

I had the same issue
๐Ÿ’ฃ Error restarting cluster: waiting for apiserver: apiserver process never appeared
When i ran _minikube start_

I solved this by running
minikube delete
And running minkube startagain . And it worked.

Thank you all !, I had the same issue on a Mac OS with VirtualBox and running "minikube delete" and after that , minikube start --vm-driver=virtualbox also fixed the issue as mentioned by phfirmware !

@claudioabudio glad to see the issue was resolved, I will close this issue, please feel free to reopen if still have isssues.

@phirmware It indeed solves the issue, but it is so irritating that I have to do it frequently. Something is fishy...

Was this page helpful?
0 / 5 - 0 ratings