users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Deniz Eren
Sent: Tuesday, June 14, 2016 11:07 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Excessive TCP memory usage
Little bump :)
I have posted bug report with steps to reproduce. The problem still exists and
Little bump :)
I have posted bug report with steps to reproduce. The problem still
exists and I am curious whether anyone else is having the same
problem, too.
http://bugs.squid-cache.org/show_bug.cgi?id=4526
On Wed, May 25, 2016 at 1:18 PM, Deniz Eren wrote:
> When I listen to connections betw
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
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 using c-icap and ssl-bump
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?
>
> When squid was running for a long time TCP memory usage is like below:
> test@test:~$ cat /proc/net/sockstat
>
