Re: [squid-users] ERROR: Collapsed forwarding queue overflow for kid2 at 1024 items

On 05/24/2016 02:32 PM, Amos Jeffries wrote: > On 25/05/2016 5:46 a.m., Heiler Bemerguy wrote: >> Is this normal? > Depends on your normal. > AIUI, that "ERROR:" message means thehre are more than 1024 concurrent > transactions being collapsed by your proxy and the overflowed one is > failing.

Re: [squid-users] ERROR: Collapsed forwarding queue overflow for kid2 at 1024 items

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 BTW, it can be any malware on client machine. 25.05.16 21:35, Heiler Bemerguy пишет: > > > I don't know if there's something "in loop".. that's why I'm asking... > > Start Time: Fri, 20 May 2016 10:42:20 GMT > Current Time: Wed, 25 May

Re: [squid-users] ERROR: Collapsed forwarding queue overflow for kid2 at 1024 items

I don't know if there's something "in loop".. that's why I'm asking... Start Time: Fri, 20 May 2016 10:42:20 GMT Current Time: Wed, 25 May 2016 15:34:42 GMT Connection information for squid: Number of clients accessing cache: 4745 Number of HTTP requests received:

Re: [squid-users] Excessive TCP memory usage

When I listen to connections between squid and icap using tcpdump I saw that after a while icap closes the connection but squid does not close, so connection stays in CLOSE_WAIT state: [root@test ~]# tcpdump -i any -n port 34693 tcpdump: WARNING: Promiscuous mode not supported on the "any" device

Re: [squid-users] Excessive TCP memory usage

2016-05-24 21:47 GMT+03:00 Amos Jeffries : > On 25/05/2016 5:50 a.m., Deniz Eren wrote: >> Hi, >> >> After upgrading to squid 3.5.16 I realized that squid started using >> much of kernel's TCP memory. > > Upgrade from which version? > Upgrading from squid 3.1.14. I started