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

Agent unable to connect to the leader #2546

Open
anshulpundir opened this issue Mar 8, 2018 · 2 comments
Open

Agent unable to connect to the leader #2546

anshulpundir opened this issue Mar 8, 2018 · 2 comments
Assignees

Comments

@anshulpundir
Copy link
Contributor

In this instance seen recently, the manager is aware of the cluster leader:

Mar 05 10:28:43 dockerd[1109]: time="2018-03-05T10:28:43.905167275-05:00" level=info msg="raft.node: 39500a8b3abac75d elected leader 713d480a713f8585 at term 3600" module=raft node.id=pvp0h3p6cwy157do6ajbfbhuu

But the agent session rpc is still delivered to the dispatcher on the local node:

Mar 05 10:29:14 dockerd[1109]: time="2018-03-05T10:29:14.408645452-05:00" level=error msg="agent: session failed" error="rpc error: code = 10 desc = dispatcher is stopped" module="node/agent" node.id=pvp0h3p6cwy157do6ajbfbhuu

@anshulpundir anshulpundir self-assigned this Mar 8, 2018
@cyli
Copy link
Contributor

cyli commented Mar 8, 2018

moby/moby#36326 (comment) seemed to be this issue as well.

@anshulpundir
Copy link
Contributor Author

But the agent session rpc is still delivered to the dispatcher on the local node:

Actually I don't know this for certain. Its not clear which manager these rpcs are being routed to.

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

No branches or pull requests

2 participants