Re: [squid-users] not working tproxy in squid 3.2

On Tue, Mar 19, 2013 at 08:49:25PM +0200, Eliezer Croitoru wrote:
> Hey Oleg,
>
> I want to understand couple things about the situation.
> what is the problem? a memory leak?

  1 problem - memory leak;
  2 problem - tproxy doesn't work in squid 3.2.

> How do you see the memory leak? and where?

  I just start squid, start top and wait about a hour when squid grow from
40MB to 800MB and kernel kills it.

> The memory leak you are talking about is in a case of tproxy usage only?

  It's hard to say. I was run squid 3.2, with no working tproxy (as i wrote),
but with normal proxy on 3128 tcp port and it eat my memory too. So, tproxy
is configured, but not used.

> what is the load of the proxy cache?
> do you use it for filtering or just plain cache?

  Only for filtering.

> on what environment?

  What do mean under environment?

> the more details you can give on the scenario and point with your
> finger on the problem I will be happy to assist us finding the
> culprit.
>
> What linux distro are you using?

  Debian 6 and also tried debian 7.
Received on Tue Mar 19 2013 - 19:27:46 MDT