Kubeadm: The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.

Created on 7 Nov 2019  路  7Comments  路  Source: kubernetes/kubeadm

i have installed kubernetes on rhel7.4
when i run kubeadm init i am getting error like
The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.

Unfortunately, an error has occurred:
timed out waiting for the condition

This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

can some one guide me to resolve this error

kinsupport

Most helpful comment

i have installed kubernetes on arm
and I have the same problem as you
The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.

but after i reset kubeadm , the problem remains
can you tell me the detailed solution process, thanks

All 7 comments

try calling kubeadm reset, then kubeadm init again and look at the kubelet logs right after this happens using journalctl -xeu kubelet and share them here.

/triage support

Thanks i have done kubectl reset and i have increased the memory size and it's running fine.
can you tell me how to make single master node cluster i want to set up in one instance only master and node how can we do this

Thanks i have done kubectl reset and i have increased the memory size and it's running fine.

thanks for confirming that it works.

can you tell me how to make single master node cluster i want to set up in one instance only master and node how can we do this

calling kubeadm init on one machine will give you a single control-plane instance (one master). then you can join workers to it. if you don't join any new control-planes using kubeadm join ... --control-plane... you will remain with a single control-plane.

Thanks i have done kubectl reset and i have increased the memory size and it's running fine.
That must be kubeadm reset but not kubectl reset
can you tell me how to make single master node cluster i want to set up in one instance only master and node how can we do this

Thanks i have done kubectl reset and i have increased the memory size and it's running fine.
can you tell me how to make single master node cluster i want to set up in one instance only master and node how can we do this

Encountered this problem, minikube 1.12.1 docker 18.0.1 centos 8.1 kubernets version 1.18.3.

Tried your way, failed.

i have installed kubernetes on arm
and I have the same problem as you
The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.

but after i reset kubeadm , the problem remains
can you tell me the detailed solution process, thanks

@cheeseyeah and anyone else stumbling upon this thread: in my case the containers where not created, or at least they weren't there after the kubeadm command finished. I managed to make it work only after disabling swap. This is crazy, from my point of view, because swap is a normal OS function and shouldn't create this bizarre behavior. But, hey, it works.

Was this page helpful?
0 / 5 - 0 ratings