[ 
https://issues.apache.org/jira/browse/MESOS-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309804#comment-14309804
 ] 

Matt Christiansen commented on MESOS-1837:
------------------------------------------

In the case of my issue, the containers are starting up and completing fine. I 
agree with [~tnachen] that in the case of my logs it appears to be a race 
condition, the task/container has already exited and it was trying to grab 
information. 

While this isn't causing task failure (its giving off a false message); in my 
case this seems to prevent the process from being moved from Active tasks to 
competed tasks. The only way I can get that to happen is by shutting down the 
slaves for longer then the slave time out. When this happens, the task (even if 
it had a status of finished before) gets marked as lost. So its giving off a 
lot of misinformation. 

I havn't been able to repo this as well in marathon, but my framework works 
more like Chronos (run a scheduled task in a container) so maybe that will be 
easier to repo with? 

> failed to determine cgroup for the 'cpu' subsystem
> --------------------------------------------------
>
>                 Key: MESOS-1837
>                 URL: https://issues.apache.org/jira/browse/MESOS-1837
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker
>    Affects Versions: 0.20.1
>         Environment: Ubuntu 14.04
>            Reporter: Chris Fortier
>            Assignee: Timothy Chen
>
> Attempting to launch Docker container with Marathon. Container is launched 
> then fails. 
> A search of /var/log/syslog reveals:
> Sep 27 03:01:43 vagrant-ubuntu-trusty-64 mesos-slave[1409]: E0927 
> 03:01:43.546957  1463 slave.cpp:2205] Failed to update resources for 
> container 8c2429d9-f090-4443-8108-0206ca37f3fd of executor 
> hello-world.970dbe74-45f2-11e4-8b1d-56847afe9799 running task 
> hello-world.970dbe74-45f2-11e4-8b1d-56847afe9799 on status update for 
> terminal task, destroying container: Failed to determine cgroup for the 'cpu' 
> subsystem: Failed to read /proc/9792/cgroup: Failed to open file 
> '/proc/9792/cgroup': No such file or directory



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to