Skip to content
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

docker manager node throwing rpc error #33631

Closed
chaitu0292 opened this issue Jun 11, 2017 · 1 comment
Closed

docker manager node throwing rpc error #33631

chaitu0292 opened this issue Jun 11, 2017 · 1 comment

Comments

@chaitu0292
Copy link

ours is a cluster of 11 machines and we have 3 manager nodes.Till date it used to work fine but due to unkown reasons machines got rebooted and docker engine didnt start on reboot.
So manually started.
After that when i execute docker node ls its throwing the below error
Error response from daemon: rpc error: code = 4 desc = context deadline exceeded

What is this error?which caused this?which reason?

Environment:
centos 7
Client:
Version: 17.03.1-ce
API version: 1.27
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:05:44 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.1-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:05:44 2017
OS/Arch: linux/amd64
Experimental: false

@thaJeztah
Copy link
Member

This error can have various causes (see https://github.com/moby/moby/issues?utf8=✓&q=is%3Aissue%20%22context%20deadline%20exceeded%22 for existing issues mentioning this error). The error itself is quite generic, and could mean that the manager was not able to communicate with other managers in the cluster. From just the error, it's not easy to discover why it fails to communicate (it can be either a bad network connection, other managers did not properly re-join the cluster, therefore you lost quorum, or it could be if (e.g.) managers did not have a static IP-address, and the IP-address changed - which is currently not supported).

We have an issue to improve the error message, and provide more information about the specific reason for the error (where possible); see #29987, and #29367

Please keep in mind that the GitHub issue tracker is not a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

I'm going to close this issue because this is a support question, but feel free to comment after I closed.

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

No branches or pull requests

3 participants