1:17 a.m.
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Bug ID: 1087704
Summary: repetition of signal 21 with --sig-proxy and SIGSTOP
of docker
Product: Fedora
Version: 20
Component: docker-io
Severity: low
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
I noticed weird reaction to SIGSTOP signal. When you start container with
--sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to
the `docker run` process, it's put into background. (so far correct behavior)
Than when you use kill -SIGCONT, it's resumed (still in background) and it's
continuing to send signal 21 to the container (100% CPU utilization).
This disappears once you attach the process with fg.
Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64
How reproducible:
always
Steps to Reproduce:
1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly
localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps ax |grep docker
3. kill -SIGSTOP $PID
4. kill -SIGCONT $PID
Actual results:
[1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name
test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`;
do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1;
done'
[root@t530 ~]# Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
... (100% CPU utilization, when you use fg it stops and you can use the
container again...)
Expected results:
[1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name
test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`;
do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1;
done'
[root@t530 ~]# Received 21, ignoring...
Additional info:
I'm not definitely sure if this is really required as it's not a common usage.
But as there is no way to detach the process apart from kill -SIGSTOP people
might use it and get to this problem...
--
You are receiving this mail because:
You are on the CC list for the bug.
2:59 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
--- Comment #1 from Lukas Doktor <ldoktor(a)redhat.com> ---
I retested this with the upstream dc9c28f/0.10.0 with the same results. The
daemon output is:
...
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) =
OK (0)
2014/05/05 09:58:13 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN)
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) =
OK (0)
2014/05/05 09:58:13 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN)
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) =
OK (0)
2014/05/05 09:58:13 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
9:38 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Lukas Doktor <ldoktor(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |1096273
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1096273
[Bug 1096273] repetition of signal 21 with --sig-proxy and SIGSTOP of
docker
--
You are receiving this mail because:
You are on the CC list for the bug.
4:29 p.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ldoktor(a)redhat.com
Flags| |needinfo?(ldoktor(a)redhat.co
| |m)
--- Comment #2 from Daniel Walsh <dwalsh(a)redhat.com> ---
Are you still seeing this with 0.11?
--
You are receiving this mail because:
You are on the CC list for the bug.
6:30 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Lukas Doktor <ldoktor(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(ldoktor(a)redhat.co |
|m) |
--- Comment #3 from Lukas Doktor <ldoktor(a)redhat.com> ---
I tested it only on RHEL version of this package here:
https://bugzilla.redhat.com/show_bug.cgi?id=1096273
the bug persists...
--
You are receiving this mail because:
You are on the CC list for the bug.
3:35 p.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|lsm5(a)redhat.com |whenry(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
2:26 p.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|whenry(a)redhat.com |mheon(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
8:59 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--
You are receiving this mail because:
You are on the CC list for the bug.
2:59 p.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
--- Comment #4 from Daniel Walsh <dwalsh(a)redhat.com> ---
Can you test against docker-1.2
--
You are receiving this mail because:
You are on the CC list for the bug.
3:44 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
--- Comment #5 from Lukas Doktor <ldoktor(a)redhat.com> ---
On docker-1.2.0-19.el7.x86_64 it still fails and results in too many open
files:
[debug] commands.go:610 Error sending signal: Post
http:///var/run/docker.sock/v1.15/containers/64b2b2d8171bca438d6c7a0e2ed93573e0dd37ab1a0c9a2f75f8acd77bda8236/kill?signal=TTIN:
dial unix /var/run/docker.sock: too many open files
[debug] commands.go:610 Error sending signal: Post
http:///var/run/docker.sock/v1.15/containers/64b2b2d8171bca438d6c7a0e2ed93573e0dd37ab1a0c9a2f75f8acd77bda8236/kill?signal=TTIN:
dial unix /var/run/docker.sock: too many open files
[debug] commands.go:610 Error sending signal: Post
http:///var/run/docker.sock/v1.15/containers/64b2b2d8171bca438d6c7a0e2ed93573e0dd37ab1a0c9a2f75f8acd77bda8236/kill?signal=TTIN:
dial unix /var/run/docker.sock: too many open files
[debug] commands.go:610 Error sending signal: Post
http:///var/run/docker.sock/v1.15/containers/64b2b2d8171bca438d6c7a0e2ed93573e0dd37ab1a0c9a2f75f8acd77bda8236/kill?signal=TTIN:
dial unix /var/run/docker.sock: too many open files
[debug] commands.go:610 Error sending signal: Post
http:///var/run/docker.sock/v1.15/containers/64b2b2d8171bca438d6c7a0e2ed93573e0dd37ab1a0c9a2f75f8acd77bda8236/kill?signal=TTIN:
dial unix /var/run/docker.sock: too many open files
[debug] stdcopy.go:98 Corrupted prefix: []
[debug] hijack.go:102 [hijack] End of stdout
[debug] hijack.go:110 [hijack] End of stdin
[debug] hijack.go:118 Couldn't send EOF: use of closed network connection
[debug] commands.go:2332 End of CmdRun(), Waiting for hijack to finish.
2014/09/26 13:07:49 Get
http:///var/run/docker.sock/v1.15/containers/64b2b2d8171bca438d6c7a0e2ed93573e0dd37ab1a0c9a2f75f8acd77bda8236/json:
dial unix /var/run/docker.sock: too many open files
--
You are receiving this mail because:
You are on the CC list for the bug.
3:53 p.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
John Skeoch <jskeoch(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|mheon(a)redhat.com |jrieden(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
8:38 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|jrieden(a)redhat.com |mheon(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
10:26 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
--- Comment #7 from Matthew Heon <mheon(a)redhat.com> ---
I'm fairly certain this is an issue with Golang, not docker-specific. Upstream
issue tracker describing very similar symptoms from SIGSTOP:
https://github.com/golang/go/issues/4391
--
You are receiving this mail because:
You are on the CC list for the bug.
7:17 a.m.
New subject: [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Daniel Walsh <dwalsh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution|--- |CANTFIX
Last Closed| |2015-04-15 08:17:16
--- Comment #8 from Daniel Walsh <dwalsh(a)redhat.com> ---
Not something docker can fix.
--
You are receiving this mail because:
You are on the CC list for the bug.
3298
days inactive
3663
days old
golang@lists.fedoraproject.org
13 comments
1 participants
participants (1)
-
Red Hat Bugzilla