Package: docker.io Version: 1.2.0~dfsg1-2 Severity: normal root@elephant:/etc>docker.io ps 2014/10/19 03:31:46 Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
root@elephant:/etc>ps ax |grep 'docker.io -d'
3172 pts/3 S+ 0:00 grep docker.io -d
12111 pts/1 S+ 0:02 strace -o strace2 docker.io -d
12160 pts/1 Sl+ 4:56 docker.io -d
I happened to have docker running in a screen session, and straced,
since I'm attempted to track down the other bug I reported, so I could see
the last lines of output, which all look ok:
[4cc2a997] -job containers() = OK (0)
[info] GET /v1.14/containers/json
[4cc2a997] +job containers()
[4cc2a997] -job containers() = OK (0)
[info] GET /v1.14/containers/json
[4cc2a997] +job containers()
[4cc2a997] -job containers() = OK (0)
And I have the strace log, which ends like this:
futex(0x1000d58, FUTEX_WAKE, 1) = 1
clock_gettime(CLOCK_REALTIME, {1413552721, 769924641}) = 0
write(18, "{\"log\":\"propellor: \\u003csocket:"..., 146) = 146
read(25, 0xc208226000, 32768) = ? ERESTARTSYS (To be restarted if
SA_RESTART is set)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
rt_sigreturn() = 0
read(25, 0xc208226000, 32768) = ? ERESTARTSYS (To be restarted if
SA_RESTART is set)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
rt_sigreturn() = 0
read(25,
Complete strace attached.
Here's /proc/12160/fd, where we can see that the fd 25 it's reading
from and blocking is /dev/pymx.
dr-x------ 2 root root 0 Oct 16 16:56 ./
dr-xr-xr-x 9 root root 0 Oct 10 12:10 ../
lrwx------ 1 root root 64 Oct 18 23:46 0 -> /dev/pts/1
lrwx------ 1 root root 64 Oct 18 23:46 1 -> /dev/pts/1
lrwx------ 1 root root 64 Oct 18 23:46 10 ->
/var/lib/docker/containers/ab9d53701537e768f545a9f95df9ab85cdd191b5ddd74eaf16155ecf48b69f09/ab9d53701537e768f545a9f95df9ab85cdd191b5ddd74eaf16155ecf48b69f09-json.log
lrwx------ 1 root root 64 Oct 18 23:46 11 -> /dev/ptmx
lrwx------ 1 root root 64 Oct 18 23:46 12 -> socket:[1525702922]
lrwx------ 1 root root 64 Oct 18 23:46 13 -> socket:[636542107]
lrwx------ 1 root root 64 Oct 18 23:46 14 -> socket:[1525655771]
lrwx------ 1 root root 64 Oct 18 23:46 15 ->
/var/lib/docker/containers/bbed6c2245cfe27efe470fcac76a1add11edb1da4aed8daebdf50f1e7f44777c/bbed6c2245cfe27efe470fcac76a1add11edb1da4aed8daebdf50f1e7f44777c-json.log
lrwx------ 1 root root 64 Oct 18 23:46 16 ->
/var/lib/docker/containers/bbed6c2245cfe27efe470fcac76a1add11edb1da4aed8daebdf50f1e7f44777c/bbed6c2245cfe27efe470fcac76a1add11edb1da4aed8daebdf50f1e7f44777c-json.log
lrwx------ 1 root root 64 Oct 18 23:46 17 -> /dev/ptmx
lrwx------ 1 root root 64 Oct 18 23:46 18 ->
/var/lib/docker/containers/8486cc1a7c1162894ec73587fc4f3cd20b6e35b603522bc0cf24d577b9e95be7/8486cc1a7c1162894ec73587fc4f3cd20b6e35b603522bc0cf24d577b9e95be7-json.log
lrwx------ 1 root root 64 Oct 18 23:46 19 -> socket:[636542570]
lrwx------ 1 root root 64 Oct 16 17:01 2 -> /dev/pts/1
lrwx------ 1 root root 64 Oct 18 23:46 20 -> socket:[1525702077]
lrwx------ 1 root root 64 Oct 18 23:46 21 -> socket:[1525702976]
lrwx------ 1 root root 64 Oct 18 23:46 22 -> socket:[1525702978]
lrwx------ 1 root root 64 Oct 18 23:46 23 ->
/var/lib/docker/containers/b72a24acddb1786eb9be0708c456844428e7d139249a6e9db8bfd5f4274567b1/b72a24acddb1786eb9be0708c456844428e7d139249a6e9db8bfd5f4274567b1-json.log
lrwx------ 1 root root 64 Oct 18 23:46 24 ->
/var/lib/docker/containers/8486cc1a7c1162894ec73587fc4f3cd20b6e35b603522bc0cf24d577b9e95be7/8486cc1a7c1162894ec73587fc4f3cd20b6e35b603522bc0cf24d577b9e95be7-json.log
lrwx------ 1 root root 64 Oct 18 23:46 25 -> /dev/ptmx
lrwx------ 1 root root 64 Oct 18 23:46 26 ->
/var/lib/docker/containers/b72a24acddb1786eb9be0708c456844428e7d139249a6e9db8bfd5f4274567b1/b72a24acddb1786eb9be0708c456844428e7d139249a6e9db8bfd5f4274567b1-json.log
lrwx------ 1 root root 64 Oct 18 23:46 27 -> socket:[636543916]
lrwx------ 1 root root 64 Oct 18 23:46 28 -> /dev/ptmx
lrwx------ 1 root root 64 Oct 18 23:46 29 -> socket:[1525702140]
lr-x------ 1 root root 64 Oct 18 23:46 3 -> /dev/urandom
lrwx------ 1 root root 64 Oct 18 23:46 30 -> socket:[1525702993]
lrwx------ 1 root root 64 Oct 18 23:46 31 -> socket:[1525718669]
lrwx------ 1 root root 64 Oct 18 23:46 32 -> socket:[1525718676]
lrwx------ 1 root root 64 Oct 18 23:46 33 -> socket:[1525724109]
lrwx------ 1 root root 64 Oct 18 23:46 34 -> socket:[1525724122]
lrwx------ 1 root root 64 Oct 18 23:46 35 -> socket:[1525728455]
lrwx------ 1 root root 64 Oct 18 23:46 36 -> socket:[1525733296]
lrwx------ 1 root root 64 Oct 18 23:46 37 -> socket:[1525733299]
lrwx------ 1 root root 64 Oct 18 23:46 38 -> socket:[1525733303]
lrwx------ 1 root root 64 Oct 18 23:46 39 -> socket:[1525756414]
lrwx------ 1 root root 64 Oct 18 23:46 4 -> socket:[636533398]
lrwx------ 1 root root 64 Oct 18 23:46 40 -> socket:[1525755596]
lrwx------ 1 root root 64 Oct 18 23:46 41 -> socket:[1525755602]
lrwx------ 1 root root 64 Oct 18 23:46 42 -> socket:[1525756449]
lrwx------ 1 root root 64 Oct 18 23:46 43 -> socket:[1525768395]
lrwx------ 1 root root 64 Oct 18 23:46 44 -> socket:[1525768403]
lrwx------ 1 root root 64 Oct 18 23:46 45 -> socket:[1525769012]
lrwx------ 1 root root 64 Oct 18 23:46 46 -> socket:[1525774251]
lrwx------ 1 root root 64 Oct 18 23:46 47 -> socket:[1525774702]
lrwx------ 1 root root 64 Oct 18 23:46 48 -> socket:[1525995039]
lrwx------ 1 root root 64 Oct 18 23:46 5 -> anon_inode:[eventpoll]
lrwx------ 1 root root 64 Oct 18 23:46 6 -> /var/lib/docker/linkgraph.db
lrwx------ 1 root root 64 Oct 18 23:46 7 -> /var/lib/docker/linkgraph.db
lrwx------ 1 root root 64 Oct 18 23:46 8 -> socket:[1525702920]
lrwx------ 1 root root 64 Oct 18 23:46 9 ->
/var/lib/docker/containers/ab9d53701537e768f545a9f95df9ab85cdd191b5ddd74eaf16155ecf48b69f09/ab9d53701537e768f545a9f95df9ab85cdd191b5ddd74eaf16155ecf48b69f09-json.log
I have seen this happen more than once, although I don't know how to
trigger the problem.
Interestingly, while the docker daemon stopped answering requests here,
all the containers stayed up and running. In fact, I have left the daemon
this state for now, until I need to modify a container, so if there are ideas
for thing to look at I may be able to try them.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages docker.io depends on:
ii adduser 3.113+nmu3
ii iptables 1.4.21-2
ii libapparmor1 2.8.0-8
ii libc6 2.19-11
ii libdevmapper1.02.1 2:1.02.90-2
ii libsqlite3-0 3.8.6-1
ii perl 5.20.1-1
Versions of packages docker.io recommends:
ii aufs-tools 1:3.2+20130722-1.1
ii ca-certificates 20140927
ii cgroupfs-mount 1.0
ii git 1:2.1.1-1
ii xz-utils 5.1.1alpha+20120614-2
Versions of packages docker.io suggests:
pn btrfs-tools <none>
ii debootstrap 1.0.63
pn lxc <none>
pn rinse <none>
-- no debconf information
--
see shy jo
strace2.bz2
Description: Binary data
signature.asc
Description: Digital signature
