9.3.0 coring on FreeBSD 5.3-STABLE

[Alex R]

It crashed again and I turned the log level up to 99 yet I can't see things
like queries or anything else at all. There is no crash information in
/var/log/messages either.

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf
Of Alex R
Sent: Friday, November 26, 2004 1:02 PM
To: comp-protocols-dns-bind at isc.org
Subject: RE: 9.3.0 coring on FreeBSD 5.3-STABLE

Nope no overclocking. The rest of the system runs perfectly as far as I =
can
see. I do not have any other corefiles around either. RAM is fine as =
well,
I've tested it using memtest86. I upped the logging using rndc trace 5 =
and
nothing suspicious has come up, but on the other hand it hasn=92t =
crashed yet.
It is really weird that sometimes it crashes twice daily and other times =
not
at all.

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On =
Behalf
Of phn at icke-reklam.ipsec.nu
Sent: Friday, November 26, 2004 8:54 AM
To: comp-protocols-dns-bind at isc.org
Subject: Re: 9.3.0 coring on FreeBSD 5.3-STABLE

Alex R <alex at deviousmeans.net> wrote:
> Before I had a problem with named coring on sighup. My solution to =
that
> problem was to use rndc reload. Now named keeps on coring sporadically
when
> I'm not doing anything besides using it for normal lookups. Where can =
I
look
> to start debugging this problem? Does named leave a core file =
anywhere?
Also
> I'm not sure if this has anything to do with it but it is a secondary =
DNS
> for the .lan zone I use internally on my home LAN.
> =20

Are your hardware really running ok ?   Overclocked ? Is there
any other corefiles around ( Yes means other programs also have trouble)





--=20
Peter H=E5kanson        =20
        IPSec  Sverige      ( At Gothenburg Riverside )
           Sorry about my e-mail address, but i'm trying to keep spam =
out,
	   remove "icke-reklam" if you feel for mailing me. Thanx.