Issues with releases of 3.2 after squid-3.2.0.14-20120117-r11491

Hi,

I'm currently running a number of squid caches with
squid-3.2.0.14-20120117-r11491. Ignoring the issues fixed in
subsequent releases, everything is more or less o.k. However
attempting to install any subsequent releases have caused problems
ranging from "chunky" response to just basically not working. e.g

Platform 12 core Dell server running 64 bit ubuntu 10.43 LTS
operating system. IPv6 disabled in kernel as we don't run IPv6 at
present. Squid built with

#!/bin/bash
ulimit -SHn 49152
CFLAGS="-m64" ./configure --enable-snmp --enable-basic-auth-
helpers="PAM" --enable-cachemgr-hostname=wwwcache1-west.hull.ac.uk --
enable-htcp --enable-cache-digests --enable-async-io --prefix=/usr/
local/squid --with-pthreads --enable-removal-policies --enable-ssl --
disable-linux-netfilter -with-large-files --with-maxfd=49152 --with-dl
--enable-icmp --enable-poll --disable-ident-lookups --enable-truncate
--disable-delay-pools --disable-loadable-modules --disable-ipv6

Configuration has 12 worker processes each mapped to a cpu core.

In the config file I've disabled htcp as I initially had issues with
clustering 3.2 and 3.1 versions of squid.

With the above config 3.2.0.14...1491 works just fine. With the next
release up where squid is performing A and AAAA DNS queries
simultaneously I was getting seriously long delays before pages would
appear in a web browser. This was with 1 client running through squid.

With version 3.2.0.15, Even this doesn't work. everything seems to be
up and running, there are no strange errors in cache.log but the
browser just waits for pages to be served.

I then downloaded the latest patch release 3.2.0.15......11508 and
installed it on the test server. With this release, again everything
seemed ok and a browser connecting to squid would get the 1st page.
Any further attempts would result in a seriously long delay before
anything appeared in the browser. A netstat -a would show a connection
from the client to squid access.log would show nothing and then
eventually (sorry I've XML'ized the logs) something of the form shown
below.

<squid_rec source_ip="150.237.129.18" client_ip="-"
cache="150.237.85.197" time="1328683548.416"
real_cache="150.237.85.197"><source_ip>150.237.129.18</
source_ip><client_ip>-</client_ip><user_login>-</
user_login><user_ident>-</user_ident><user_name>-</
user_name><date_time>08/Feb/2012:06:45:48 +0000</
date_time><request_method>GET</request_method><url>http://www.mozilla.org/img/covehead/divider-notch.jpg
</url><protocol>HTTP/1.1</protocol><status_code>0</
status_code><reply_size>0</
reply_size><request_status>NONE_ABORTED:HIER_NONE</
request_status><response_time>22881</response_time></squid_rec>

The only thing that's changed is the release of squid used.

FWIW I've re-enabled ipv6 on the box and removed the --disable-ipv6
option from the configure to no avail.

Bit stuck as to what to look at next, any suggestions?
Rgds
Alex
Received on Wed Feb 08 2012 - 12:15:54 MST