You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2015/04/03 22:21:52 UTC

[jira] [Commented] (MESOS-1837) failed to determine cgroup for the 'cpu' subsystem

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

Timothy Chen commented on MESOS-1837:
-------------------------------------

Also my fix for MESOS-2583 should also address this ticket, as I avoid the need to do containerizer update after first launch since we set the resources when the container runs already. I'm going to mark this as resolved, please try the latest master and let me know if the issue is still happening.

> 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)