Re: trouble with cache digests

Alex,

Thanks for the feedback.

Checked that they know eachother consistently. They do.

Checked the proxy1 has a digest using cachemgr, it shows

Local Digest:
store digest: size: 2618182 bytes
          entries: count: 1383662 capacity: 4189090 util: 33%
          deletion attempts: 0
          bits: per entry: 5 on: 4863896 capacity: 20945456 util: 23%
          bit-seq: count: 7467746 avg.len: 2.80
          added: 1383662 rejected: 3159551 ( 69.54 %) del-ed: 0
          collisions: on add: 0.06 % on rej: 0.06 %

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-*/*

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?

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

Appreciate any help you can give me.

jm
Received on Thu Jun 08 2000 - 16:28:31 MDT