Quoting Gordon Henderson (gor...@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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
