Date: Thu, 20 Jun 2013 15:48:17 +0200 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> To: Jeremie Le Hen <jlh@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: Panic with RACCT on a jailed process Message-ID: <ED0BA8E7-8F3D-4878-9C70-7631DA275428@FreeBSD.org> In-Reply-To: <20130618220824.GA11548@caravan.chchile.org> References: <20130618220824.GA11548@caravan.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Wiadomość napisana przez Jeremie Le Hen <jlh@FreeBSD.org> w dniu 19 cze 2013, o godz. 00:08: > Hi, > > I've been bit by a panic three times over the last month. > > I'm currently running: > FreeBSD obiwan.piupiu.local 10.0-CURRENT FreeBSD 10.0-CURRENT #7 r251519: Sun Jun 9 22:37:09 CEST 2013 root@obiwan.piupiu.local:/usr/obj/usr/src/sys/OBIWAN amd64 > > The panic message is: > panic: destroying non-empty racct: 1007616 allocated for resource 4 > > I quicky tried to track this down, but in half an hour I didn't get very > far. Resource 4 is RACCT_RSS. The faulty process seems to be 66555 > which looks like a 32-bits cron(8) running in a jail. I've seen a similar report in the past, but I was unable to figure out what could be causing this. Do you have a way to figure out exactly what cron job causes this? Also, could you try a workaround of adding any kind of rctl rule for that user (this will cause the uidinfo to be "held" by the rctl rule, so uifree() won't try to destroy its racct), e.g. "user:XXX:maxproc:log=1000000000", and see if it panics in some other place? Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ED0BA8E7-8F3D-4878-9C70-7631DA275428>