New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubectl is getting server timeout #73878

recrk opened this Issue Feb 9, 2019 · 2 comments


None yet
3 participants
Copy link

recrk commented Feb 9, 2019

I installed first ectd, kubeapiserver and kubelet using systemd service. The services are running fine and listening to all required ports.

When I run kubectl cluster-info , I get below output Kubernetes master is running at http://localhost:8080

When I run kubectl get componentstatuses, then I get below output etcd-0 Healthy {"health": "true"}

But running kubectl get nodes , I get below error Error from server (ServerTimeout): the server cannot complete the requested operation at this time, try again later (get nodes)

Can anybody help me out on this.

@recrk recrk added the triage/support label Feb 9, 2019


This comment has been minimized.

Copy link

k8s-ci-robot commented Feb 9, 2019

@recrk: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

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.


This comment has been minimized.

Copy link

tanshanshan commented Feb 12, 2019

maybe you can use journalctl -fu to get kube-apiserver and kubelet logs , wheather exists error log .
or user curl to access apiserver
and paste kubernetes version info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment