[Lxc-users] lxc-destroy does not destroy cgroup
Jérôme Petazzoni
jerome.petazzoni at dotcloud.com
Sun Dec 18 19:06:43 UTC 2011
Hi Arie,
Glad to hear that you could fix this!
Otherwise, it can happen sometimes that a cgroup is stuck with
unkillable processes.
It can be annoying because you can't remove the cgroup, so if you want
to start a new one with the same name, you might think you have to reboot.
If that happens, just try to terminate the other processes running in
the cgroup, rename it ("mv /cgroup/mylittlecontainer /cgroup/broken")
and restart it.
This saved me a few reboots already :-)
Cheers,
On 12/18/2011 10:24 AM, Arie Skliarouk wrote:
> I am sorry, the problem was on my side - did a syntax mistake in the
> lxc.conf.
> Disregard my previous message and continue the good job you are doing! :)
>
> --
> Arie
>
>
>
> On Sun, Dec 18, 2011 at 18:19, Arie Skliarouk <skliarie at gmail.com
> <mailto:skliarie at gmail.com>> wrote:
>
> What could be worse than a cgroup is not deleted by lxc-destroy?
> Why, inability to create a cgroup using lxc-create!
>
> Seriously, the host machine can not start vservers anymore. This
> is after one of the cgroups got stuck in the unremovable state.
>
> With these issues it becomes harder and harder for me to justify
> LXC to my boss...
>
> --
> Arie
>
>
> On Tue, Dec 13, 2011 at 00:01, Serge Hallyn
> <serge.hallyn at canonical.com <mailto:serge.hallyn at canonical.com>>
> wrote:
>
> Quoting Gordon Henderson (gordon at drogon.net
> <mailto:gordon at drogon.net>):
> > On Thu, 8 Dec 2011, Arie Skliarouk wrote:
> >
> > > When I tried to restart the vserver, it did not came up.
> Long story short,
> > > I found that lxc-destroy did not destroy the cgroup of the
> same name as the
> > > server. The cgroup remains visible in the
> /sys/fs/cgroup/cpu/master
> > > directory. The tasks file is empty though.
> >
> > And just now, I've had the same thing happen - a container
> failed to
> > start and it left it's body in /cgroup - with empy tasks.
>
> The patch I sent out on Friday should help handle that more
> gracefully -
> it moves the cgroup out of the way so a new container can
> start. You'll
> need to clean the old one up by hand if you care to, though
> lxc could
> easily provide a tool to clean it up (and move and analyze any
> tasks left
> running in the cgroup, though I suspect in most cases there
> are none).
>
> -serge
>
> ------------------------------------------------------------------------------
> Learn Windows Azure Live! Tuesday, Dec 13, 2011
> Microsoft is holding a special Learn Windows Azure training
> event for
> developers. It will provide a great way to learn Windows Azure
> and what it
> provides. You can attend the event by watching it streamed
> LIVE online.
> Learn more at http://p.sf.net/sfu/ms-windowsazure
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> <mailto:Lxc-users at lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/lxc-users
>
>
>
>
>
> ------------------------------------------------------------------------------
> Learn Windows Azure Live! Tuesday, Dec 13, 2011
> Microsoft is holding a special Learn Windows Azure training event for
> developers. It will provide a great way to learn Windows Azure and what it
> provides. You can attend the event by watching it streamed LIVE online.
> Learn more at http://p.sf.net/sfu/ms-windowsazure
>
>
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20111218/6cdaef2b/attachment.html>
More information about the lxc-users
mailing list