djbdns
[Top] [All Lists]

Re: dnscache stopped responding

To: dns@list.cr.yp.to
Subject: Re: dnscache stopped responding
From: Jeff King <peff@peff.net>
Date: Wed, 3 Jan 2007 02:42:02 -0500
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-djbdns@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list dns@list.cr.yp.to
In-reply-to: <19a9fd170701021714l37a14b4cs619d6567a5a94c10@mail.gmail.com>
Mail-followup-to: dns@list.cr.yp.to
Mailing-list: contact dns-help@list.cr.yp.to; run by ezmlm
References: <19a9fd170701021714l37a14b4cs619d6567a5a94c10@mail.gmail.com>
On Tue, Jan 02, 2007 at 08:14:56PM -0500, John (yt) Hogenmiller wrote:

> Basically, as near as I can tell, dnscache is refusing dns requests.
> I may be wrong in this assumption, but I've reached the end of my
> knowledge, and the end of any pertinent list archives I've been able
> to find on the subject.  I turn to the list for further information.

What does "svstat /service/dnscache" say? Have you tried running strace
against the hung dnscache to see what it's doing?

> Immediately after restarting dnscache, I get a timeout.  After a few
> seconds, I get connection refused.  Netstat -nl shows dnscache

I don't see how dnscache could produce a refused connection unless it
closed port 53, which it never does. It sounds like it might be
terminating and getting restarted by svscan (the svstat above will tell
us that).

> root@primus_ip 0%: sudo /usr/local/etc/rc.d/services.sh restart
> Restarting services:  axfrdns dnscache tinydns.

Although here it looks like you might not be running svscan. What's in
services.sh?

-Peff

<Prev in Thread] Current Thread [Next in Thread>