Re: [squid-users] DNS processes running out

Hi Henrik,

We have greater than version 2.3, so I don't believe this is Squid's
fault. Our BIND is old and will be upgrading soon and I strongly believe
this is the problem. We also don't use the internal dns either.

Why would a newer version of Squid use so many more dsnserver processes
than an older version?

Henrik Nordstrom <hno@marasystems.com>
Sent by: hno@marasystems.com
26/03/2002 23:26

 
        To: philip.wolfe@centrelink.gov.au
        cc: squid-users@squid-cache.org
        Subject: Re: [squid-users] DNS processes running out

You either have a very high load, or your DNS servers is really slow.

If load is your problem, consider upgrading to a more recent Squid
version using a new improved internal DNS resolver (i.e. Squid-2.3 or
later), and don't compile Squid with --disable-internal-dns.

Regards
Henrik Nordström
Squid Developer

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
> 2002/03/13 08:46:54| Consider increasing the number of dnsserver
> processes in your config file.
> 2002/03/13 08:46:56| dnsSubmit: queue overload, rejecting
> www.auscap.com.au
> 2002/03/13 08:46:56| dnsSubmit: queue overload, rejecting
> www.gippstafe.vic.edu.au
>
> Fair enough, but I'm already running:
>
> dns_children 15
>
> 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.
>
> 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?
>
> Cheers.
Received on Wed Mar 27 2002 - 15:34:03 MST