Visualizer not displaying node about docker-swarm-visualizer HOT 24 CLOSED

Looks like your firewall is preventing access to the Docker Unix socket.

from docker-swarm-visualizer.

Turning off the firewall on all systems did not correct the incident.
The error messages in the container log do not appear until I enter URL: http://192.168.1.201:5000/ in the browser and stop when I close the browser and start again when entering the URL: http://192.168.1.201:5000/ in the browser. No errors were found in /var/log/upstart/docker.log

from docker-swarm-visualizer.

This is a duplicate of issue #3

from docker-swarm-visualizer.

You are correct that the observed symptom of the visualizer not displaying any nodes in browser is the same as #3 but #3 states no errors were found in the log as this one does. That is why I opened it to post the errors I am viewing in the log. It would be more helpful if you could suggest additional debugging method you would recommend, thank you.

from docker-swarm-visualizer.

Sorry I'm on vacation right now and unable to test things out
On Jul 3, 2016 4:35 PM, "Bradley Allen" [email protected] wrote:

You are correct that the observed symptom of the visualizer not displaying
any nodes in browser is the same as #3
#3 but #3
#3 states no
errors were found in the log as this one does. That is why I opened it to
post the errors I am viewing in the log. It would be more helpful if you
could suggest additional debugging method you would recommend, thank you.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#6 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAG8v8kEXJTghmpEMyL50YxdD8KpbOdvks5qR8idgaJpZM4JCt4J
.

from docker-swarm-visualizer.

I'll be back next week and in front of a computer
On Jul 3, 2016 7:18 PM, "Mano Marks" [email protected] wrote:

Sorry I'm on vacation right now and unable to test things out
On Jul 3, 2016 4:35 PM, "Bradley Allen" [email protected] wrote:

You are correct that the observed symptom of the visualizer not
displaying any nodes in browser is the same as #3
#3 but #3
#3 states
no errors were found in the log as this one does. That is why I opened it
to post the errors I am viewing in the log. It would be more helpful if you
could suggest additional debugging method you would recommend, thank you.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#6 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAG8v8kEXJTghmpEMyL50YxdD8KpbOdvks5qR8idgaJpZM4JCt4J
.

from docker-swarm-visualizer.

OK so I'm back. Is it possible your daemon is running on a different socket? It can be configured to run differently. Other things to try: Did you build the visualizer image yourself? Or use the hub version? If you used the hub version, try pulling again I just pushed a new image that works for me.

from docker-swarm-visualizer.

Repeated test on another system named three, same incident
Download docker 1.12.0-rc4
Restarted docker
$ sudo service docker restart
Downloaded latest manomarks/visualizer (did not build my own image)
$ docker images | grep mano
manomarks/visualizer latest 7f2899d7f460 23 hours ago 373.5 MB
Started visualizer

$ docker run -it -d -p 5000:5000 -e HOST=hostname -i -e PORT=5000 -v /var/run/docker.sock:/var/run/docker.sock manomarks/visualizer

Output of dockerd
$ ps -ef | grep dockerd
root 4954 1 1 12:23 ? 00:00:31 /usr/bin/dockerd --graph=/usr/local/docker --dns 192.168.1.202 --dns 8.8.8.8 --dns 8.8.4.4 --log-level warn --tlsverify --tlscacert=/etc/docker/certs.d/daemon/ca.pem --tlscert=/etc/docker/certs.d/daemon/three.cptx86.com-cert.pem --tlskey=/etc/docker/certs.d/daemon/three.cptx86.com-priv-key.pem -H=three.cptx86.com:2376 --raw-logs

$ docker logs $(docker ps -lq)
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info prestart [email protected]
npm info start [email protected]

[email protected] start /app
node server.js

problem with request: connect ECONNREFUSED /var/run/docker.sock
Error: connect ECONNREFUSED /var/run/docker.sock
at Object.exports._errnoException (util.js:849:11)
at exports._exceptionWithHostPort (util.js:872:20)
at PipeConnectWrap.afterConnect as oncomplete
problem with request: connect ECONNREFUSED /var/run/docker.sock
Error: connect ECONNREFUSED /var/run/docker.sock
at Object.exports._errnoException (util.js:849:11)
at exports._exceptionWithHostPort (util.js:872:20)
at PipeConnectWrap.afterConnect as oncomplete
. . .

from docker-swarm-visualizer.

What showed up in the Chrome console logs?

from docker-swarm-visualizer.

Never mind, it's a socket error, happening at initial connection to the docker socket.

from docker-swarm-visualizer.

