Simon at wretched.demon.co.uk
Wed Jun 19 00:13:10 UTC 2002
Óscar Zovo wrote:
> Hello there!
> I've a problem here. My BIND 9.2.1 server keep crashing after this error.
> task.c:395: REQUIRE((((task) != ((void *)0)) && (((const isc__magic_t *)(task))-
> >magic == ((('
> T') << 24 | ('A') << 16 | ('S') << 8 | ('K')))))) failed
> Jun 16 07:53:02 leopard named: exiting (due to assertion failure)
This is a check in the code for a valid task state, whether you
view it as a crash or a deliberate failure due to a condition
that shouldn't arise is a philosophical question.
> I'm running on a RH Linux 7.2
> I've found these errors on previous version of BIND.
> Can anyone help me with this?
If you don't have multiple CPU's disable thread on the compile.
This should bypass the problem. "./configure --disable-threads"
Since you are the first reporting here with a mainstream Linux
release my guess is you must have a wacky kernel, or some sort
of bizarre thread implementation..... Go on admit you fiddled
with something ;)
More information about the bind-users