Hi Brian,
> If you don't have any particular need for 9.2.1 features then you
could go
> back to 8.3.1.
Yes, but I am afraid of the version 8.3.1 vulnerabilities !
Somebody wrote the following:
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.
If you don't have multiple CPU's disable thread on the compile.
This
should bypass the problem. "./configure --disable-threads"
(IIRC)
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
;)
Thanks and regards
Jose
----- Original Message -----
Sent: Wednesday, June 19, 2002 10:51 AM
Subject: Re: Named exiting due to assertion failure
> On Wed, Jun 19, 2002 at 08:43:06AM +0100, Jose Pereira
Van-Dunem wrote:
> > I am running Red Hat Linux 7.2.
> > I
have installed the BIND 9.2.1 package. After that, at least 5 times
a
> > day, the Named exit due to assertion failure!
> > In the
/var/log/messages file i can read the following error message:
> >
> > 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[30712]: exiting (due to assertion failure)
>
> You are not alone. A quick search of the archives at www.isc.org finds:
>
> http://marc.theaimsgroup.com/?l=bind9-users&m=101766924603879&w=2
>
http://marc.theaimsgroup.com/?l=bind9-users&m=101765494426329&w=2
>
> Unfortunately following the list threads doesn't seem to show
any
> resolution.
>
> If you don't have any particular need
for 9.2.1 features then you could go
> back to 8.3.1.
>
>
B.