Re: [squid-users] DNS processes running out

13-Mar-02 at 09:32, philip.wolfe@centrelink.gov.au wrote :
> I'm getting the following error in cache.log:
>
> 2002/03/13 08:46:54| WARNING: All dnsserver processes are busy.
> 2002/03/13 08:46:54| WARNING: 15 pending requests queued
>
> The maximum the config says to run is 32, so how do you estimate what you
> need. Simple guess and see or is there a smarter way.

I would try increasing it anyway, conservatively, to about 20, and see if you
get this error again.

>
> Also, what part does the DNS server play in this and could it be causing a
> problem such as the DNS server not caching requests correctly?

Slow DNS response, whether it is caching or not, could be causing issues. If
your DNS server is taking too long to respond to each query, then you might
consider running a local caching-only nameserver on the squid box, or on the
same LAN. If you already have a DNS server on the same LAN, and it is
responding slowly to requests, troubleshoot that.

The queue in Squid will grow quickly if you have either high levels of traffic
or a slow DNS server, but this would be noticable in browsing performance
also.

There are all sorts of DNS tweaks - one thing that can improve performance is
to have a caching only server and a public server (with zones you are
authoritative for) separate, since public servers tend to get HUPped often
when changes are made, losing their cache.

-- 
|-Simon White               # GIMPS current unit progress: 38.19% #-|
|-Internet Services Manager # > http://www.mersenne.org/prime.htm #-|
|-MTDS S.A. 14, rue 16 novembre    :-Pd-;      tel: +212.3.737.4861-|
|-Rabat, Kingdom of Morocco      Cyberneckin'  fax: +212.3.737.4863-|