This cluster is currently Unavailable; areas that interact directly with it will not be available until the API is ready

Hello all,

Thanks for the great product.
I have been trying it for over 4 months now, but I still run untill problems more often then I expected.
Part of learning is breaking and fixing, but sometimes its hard to find out what and where it broke, and why? And what exactly to monitor…
My cluster now no longer works As i get the error:

This cluster is currently Unavailable; areas that interact directly with it will not be available until the API is ready.

I checked etcd kubectl logs and kube, looks fine.
kubectl command no longer works.

I do see some errore on kube-apiserver
1 log.go:172] http: TLS handshake error from 10.255.7.63:49118: EOF
I0326 14:19:25.401947 1 log.go:172] http: TLS handshake error from 10.255.7.63:49120: EOF
I0326 14:19:25.405188 1 log.go:172] http: TLS handshake error from 10.255.7.63:49122: EOF
I0326 14:19:25.408568 1 log.go:172] http: TLS handshake error from 10.255.7.63:49124: EOF
I0326 14:19:25.434846 1 log.go:172] http: TLS handshake error from 10.255.7.63:49128: EOF
I0326 14:19:25.438337 1 log.go:172] http: TLS handshake error from 10.255.7.63:49130: EOF
I0326 14:19:25.438730 1 log.go:172] http: TLS handshake error from 10.255.7.63:49126: EOF

could that be the cause of the error?

I am running rancher os 1.5 and rancher server v2 (latest)

I saw some of rancher images running under ubuntu I am thinking about using ubuntu 18 instead of rancher OS, it is a great idea but it seems just another layer of possible problems, and I miss have a full a OS (systemd) and etc…

thanks

I was getting similar issue and it turned out restarting my cluster ends up fixing the issue. I use EC2 for my node templates and once I rebooted my EC2 instance it fixed the error.

1 Like

thanks I did the same, reboot the HOST and it now is working…
wish someone could explain what happened…