Linh,
This resembles a bug. You might want to upgrade to the latest patch release.
Rohan
On Mon, 10 Dec 2012 12:30:48 -0500
"Khuu, Linh Contractor" wrote:
>Hello,
>
>Our named just crashed this morning. I looked into the log, and saw the
>following errors in the log. What is dst_api.c? Why d
Linh,
>From my personal experience - BIND have lots of such bugs.
Upgrade to the latest version (minor one - 9.8.4-P1, not 9.9.2) and see if
the error reappears.
If yes, report it to bind9-b...@isc.org (if the bug is not reproducible
anyway even on 9.8.3-P1, I'd report it too).
Alexander Gurvitz,
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
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)
> >
> 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
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
6 matches
Mail list logo
