Re: [squid-users] Squid is not caching much

On 28 Feb, 2005, at 14:25, Merton Campbell Crockett wrote:

> On Mon, 28 Feb 2005, Robert Borkowski wrote:
>
>> James Stocks wrote:
>>> I've installed Squid on OS X 10.3, I'm trying to use it to cache
>>> large
>>> files (mainly stuff like OS updates). The problem is that according
>>> to
>>> store.log, everything seems to be released from the cache straight
>>> away:
>>>
>>> 1109458635.046 RELEASE -1 FFFFFFFF 5190EC019A89E3FF32D62D1693A09C7E
>>> 200
>>> 1109458630 1107797158 -1 application/octet-stream
>>> 6946727/194984
>>> GET http://ftp.plig.net/pub/apache/dist/httpd/httpd-2.0.53.tar.gz
>>> 1109460094.435 RELEASE -1 FFFFFFFF E2F545F6D2407B81FB35E1FF0140886F
>>> 200
>>> 1109459923 1107797158 -1 application/octet-stream
>>> 6946727/6946727
>>> GET http://ftp.plig.net/pub/apache/dist/httpd/httpd-2.0.53.tar.gz
>>>
>>> This is my squid.conf:
>>>
>>> cache_effective_user squid
>>> cache_effective_group squid
>>> http_port 192.168.0.81:3128
>>> http_port 127.0.0.1:3128
>>> cache_mgr cache@stocksy.co.uk
>>> visible_hostname stocksy.is-a-geek.com
>>> cache_dir ufs /usr/local/squid/var/cache 7000 16 256
>>> cache_swap_low 90
>>> cache_swap_high 95
>>> maximum_object_size 2097152 KB
>>> cache_mem 32 MB
>>> refresh_pattern -i \.gz$ 4320 100% 43200 reload-into-ims
>>> override-expire
>>> override-lastmod ignore-reload
>>> refresh_pattern . 0 20% 4320
>>> cache_log /usr/local/squid/var/logs/cache.log
>>> cache_access_log /usr/local/squid/var/logs/access.log
>>> cache_store_log /usr/local/squid/var/logs/store.log
>>> logfile_rotate 4
>>> acl All src 0/0
>>> acl Manager proto cache_object
>>> acl Localhost src 127.0.0.1/32
>>> acl Safe_ports port 80 21 443 563 70 210 280 488 591 777 1025-65535
>>> acl SSL_ports port 443 563
>>> acl CONNECT method CONNECT
>>> acl SpruceWayNetwork src 192.168.0.0/24
>>> http_access allow Manager Localhost
>>> http_access deny Manager
>>> http_access deny !Safe_ports
>>> http_access deny CONNECT !SSL_ports
>>> http_access allow SpruceWayNetwork
>>> http_access deny All
>>>
>>> I googled for similar problems, the only solutions I found were that
>>> the
>>> cache wasn't writable (I did 'chown -R squid:squid
>>> /usr/local/squid') or
>>> that the cache_swap_low was higher than cache_swap_high (which it
>>> isn't).
>>> I also increased the maximum_object_size to 2097152 KB.
>>>
>>> Many thanks,
>>> James Stocks.
>>>
>>>
>>>
>>
>> The FFFFFFFF in the store.log means the memory object was released.
>> Squid puts incoming objects into memory, swaps them out to disk, and
>> the if
>> the object is larger than the tunable maximum_object_size_in_memory'
>> it
>> releases the memory object. OS updates tend to be bigger than the 8
>> KB default
>> for this.
>>
>> Is there a SWAPOUT line for that same object?
>
> You might want to check with Apple. They may have set the updates to
> be
> non-cacheable. Some updates are only available to users with a current
> support contract.
>
> Merton Campbell Crockett
>
>
> --
> BEGIN: vcard
> VERSION: 3.0
> FN: Merton Campbell Crockett
> ORG: General Dynamics Advanced Information Systems;
> Intelligence and Exploitation Systems
> N: Crockett;Merton;Campbell
> EMAIL;TYPE=internet: mcc@CATO.GD-AIS.COM
> TEL;TYPE=work,voice,msg,pref: +1(805)497-5045
> TEL;TYPE=work,fax: +1(805)497-5050
> TEL;TYPE=cell,voice,msg: +1(805)377-6762
> END: vcard
>
>

I found that for some reason running squid as nobody:wheel and changing
the ownership of squid/var accordingly seems to have sorted it, along
with a few refresh_pattern lines.

Thanks again,
James.
Received on Mon Feb 28 2005 - 10:14:11 MST