How to deal with error "dial tcp 10.240.0.4:10250: i/o timeout" to see pod's logs in AKS?

Question

Before I could run this command kubectl logs <pod> without issue for many days/versions. However, after I pushed another image and deployed recently, I faced below error:

Error from server: Get https://aks-agentpool-xxx-0:10250/containerLogs/default/<-pod->/<-service->: dial tcp 10.240.0.4:10250: i/o timeout

I tried to re-build and re-deploy but failed.

Below was the Node info for reference:

i dont think has anything to do with the build. try redownloading kubectl config — 4c74356b41, Sep 10 '19 at 07:53
hi @4c74356b41, but when I logged in to another subscription's AKS, I could see the logs — DaiKeung, Sep 10 '19 at 08:01
hi @4c74356b41, may you share commands to me to redownload kubectl config? — DaiKeung, Sep 10 '19 at 08:06
https://learn.microsoft.com/en-us/azure/aks/kubernetes-walkthrough#connect-to-the-cluster it will show you the sample — 4c74356b41, Sep 10 '19 at 08:08
I tried to run below commands but still fails: 1. `az aks install-cli` 2. `az aks get-credentials --resource-group <-ResourceGroup-> --name <-AKS->` 3. checked still have timeout error 4. delete file in **/Users/<-user->/.kube/config** 5. `az aks get-credentials --resource-group <-ResourceGroup-> --name <-AKS->` Still not okay. — DaiKeung, Sep 10 '19 at 08:14
Do you check if there is any problem with the AKS cluster node? — Charles Xu, Sep 11 '19 at 06:45
@CharlesXu, added Node Info for your reference by running `kubecel describe nodes` before. — DaiKeung, Sep 11 '19 at 06:51

score 3 · Accepted Answer · edited Aug 12 '21 at 12:09

3

Not sure if your issue is caused by the problem described in this troubleshooting. But maybe you can take a try, it shows below:

Make sure that the default network security group isn't modified and that both port 22 and 9000 are open for connection to the API server. Check whether the tunnelfront pod is running in the kube-system namespace using the kubectl get pods --namespace kube-system command. If it isn't, force deletion of the pod and it will restart.

edited Aug 12 '21 at 12:09

kenorb

155,785
88
678
743

answered Sep 12 '19 at 10:02

Charles Xu

29,862
2
22
39

In my case, deleting/restarting `tunnelfront` pod worked fine. – kenorb Aug 12 '21 at 12:10

How to deal with error "dial tcp 10.240.0.4:10250: i/o timeout" to see pod's logs in AKS?

1 Answers1

Linked