Re: named crashed (mem.c:1099: INSIST(ctx->stats[i].gets == 0U) failed)

2011-05-05 Thread Evan Hunt
On Thu, May 05, 2011 at 01:07:24PM -0700, Fr34k wrote: > Thanks Evan. > > Should the Community expect a BIND 9.7.3 train update/maintenance release > which, among other things, addresses this mem.c issue? There will be a 9.7.4 release fairly soon--the beta is in the pipeline already. 9.8.1 will

Re: named crashed (mem.c:1099: INSIST(ctx->stats[i].gets == 0U) failed)

2011-05-05 Thread Fr34k
2011 10:50:05 AM > Subject: Re: named crashed (mem.c:1099: INSIST(ctx->stats[i].gets == 0U) >failed) > > > daemon:crit named[221184]: mem.c:1099: INSIST(ctx->stats[i].gets == 0U) >failed > > daemon:crit named[221184]: exiting (due to assertion failure) > >

Re: named crashed (mem.c:1099: INSIST(ctx->stats[i].gets == 0U) failed)

2011-04-12 Thread Evan Hunt
> daemon:crit named[221184]: mem.c:1099: INSIST(ctx->stats[i].gets == 0U) failed > daemon:crit named[221184]: exiting (due to assertion failure) > > named restarted fine and running without any problem. Does anyone have > any idea why named crashed with these errors??? Is it a bug in bind?? > We'r

Re: named crashed (mem.c:1099: INSIST(ctx->stats[i].gets == 0U) failed)

2011-04-12 Thread Alan Clegg
On 4/12/2011 8:32 AM, Khuu, Linh Contractor wrote: > Last night, our named crashed with the following errors: > > daemon:crit named[221184]: mem.c:1099: INSIST(ctx->stats[i].gets == 0U) > failed > daemon:crit named[221184]: exiting (due to assertion failure) > > named restarted fine and runnin

named crashed (mem.c:1099: INSIST(ctx->stats[i].gets == 0U) failed)

2011-04-12 Thread Khuu, Linh Contractor
Hi, Last night, our named crashed with the following errors: daemon:crit named[221184]: mem.c:1099: INSIST(ctx->stats[i].gets == 0U) failed daemon:crit named[221184]: exiting (due to assertion failure) named restarted fine and running without any problem. Does anyone have any idea why named cra