[Lxc-users] lxc_cgroup start error

[Christoph Mitasch]

yes, I was rebooting the server each time.

Christoph

----- Original Message -----
From: "Serge Hallyn" <serge.hallyn at canonical.com>
To: "Christoph Mitasch" <cmitasch at thomas-krenn.com>
Cc: lxc-users at lists.sourceforge.net
Sent: Monday, August 27, 2012 3:34:40 PM
Subject: Re: [Lxc-users] lxc_cgroup start error

Quoting Christoph Mitasch (cmitasch at thomas-krenn.com):
> thanks for the fix.
> 
> I tried multiple times with the new package. After approx. 10 tries I got the same error again.

Rebooting each time, or not?  If not rebooting, then it is not related
to what this was trying to fix.

> root:~# date +%s
> 1345919455
> root:~# cat /var/run/resource-agents/res_lxc_3.log 
>       lxc-start 1345919348.053 ERROR    lxc_cgroup - File exists - failed to create '/sys/fs/cgroup/perf_event//lxc' directory
>       lxc-start 1345919348.053 ERROR    lxc_start - failed to spawn 'test3'
>       lxc-start 1345919348.341 ERROR    lxc_cgroup - No such file or directory - failed to remove cgroup '/sys/fs/cgroup/perf_event//lxc/test3'
> root:~# dpkg -l | grep lxc
> hi  lxc                              0.7.5-3ubuntu63~ppa1       Linux containers userspace tools
> 
> Regards,
> Christoph
> 
> ----- Original Message -----
> From: "Serge Hallyn" <serge.hallyn at canonical.com>
> To: "Christoph Mitasch" <cmitasch at thomas-krenn.com>
> Cc: lxc-users at lists.sourceforge.net
> Sent: Friday, August 24, 2012 6:13:47 PM
> Subject: Re: [Lxc-users] lxc_cgroup start error
> 
> Quoting Christoph Mitasch (cmitasch at thomas-krenn.com):
> > Thanks for clarification. I currently have two containers and so a race condition is very probable.
> > 
> > Can I help with testing something or is it already ready to be fixed?
> 
> If you're running Ubuntu precise (12.04) or quantal (12.10), I've pushed
> a proposed fix to ppa:ubuntu-virt/ppa.  It should build soon, then you
> can
> 
> 	sudo add-apt-repository ppa:ubuntu-virt/ppa
> 	sudo apt-get update
> 	sudo apt-get dist-upgrade
> 
> and you should have the new version.  If you still get the error with
> that package, then (a) I won't push my fix upstream, and (b) I don't
> know what the problem is :)
> 
> thanks,
> -serge