Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

swarm create fails with "remaining connection slots are reserved..." #1503

Closed
ahaurw01 opened this issue Dec 5, 2015 · 8 comments · Fixed by #1505
Closed

swarm create fails with "remaining connection slots are reserved..." #1503

ahaurw01 opened this issue Dec 5, 2015 · 8 comments · Fixed by #1505

Comments

@ahaurw01
Copy link
Contributor

ahaurw01 commented Dec 5, 2015

Following the beginner's docs for OSX:

# Terminal started via Docker Quickstart Terminal app.
$ docker-machine create -d virtualbox local
$ eval "$(docker-machine env local)"
$ docker run swarm create

Results in pq: remaining connection slots are reserved for non-replication superuser connections.

$ docker --version
# Docker version 1.9.1, build a34a1d5
$ docker run swarm --version
# swarm version 1.0.0 (087e245)

# Virtualbox version 5.0.10 r104061
# OSX 10.11.1 (15B42)

Any ideas what I'm doing wrong or how the docs need to be updated?

@ChristSent
Copy link

Same issue here with Ubuntu 14.04 LTS. This was totally working for me the night before last. Using whatever version of docker is available in the Ubuntu's default repos. Can provide more detail if need be.

@AlexOugh
Copy link

AlexOugh commented Dec 6, 2015

I also had "pq: sorry, too many clients already" error. After restarting docker, now I have the same error, "pq: remaining connection slots are reserved for non-replication superuser connections"

@stewartpark
Copy link

I'm having this error, too. I think node discovery with a token ID can be faulty in cases like this. Having a private discovery system should be strongly recommended. i.e. consul, etc. My nodes are all missing now and I have no means to access containers at the moment other than accessing each docker swarm host.

@remonlam
Copy link

remonlam commented Dec 6, 2015

If you're using Docker Swarm Discovery, it's down since Friday check http://status.docker.com
also check issue #1482 it's recommended to use a private discovery tool.

@rhinoceros
Copy link

I have the same problem.
root@xxxx:~# docker run --rm swarm create
pq: sorry, too many clients already

root@xxxx:~# docker version
Client:
Version: 1.9.1
API version: 1.21
Go version: go1.4.2
Git commit: a34a1d5
Built: Fri Nov 20 13:12:04 UTC 2015
OS/Arch: linux/amd64

Server:
Version: 1.9.1
API version: 1.21
Go version: go1.4.2
Git commit: a34a1d5
Built: Fri Nov 20 13:12:04 UTC 2015
OS/Arch: linux/amd64
root@xxxx:~# docker run --rm swarm -v
swarm version 1.0.0 (087e245)

root@xxxx:~# cat /etc/issue
Ubuntu 14.04 LTS \n \l

@cpuguy83
Copy link
Contributor

cpuguy83 commented Dec 6, 2015

It looks like this is because the hosted discovery service is having issues.
Please try with either a static node list or with a supporter k/v store (etcd, zk, consul).

@ahaurw01
Copy link
Contributor Author

ahaurw01 commented Dec 6, 2015

I created a PR to add a documentation note with this advice. Thanks all for chiming in. I haven't yet tried setting up an alternate backend. I'll try to confirm that this works.

@amitshukla
Copy link

Thanks @ahaurw01 - closing this question

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

Successfully merging a pull request may close this issue.

8 participants