BIND 9.14.1 assertion failure

[Havard Eidnes]

Hi,

we're running BIND 9.14.1 in a pretty much "standard"
configuration; this one instance does query forwarding but also
"forward first".

Today this one instance decided to exit, and in the log I find:

May 11 15:02:51 nnnn named[5567]: resolver.c:10515: REQUIRE(fetchp != ((void *)0) && *fetchp == ((void *)0)) failed, back trace
May 11 15:02:51 nnnn named[5567]: #0 0x41e7a8 in ??
May 11 15:02:51 nnnn named[5567]: #1 0x713bce612ad3 in ??
May 11 15:02:51 nnnn named[5567]: #2 0x713bcfaf4b67 in ??
May 11 15:02:51 nnnn named[5567]: #3 0x713bcfaf97e0 in ??
May 11 15:02:51 nnnn named[5567]: #4 0x713bcfafcf33 in ??
May 11 15:02:51 nnnn named[5567]: #5 0x713bcfafda80 in ??
May 11 15:02:51 nnnn named[5567]: #6 0x713bcfafe721 in ??
May 11 15:02:51 nnnn named[5567]: #7 0x713bce62d9a2 in ??
May 11 15:02:51 nnnn named[5567]: #8 0x713bcc40b8b5 in ??
May 11 15:02:51 nnnn named[5567]: #9 0x713bcc081b60 in ??
May 11 15:02:51 nnnn named[5567]: exiting (due to assertion failure)

The first entry is assertion_failed(), but the rest I can't
manage to decode, even after doing "b main" and "r", and as far
as I can see there's no core file to be found anywhere.

Any hints or what to look for?  This seems to be a quite
infrequent event; I beleive it had run for a few weeks before
deciding to act up.

Regards,

- Håvard