Search squid archive

Re: leaking memory in squid 3.4.8 and 3.4.7.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/28/2014 12:18 PM, Victor Sudakov wrote:
If I have to stick to some old unsupported version, I'd choose 2.7.
It has worked flawlessly until it was deleted from the ports tree and
I had to migrate to squid3.

Victor,
Please start by declaring the environment in the form of:
is it a intercept or forward proxy?(defined in the browser or using a GW in the middle) In the case you intercept, do you intercept on the squid machine only or you redirect\route the traffic to it?
If you intercept share your intercept\pf\IPFW rules.
Did you had the chance to watch the cache.log for more information? maybe squid output something to the cache.log?

There is too much missing to just declare a memory leak.

I have seen something that looks like a memory leak in 3.4.6 and 3.4.7 in the past but it was seen in the memory counters in the cache manager interface which shows exactly to where these bits are leaking to..

If you want\need help consider getting into the #squid irc channel at irc.freenode.net and get some more directions. I am there on and off but once you find me I can try to help you with the basics.

Eliezer
_______________________________________________
Squid-users mailing list
Squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users





[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux