strange core dump

Markus Stumpf maex-bind-users at Space.Net
Sun Sep 19 02:48:35 UTC 1999


Today morning our watchogs complained that two of our DNS servers
had died. I am still running 8.1.2 on both of them, but I am curious
if anyone has seen this before, if it is kind of an exploit? What
puzzles me is that they both died within 10 seconds.

I have checked the logfiles and all I have found were two lines in each
servers logfiles.  The core dumps are kinda useless, as I don't
have debugging code/symbols in the binaries.

The two lines said:

Sep 18 07:10:09 fano named[3867]: ns_main.c:672: INSIST(evRead(lev, rfd, &iov, 1, stream_getlen, sp, &sp->evID_r) != -1): Invalid argument failed.
Sep 18 07:10:16 fano /kernel: pid 3867 (named), uid 0: exited on signal 6 (core dumped)

Sep 18 07:10:18 kronecker named[26222]: ns_main.c:672: INSIST(evRead(lev, rfd, &iov, 1, stream_getlen, sp, &sp->evID_r) != -1): Invalid argument failed.
Sep 18 07:10:44 kronecker /kernel: pid 26222 (named), uid 0: exited on signal 6 (core dumped)

Times are GMT+2 (ntp synched)
The two nameservers are mainly used by our customers, one of them (fano
aka ns2.space.net) does not even show up publically, e.g. in zone files
(kronecker is ns.space.net).
Two others (ns3.dns.space.net and ns4.dns.space.net) had no problems.
All four DNS servers run exactly the same setup, zones and version.

Thanks for any info

	\Maex

P.S. And yes, I will upgrade as soon as 8.2.2-R is out ;-))

-- 
SpaceNet GmbH             |   http://www.Space.Net/   | Yeah, yo mama dresses
Research & Development    | mailto:maex-sig at Space.Net | you funny and you need
Joseph-Dollinger-Bogen 14 |  Tel: +49 (89) 32356-0    | a mouse to delete files
D-80807 Muenchen          |  Fax: +49 (89) 32356-299  |


More information about the bind-users mailing list