Okay. I've got a reproducible problem. Hard to pin down, exactly.
DNS lookups with the internal DNS system are the problem.
Example: The installation I have will not look up www.mozilla.org
(possibly because it's a CNAME, though I shouldn't think that that alone
is the problem). My wife reports that browsing some sites, she will be
chugging along quite well for a while, then suddenly squid claims that
the site name cannot be resolved....This is after perhaps fifteen
minutes and several dozen objects being fetched from that name. This
implies a problem with the internal DNS cache(? Or that the name expired
from the cache and the subsequent lookup failed).
Squid 2.3devel3, linux 2.2.10-ac10.
I'm using this box as my primary gateway, and squid test-bench.
2.2stable has done well, with no problems. I've temporarily replaced it
with 2.3devel3 for the purposes of bug-hunting and testing.
There also appear to be some inordinate delays in looking some names up.
Minutes sometimes.
Async-io, poll enabled. More information and tests available on request.
There is one small modification to the source: Referer is substituted
with the url actually being requested. This allows some of my personal
links and comics pages to work with servers that would rather not be
deep-linked. I don't consider this modification (two lines) to be
associated with this problem.
I can open up a src acl for anyone that would like to verify the
behaviour. The box is moderately well-connected.
D
Received on Thu Nov 11 1999 - 19:01:44 MST
This archive was generated by hypermail 2.2.0 : Wed Apr 09 2008 - 12:01:56 MDT