An: Amos Jeffries; squid-users@squid-cache.org
Betreff: AW: [squid-users] squid 3.4. uses 100% cpu with ntlm_auth
thanxs,
our assumption is, that it is related to helper management. with 3.4. there is
a "new helper protocol", right?
our environment worked with 3.2 without problems. no
at. the rise is not
that fast...
... but also happens in the end!
-Ursprüngliche Nachricht-
Von: Carlos Defoe [mailto:carlosde...@gmail.com]
Gesendet: Dienstag, 4. Februar 2014 20:38
An: squid-users
Betreff: Re: AW: [squid-users] squid 3.4. uses 100% cpu with ntlm_auth
For me, the version
; but also with fakeauth we can see the rising of cpu usage. we then enabled
>> 2 workers and this seems to reduce the problem somewhat. the rise is not
>> that fast...
>
> ... but also happens in the end!
>
>
>> -----Ursprüngliche Nachricht-
>> Von: Carlos Defo
oe [mailto:carlosde...@gmail.com]
> Gesendet: Dienstag, 4. Februar 2014 20:38
> An: squid-users
> Betreff: Re: AW: [squid-users] squid 3.4. uses 100% cpu with ntlm_auth
>
> For me, the version 3.4.3 have the same behavior. It uses 100% CPU (in
> one core, the others are normal). Fo
For me, the version 3.4.3 have the same behavior. It uses 100% CPU (in
one core, the others are normal). For the users, it's just a slowed
down navigation. As soon as I change back to the 3.3.8, everything
works fine.
Actually I'm not sure the problem is caused by ntlm or kerberos or
external_acl_
On Wed, Jan 8, 2014 at 1:05 PM, Amos Jeffries wrote:
> On 7/01/2014 10:21 p.m., Rietzler, Markus (RZF, SG 324 /
> ) wrote:
>> thanxs,
>>
>> our assumption is, that it is related to helper management. with 3.4. there
>> is a "new helper protocol", right?
>
> Right. That is the big user-visible bit
I switched from 3.3.8 to 3.4.2, and apparently, I got problems with
auth too (I'm using negotiate_wrapper and ext_kerberos_ldap_group_acl,
most clients are using kerberos). The CPU load started growing, and
for some clients we got "connection timed out" on a random basis. I
quick switched back to 3
On 7/01/2014 10:21 p.m., Rietzler, Markus (RZF, SG 324 /
) wrote:
> thanxs,
>
> our assumption is, that it is related to helper management. with 3.4. there
> is a "new helper protocol", right?
Right. That is the big user-visible bit in 3.4.
But there are other background changes involving TCP c
thanxs,
our assumption is, that it is related to helper management. with 3.4. there is
a "new helper protocol", right?
our environment worked with 3.2 without problems. now with the jump to 3.4. it
will not work anymore. so number of requests are somehow important but as it
worked in the past..
