Re: trouble with cache digests

On Thu, 8 Jun 2000, Jon Mansey wrote:

> It seems that proxy1 is not serving anything out of its squid-internal space
>
> $grep squid-internal access.log
> 960501394.122 6 <host1> TCP_MISS/400 50 GET
> http://proxy1.interpacket.net:3128/squid-internal-dynamic/netdb -
> NONE/- -
> 960501470.388 1 <host2> TCP_MISS/404 1385 GET
> http://proxy1.interpacket.net:3128/squid-internal-periodic/store_digest
> - NONE/- -
> 960501599.293 1 <host3> TCP_MISS/400 50 GET
> http://proxy1.interpacket.net:3128/squid-internal-dynamic/netdb -
> NONE/- -
> 960501604.685 1 <host4> TCP_MISS/400 50 GET
> http://proxy1.interpacket.net:3128/squid-internal-dynamic/netdb -
> NONE/- -
>
> It generates a 40x code for any request to squid-internal-*/*

Hmm. Sorry, I am out of ideas then.
 
> Ive scoured the config files and www lists for info on this and
> turned up nothing. I have other squiden working just fine, same
> version, same OS, same HW.
>
> Where is this squid-internal-* space on the file system? or is it
> only in memory?

There is not special place. Internal objects are stored as any other Web
object as far as dataplacement is concerned.

> Would this have anything to do with transparent or non-transparent use of ipfw?

Internal objects are accessed via port 3128 so transparency should not
be an issue, I think. I am not sure though.

Hopefully others have better ideas on how to help you.

Alex.
Received on Thu Jun 08 2000 - 22:12:56 MDT