DNS exiting

J.B. LaRue jb.larue at mila.com
Mon Mar 20 23:03:21 UTC 2000


Sorry - I was in too much of a hurry to get this out...

The machine is an IBM Aptiva, P100, with 64Mb RAM, IDE 1Gb HD, Running
FreeBSD 2.2.5 - Running ISC Bind 8.2.1

There weren't any messages in /var/log/messages pertaining to the
shutdown.


>     >> It seems like once a week, named dies: pid82 (named), uid0:
>     >> exited on signal 11
>
>     >> and today I got a core dump. The TTL is set to 86400 (default,
>     >> I think), but it shouldn't crap out like this, should it? It's
>     >> only been doing this for the last three weeks, or so. I restart
>     >> the process and everything runs fine for the week.
>
>     >> Appreciate any info...
>
> It would have helped if you'd give information like the OS platform or
> what version of name server code you were running and, more
> importantly,what messages were printed in the logs prior to the name
> server croaking.
>
> The name server does not make a habit of dying as a general
> rule. Signal number 11 is a segmentation violation. This is usually
> generated by an illegal memory reference - like following an incorrect
> pointer. In general the name server doesn't do this. Can you correlate
> the crash to some other DNS activity - like something sending a
> specific query or malformed packet to the name server? Or could it
> just be that your name server is hitting an OS default on the amount
> of VM that a process can use?
>
> If you're not running up to date name server code, upgrade. I doubt if
> anyone cares if there *might* be a pointer bug in obsolete DNS code.

--
^^^^^^^^^^^^^^^^^^^^^^^
J.B. LaRue - I.T. Manager
jb.larue at mila.com
888.340.4347
^^^^^^^^^^^^^^^^^^^^^^^





More information about the bind-users mailing list