Re: [squid-users] Squid 3.1 rejecting connections after few thousands requests

[alter...@gmail.com]

> Wow. Sure thats hits/sec and not hits/minute?
> The 'extreme' setups of Squid-2.7 only reached 990req/sec.



I'm running squid3.0 on Dell R300 servers with 4x2.8GHz Intel Xeons and 12GB of 
ram. On production servers I'm getting 
max 1500hits/s. With 2500hits/s I have seen that some in access.log, in elapsed 
column that some requests were closed 
after 6 seconds and average was something like ~300ms. It's not acceptable for 
me. Most requests on production servers 
are closed in less than 1ms.



>FWIW; the only other occurrence of this particular "Select loop Error" 
>reported in recent years was found to be due to 
broken NIC drivers.
>The behaviour sounds very much like some such bug has been hit, or maybe a 
>limit on the open ports per IP. 


I will search for something about nic drivers on FreeBSD maillists. As I said 
before squid3.0 was running fine for few 
hours, everytime I launched squid3.1 it lasted only few seconds. There is no 
firewall configured on this machine.  


Could anyone give me some pointers about debugging newest squid to see what is 
causing that squid immediately closes 
connections? 

[squid-users] Squid 3.1 rejecting connections after few thousands requests

[alter...@gmail.com]

Hi, I've run into problems after upgrading 3.0.STABLE19 (installed from 
packages) to squid 3.1
I'm running amd64 8.0-RELEASE FreeBSD, with squid as accelerated proxy.

3.0.STABLE19 runs almost flawlessly. I'm getting 'Select loop Error' every 
second:
2010/05/21 14:37:34| Select loop Error. Retry 1

and these errors once in a while in my cache.log:
2010/05/21 14:39:14| comm_old_accept: FD 14: (53) Software caused connection 
abort
2010/05/21 14:39:14| httpAccept: FD 14: accept failure: (53) Software caused 
connection abort


I've never ran in such problems on Debian Squeeze (also with squid3.0), so I 
really don't know if I could ignore them. 
I have successfully tested 3.0.STABLE19 on FreeBSD with 2500hits/s 


After a while I tried to upgrade to the newest version of squid I've tried 
squid-3.1.3 from ports, and squid-3.1.0.13 
from packages. Both versions after handling few thousands of requests are 
stopping serving on specified port.

Here is my configuration squid listens on 2 ports:

netstat -an |grep LISTEN
tcp4   0  0 *.8080 *.*LISTEN
tcp4   0  0 *.80   *.*LISTEN

'All' request goes to :8080, I configured port :80 only for testing. After few 
thousands of requests to :8080, squid stops 
handling requests coming from that port. If I telnet to :8080 my connection is 
closed instantly, but If i send request to 
:80 everything is fine.

Here are excerpts from cache.log, after I saw that squid doesn't serve anything 
I stopped it:
2010/05/20 12:09:56| Preparing for shutdown after 7460 requests
2010/05/20 13:00:19| Preparing for shutdown after 8843 requests
2010/05/21 14:10:37| Preparing for shutdown after 9963 requests

While trying two 3.1 versions of squid I also saw 'Select loop Error. Retry 1'