Re: Cache Digest problems.

00000@life-gone-hazy.com> <20000810211858.24739.qmail@mp3.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <20000810211858.24739.qmail@mp3.com>; from Brian Degenhardt on Thu, Aug 10, 2000 at 09:
18:58PM -0000
Status: RO
Content-Length: 4619
Lines: 110

Requesting the cache digest from squid on some machines is totally broken
(see replies below).

I got some free time to see if I could squeeze out the reason why I'm
experiencing this behavior... here's some more details. I'm not done
investigating, but I was hoping somebody could help in pointing me to the
right direction:

I've taken two identical machines, with the exact same binary of squid and
the exact same installation of RedHat, and one machine will return it's
cache digest when asked for via HTTP, and one will not (see below).

Here's some debug log output:

Machine that works correctly
2000/08/23 16:19:49| redirectStart: 'http://foo.mp3.com:3128/squid-internal-periodic/store_digest'
2000/08/23 16:19:49| clientRedirectDone: 'http://foo.mp3.com:3128/squid-internal-periodic/store_dige
st' result=NULL
2000/08/23 16:19:49| clientInterpretRequestHeaders: REQ_NOCACHE = NOT SET
2000/08/23 oes not work
2000/08/23 16:42:14| redirectStart: 'http://bar.mp3.com:3128/squid-internal-periodic/store_digest'
2000/08/23 16:42:14| clientRedirectDone: 'http://bar.mp3.com:3128/squid-internal-periodic/store_dige
st' result=NULL
2000/08/23 16:42:14| 0x841d39c lookup for 33
2000/08/23 16:42:14| 0x841d39c lookup for 7
2000/08/23 16:42:14| 0x841d39c lookup for 48
2000/08/23 16:42:14| clientInterpretRequestHeaders: REQ_NOCACHE = NOT SET
2000/08/23 16:42:14| clientInterpretRequestHeaders: REQ_CACHABLE = SET
2000/08/23 16:42:14| clientInterpretRequestHeaders: REQ_HIERARCHICAL = SET
2000/08/23 16:42:14| clientProcessRequest: GET 'http://bar.mp3.com:3128/squid-internal-periodic/stor
e_digest'
2000/08/23 16:42:14| storeGet: looking up 75F7444243B5DC39C661CAF16D9BE01E
2000/08/23 16:42:14| clientProcessRequest2: storeGet() MISS
2000/08/23 16:42:14| clientProcessRequest: TCP_MISS for 'http://bar.mp3.com:3128/squid-internal-peri
odic/store_digest'

So it appears that squid has the cache digest in it's cache on one machinnna give
> out their cache digests when they are requested. It's weird, because when
> trying to access them, I either get a Forbidden error, or I get the
> following response:
>
> % telnet foobar.mp3.com 3128
> Trying XXX.XXX.XXX.XXX...
> Connected to foobar.mp3.com.
> Escape character is '^]'.
> GET /squid-internal-periodic/store_digest HTTP/1.0
>
> HTTP/1.0 404 Not Found
> Server: Squid/2.3.STABLE3
> Mime-Version: 1.0
> Date: Wed, 09 Aug 2000 23:12:58 GMT
> Content-Type: text/plain
> Content-Length: 45
> Last-Modified: Wed, 09 Aug 2000 23:12:58 GMT
> X-Cache: MISS from foobar
> X-Cache-Lookup: HIT from foobar:3128
> Connection: close
>
> This cache is currently building its digest.
> Connection closed by foreign host.
> %
>
> This is a machine that has been up for 3 weeks and the cache manager claims
> that a digest exists. The interesting thing is that this problem does not
> arise on a totally identical machine running the EXACT same binary of squid.
> I can provide a debug output if that wouo apply this patch:
> >
> > http://www.squid-cache.org/Versions/v2/2.3/bugs/#squid-2.3.stable4-ftp_icon_not_found
> >
> > Duane W.
> >
>

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html