bind-9.9.3-P2 exit(s) due to assertion failure

Evan Hunt each at isc.org
Mon Dec 2 17:28:10 UTC 2013


On Mon, Dec 02, 2013 at 04:57:15PM +0100, Harald A. Irmer wrote:
> 2 named exits cause due to assertion failure:
> 
> 01-Dec-2013 00:57:01.855 general: critical: zt.c:166: REQUIRE((((zt) != 
> ((void *)0)) && (((const isc__magic_t *)(zt))->magic == ((('Z') << 24 | 
> ('T') << 16 | ('b') << 8 | ('l')))))) failed
> 01-Dec-2013 00:57:01.855 general: critical: exiting (due to assertion 
> failure)
> 
> 01-Dec-2013 01:15:08.270 general: error: mem.c:1918: unexpected error:
> 01-Dec-2013 01:15:08.270 general: error: isc__mempool_destroy(): mempool 
> disp_sepool leaked memory
> 01-Dec-2013 01:15:08.270 general: critical: mem.c:1923: 
> REQUIRE(mpctx->allocated == 0) failed
> 01-Dec-2013 01:15:08.270 general: critical: exiting (due to assertion 
> failure)

Hello Harald,

Neither of those assertions look familiar to me, but it would probably be
worthwhile upgrading to the most recent version (9.9.4-P1); it addressed
some race conditions that might possibly account for them.

Meantime, it's best to send bug reports to bind9-bugs at isc.org. If you
can include stack backtraces for the crashes (either from the log or
from the core file, if any), that would be helpful.

-- 
Evan Hunt -- each at isc.org
Internet Systems Consortium, Inc.


More information about the bind-users mailing list