Re: [squid-users] ubuntu apt-get update 404

Matthew Morgan wrote:
> Are there any known issues with squid 3.x and apt-get update on Ubuntu?
> On 2.7 everything worked fine, but on 3.0-stable19 and 3.0-stable20, I
> get random 404 responses when doing apt-get update. I tried starting
> with a fresh cache, but no dice. Here's my squid.conf:
>
> visible_hostname proxy
> http_port 192.168.2.1:3128 transparent
> snmp_port 3401
> acl all src all

If that is actually in your squid.conf remove it.

> acl manager proto cache_object
> acl localhost src 127.0.0.1/32
> acl to_localhost dst 127.0.0.0/8
> acl snmppublic snmp_community public
> acl localnet src 192.168.1.0/24 # RFC1918 possible internal network
> acl localnet src 192.168.2.0/24

> acl CONNECT method CONNECT
> http_access allow manager localhost
> http_access deny manager

> http_access allow purge

The above line makes the next two useless...

> http_access allow purge localhost
> http_access deny purge

> http_access deny !Safe_ports
> http_access deny CONNECT !SSL_ports
> http_access allow localnet
> http_access allow localhost
> http_access deny all
> icp_access allow localnet
> icp_access deny all

> http_port 192.168.2.1:3128

You have this http_port 192.168.2.1:3128 attempting to open twice. Once
with and once without a NAT lookups required.

> hierarchy_stoplist cgi-bin ?
> cache_dir diskd /usr/local/squid/var/cache2 15000 16 256

Not exactly the fastest disk IO method. On Linux its better to use AUFS.

> client_persistent_connections off
> server_persistent_connections off

Which means squid must open a new TCP link for every single request
fetched. This will be slowing things down a fair amount.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
   Current Beta Squid 3.1.0.14