I observed when inspecting invoker logs where a pause failed that the `tid` is 
missing on the pause command and subsequent cleanup:

```
[2018-09-06T16:18:30.111Z] [INFO] [#tid_zE2ldYR6sgmxYf2CcGHK1K5E20Ao2LPe] 
[DockerClientWithFileAccess] running /usr/bin/docker run -d --cpu-shares 256 
--memory 256m --memory-swap 256m --network openwhisk_default -e 
__OW_API_HOST=https://172.17.0.1:443 --name wsk0_7_guest_t --cap-drop NET_RAW 
--cap-drop NET_ADMIN --ulimit nofile=1024:1024 --pids-limit 1024 --log-driver 
json-file ... (timeout: 1 minute) [marker:invoker_docker.run_start:810]
[2018-09-06T16:18:31.553Z] [INFO] [#tid_zE2ldYR6sgmxYf2CcGHK1K5E20Ao2LPe] 
[DockerClientWithFileAccess]  [marker:invoker_docker.run_finish:2253:1443]
[2018-09-06T16:18:31.571Z] [INFO] [#tid_zE2ldYR6sgmxYf2CcGHK1K5E20Ao2LPe] 
[DockerContainer] sending initialization to 
ContainerId(ed123b84f0aaffd4c449e89c6529ee6795a78768f52109e1a1568d07d0d7dd09) 
ContainerAddress(172.18.0.13,8080) [marker:invoker_activationInit_start:2270]
...
[2018-09-06T16:18:32.107Z] [INFO] [#tid_sid_invokerNanny] [RuncClient] running 
/usr/bin/docker-runc pause 
ed123b84f0aaffd4c449e89c6529ee6795a78768f52109e1a1568d07d0d7dd09 (timeout: 10 
seconds) [marker:invoker_runc.pause_start:133999]
[2018-09-06T16:18:32.117Z] [ERROR] [#tid_sid_invokerNanny] [RuncClient] code: 1 
, stdout: , stderr: open 
/run/runc/ed123b84f0aaffd4c449e89c6529ee6795a78768f52109e1a1568d07d0d7dd09/state.json:
 no such file or directory [marker:invoker_runc.pause_error:134010:10]
[2018-09-06T16:18:32.118Z] [INFO] [#tid_sid_invokerNanny] 
[DockerClientWithFileAccess] running /usr/bin/docker rm -f 
ed123b84f0aaffd4c449e89c6529ee6795a78768f52109e1a1568d07d0d7dd09 (timeout: 1 
minute) [marker:invoker_docker.rm_start:134010]
[2018-09-06T16:18:32.659Z] [INFO] [#tid_sid_invokerNanny] 
[DockerClientWithFileAccess]  [marker:invoker_docker.rm_finish:134551:541]
```

[ Full content available at: 
https://github.com/apache/incubator-openwhisk/issues/4007 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to