On Fri, Sep 13, 2013 at 6:53 PM, Petru Ghita <petru.gh...@gmail.com> wrote:
> Hello Fajar,
>
> What I'm doing as a workaround is to wait 10 seconds after a
> lxc-shutdown has completed.
The thing with that workaround, is it definitely don't work for an "init 6"
within the container
> This alleviates the problem as by that time
> it seems the network interfaces get almost always deleted.
The keyword is "almost" :)
> Nevertheless
> sometimes they don't and the following lxc-start won't work. I found so
> far, that a lxc-stop manages to get them deleted no matter what in those
> cases.
>
>
even lxc-stop didn't work in my case.
> I didn't report the problem myself because I wasn't able to reproduce
> it.
I was able to reproduce it every time, but only on the busy, production
container.
> My opinion on the issue is that it has something to do with CPU load
> rather than with network traffic.
>
> I'm running about 30 containers on production with a mix of services
> ranging from Zimbras to java application servers. The bug hits me while
> on a backup script that first turns off the containers.
>
>
Good to know it's not only me then :)
--
Fajar
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
