Quoting Arie Skliarouk (sklia...@gmail.com):
I don't have the /cgroup directory mounted. Somehow, the directory is
mounted automatically onto the /sys/fs/cgroup
*root@mf:~# df | grep cgroup
cgroup12368328 0 12368328 0% /sys/fs/cgroup
root@mf:~# ls /sys/fs/cgroup/
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
On Dec 18, 2011 1:09 PM, Jérôme Petazzoni jerome.petazz...@dotcloud.com
wrote:
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 :-)
You should be able to
On 12/18/2011 11:56 AM, C Anthony Risinger wrote:
On Dec 18, 2011 1:09 PM, Jérôme Petazzoni
jerome.petazz...@dotcloud.com mailto:jerome.petazz...@dotcloud.com
wrote:
If that happens, just try to terminate the other processes running
in the cgroup, rename it (mv /cgroup/mylittlecontainer
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
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.
I had to rename the container
On Sun, 11 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
Hi,
Most of the time the lxc-destroy works properly, removing the cgroup with
the same name as the container.
Today something strange happened on one of my vservers - suddenly it
stopped responding to requests and any attempt to connect just hanged (as
if connection was successful, but no data
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
On Thu, Dec 8, 2011 at 14:05, Gordon Henderson gor...@drogon.net wrote:
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
On Thu, 8 Dec 2011, Arie Skliarouk wrote:
On Thu, Dec 8, 2011 at 14:05, Gordon Henderson gor...@drogon.net wrote:
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
11 matches
Mail list logo
