Hi,
We observed the named crash with an assertion failure.
This happend only once, and backtrace says it is corrupted stack. Named
daemon starteda again by itself after this. And no crash was seen after
this.
Version I am using is : bind-9.7.1
Backtrace:
#0 0xb729789f in raise () from /lib/libc.so.6
#1 0xb729aacc in abort () from /lib/libc.so.6
#2 0x080684f4 in assertion_failed (file=0xb75402b5 "mem.c", line=1094,
type=isc_assertiontype_insist,
cond=0xb75405f7 "ctx->stats[i].gets == 0U") at ./main.c:211
#3 0xb7501f77 in isc_assertion_failed () from /usr/lib/libisc.so.60
#4 0x00000446 in ?? ()
#5 0x00000002 in ?? ()
#6 0xb75405f7 in ?? () from /usr/lib/libisc.so.60
Logs:
======
crit named[4294]: mem.c:1094: INSIST(ctx-stats[i].gets == 0U) failed
crit CLA-0 named[4294]: exiting (due to assertion failure)
Question:
Is there any known issue for this.
If yes, can someone please provide the link where I can get the patch.
>From the code browsing I can make this assertion failure happend in the
destroy function(), why the named daemon wants to exit itself, is something
unexpected happend? While it is exiting, named is cleaning up all its
structures and stats, can someone explain me why we need assertion before
freeing up the stats?
As I am new to this domain, sorry in advance if I have asked some silly
questions.
-Bhargav
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