What's the output of netstat -a ? Do you see something like
unix 2 [ ACC ] STREAM LISTENING 19954 /var/run/docker.sock
?

from docker-swarm-visualizer.

Also are you in the docker group? Check out the Docker Docs for more info

from docker-swarm-visualizer.

$ netstat -a | grep docker
unix 2 [ ACC ] STREAM LISTENING 2620 /var/lib/docker/network/files/54191b75bbb522945a8a4db733be3b61fb2fbd15dc5bc67ea6e1eb7e7c91979b.sock
unix 2 [ ACC ] STREAM LISTENING 26883 /usr/local/docker/swarm/control.sock
unix 2 [ ACC ] STREAM LISTENING 2427 /var/run/docker/libcontainerd/docker-containerd.sock
unix 3 [ ] STREAM CONNECTED 21105 /usr/local/docker/swarm/control.sock
unix 3 [ ] STREAM CONNECTED 1566 /var/run/docker/libcontainerd/docker-containerd.sock

$ groups
uthree adm cdrom sudo dip plugdev lpadmin sambashare docker

from docker-swarm-visualizer.

What happens if you run curl --unix-socket /var/run/docker.sock http:/containers/json

from docker-swarm-visualizer.

Also you can check out the docks on the Docker Remote API

from docker-swarm-visualizer.

$ curl --unix-socket /var/run/docker.sock http:/containers/json
curl: (7) Couldn't connect to server

from docker-swarm-visualizer.

OK so I think Docker is running on a different socket for you. Figure out what that is and substitute that for /var/run/docker.sock in the code should make it work

from docker-swarm-visualizer.

How would I determine what socket docker is running on ?
$ sudo ls -ld /var/run/docker.sock
drwxr-xr-x 2 root root 40 Jul 13 15:33 /var/run/docker.sock

from docker-swarm-visualizer.

I haven't been able to find a way. But, when you start Docker you can specify the path: https://docs.docker.com/engine/reference/commandline/dockerd/

from docker-swarm-visualizer.

Do you think the incident is because I am using TLS ? (-H=three.cptx86.com:2376)
Here is the option I an using with the daemon:
$ ps -ef | grep dockerd
root 4954 1 1 12:23 ? 00:00:31 /usr/bin/dockerd --graph=/usr/local/docker --dns 192.168.1.202 --dns 8.8.8.8 --dns 8.8.4.4 --log-level warn --tlsverify --tlscacert=/etc/docker/certs.d/daemon/ca.pem --tlscert=/etc/docker/certs.d/daemon/three.cptx86.com-cert.pem --tlskey=/etc/docker/certs.d/daemon/three.cptx86.com-priv-key.pem -H=three.cptx86.com:2376 --raw-logs

from docker-swarm-visualizer.

Yeah that could be it. I'm not as experienced in using that. Two things to try

1. use curl as described above to the default unix socket, but with certificates
2. try curling three.cptx86.com instead

from docker-swarm-visualizer.

curl --cert ~/.docker/cert.pem --key ~/.docker/key.pem --cacert ~/.docker/ca.pem --unix-socket /var/run/docker.sock https://hostname -f:2376/containers/json
curl: (7) Couldn't connect to server
2.
curl --cert ~/.docker/cert.pem --key ~/.docker/key.pem --cacert ~/.docker/ca.pem https://hostname -f:2376/containers/json [{"Id":"d5c03ceaf97183260d021ab21a274f488b72dacba1943b444148bfec17015f37","Names":["/tomcat"],"Image":"tomcat","ImageID":"sha256:25e98610c7d0ce3c3cf05a6d8b3e932135d86720f1d46e73a49a8256eca27892","Command":"cata . . .

from docker-swarm-visualizer.

Ah good. If you curl it without the certificates, then you have the path in your second example. You would just need to change the path in line 39 of server.js. However, if you need the certificates there's probably a bit more work. I'm using the ws NPM module for websocket connection which does look like it has some certificate support. It looks like I should have environment variable customization for custom daemon routes and certificates. Not sure when I'll get to that but I'll give it a shot. Is it OK to close this issue? I'll start another one to add those features and cc you.

from docker-swarm-visualizer.

Thank you for your help. All my systems are using TLS communications for Docker CLI and daemon.
Closing incident as current release may not support TLS and this maybe causing this incident.
I have found another method to receive the information I needed using the Linux watch command, but it is tied to a task, see example below:
docker service create --replicas 3 --name redis --update-delay 10s --update-parallelism 1 redis:3.0.6
docker service scale redis=20
docker service update --image redis:3.0.7 redis
watch -d -n 4 docker service tasks redis

from docker-swarm-visualizer.