From owner-freebsd-questions Mon Apr 16 15:45: 3 2001 Delivered-To: freebsd-questions@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [200.52.207.52]) by hub.freebsd.org (Postfix) with ESMTP id AAFD137B422 for ; Mon, 16 Apr 2001 15:45:00 -0700 (PDT) (envelope-from lcroker@unix.megared.net.mx) Received: from localhost (lcroker@localhost) by unix.megared.net.mx (8.11.0/8.11.0) with ESMTP id f3GLeHJ00577; Mon, 16 Apr 2001 16:40:17 -0500 (CDT) (envelope-from lcroker@unix.megared.net.mx) Date: Mon, 16 Apr 2001 16:40:16 -0500 (CDT) From: Lu!s Croker To: Flemming =?iso-8859-1?Q?Fr=F8kj=E6r?= Cc: questions@FreeBSD.ORG Subject: Re: Bind is Dying In-Reply-To: <4.1.20010416151348.00a819c0@sleipner.eiffel.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When your Bind is dying like the log shows, your system could be on attacks for bind... You should update to 8.2.3 version. Sorry.. my English is bad yet. =20 On Mon, 16 Apr 2001, Flemming [iso-8859-1] Fr=F8kj=E6r wrote: > Date: Mon, 16 Apr 2001 15:31:21 -0700 > From: "Flemming [iso-8859-1] Fr=F8kj=E6r" > To: questions@FreeBSD.ORG > Subject: Bind is Dying >=20 > I have 3 different DNS servers. All are running FreeBSD 4.2 > 1 is using a GENERIC kernel, the 2 others are custom. They are also fierw= all's > >From time to time, maybe ones a week one or more of the DNS servers will= die. >=20 > This is from the log files on the 2 servers. > Apr 15 13:43:33 dns1 /kernel: pid 55479 (named), uid 53: exited on signal= 11 >=20 > Apr 15 14:48:17 uriha /kernel: pid 13646 (named), uid 53: exited on signa= l 6 >=20 > How can i find out who is sending these signals, and who can i Stop them? >=20 > \Flemming >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message