On Mon, Jan 21, 2013 at 9:20 PM, Dan Kegel <d...@kegel.com> wrote: > Fairly often, when the container is coming up after being restarted, > it stays up for only a second or two, then goes down again, > and then finally stays up for good.
Once again, I am an idiot operating dangerous machinery. The telltale sign was that SIGTERM. Any time you see a strange SIGTERM on something being run under upstart, go check your upstart script, and you'll probably find that the 'stop on' clause is too broad. I had fixed this on the outer upstart, but the upstart inside the lxc container also needed to be more specific about when to stop. With both fixed, it's survived one build cycle of 9 builders on three slaves, which wasn't common before. Onwards, and sorry for the noise. - Dan ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
