I have a busy Squid 3.2.3 server that constantly has a huge number of connections tied up in CLOSE_WAIT (i.e. at the moment it has 364 ESTABLISHED but 3622 in CLOSE_WAIT).
tcp 1 0 ::ffff:172.23.3.254:8080 ::ffff:172.23.2.158:49615 CLOSE_WAIT 32303/(squid-1)
All of these sockets have an rx queue containing 1 byte. I'm aware that I can reduce client_lifetime, but I'm wondering if I have a more fundamental problem somewhere since Squid appears to not be flushing the queue. Can anyone cast any light onto this behaviour?
Other servers running various versions of Squid (including 3.2.3) don't seem to be exhibiting the problem to such an extent (I'm still seeing a number of CLOSE_WAIT sockets with an rx queue length of 1 on these servers, but in relatively small quantities.)
-- - Steve Hill Technical Director Opendium Limited http://www.opendium.com Direct contacts: Instant messager: xmpp:steve@xxxxxxxxxxxx Email: steve@xxxxxxxxxxxx Phone: sip:steve@xxxxxxxxxxxx Sales / enquiries contacts: Email: sales@xxxxxxxxxxxx Phone: +44-844-9791439 / sip:sales@xxxxxxxxxxxx Support contacts: Email: support@xxxxxxxxxxxx Phone: +44-844-4844916 / sip:support@xxxxxxxxxxxx
