[squid-users] problem with basic_ldap_auth

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/10/2014 5:30 a.m., masterx81 wrote:
> I've noticed that also others had problems on 3.4.x with high cpu
> usage using ntlm auth, and i would be happy to help and support the
> project. But i don't know too much about linux (are only few month
> that i play with it) and know squid only a bit. I not know if i can
> be much useful. And the system is of a customer of mine, but i can
> connect via vpn, so i can access to it at any time. Let me know if
> and how i can help!
> 

If possible the best thing we can get is a ALL,9 cache.log covering at
least some of the time when CPU is extremely high.

If you (or anyone affected) can do that it would be a great help.

NOTE: that amount of debug will slow the proxy down somewhat more, and
generate a huge amount of output. To get that info from a production
machine:

1) Make a copy of your squid.conf with "debug_options ALL,9" added to it.

2) run: squid -k reconfigure -f squid.conf.copy

... wait until sufficient data is logged.

3) run: squid -k reconfigure

4) move the cache.log elsewhere

5) run: squid -k rotate

Amos

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUOBWLAAoJELJo5wb/XPRj2SkIAMA8eL9+IDfnA++hRgGPAFzl
ey3M4+fQIjF97ZfiCTs6VEMW7yDE3XgzBISHe8mcyfMEJPHJv3Mkduavt2i3vSu8
NYToliYssUGtdUVgvNe96W6b/1Ak4ScvtBhpmjpnyt+nOetQjJ1r1R83jYk8tQIc
oILe4qn6aHPWlA/kx5tMkcSuiHLV+adAAhA1aAKCMrKFzQBiZT3LBLxPHA0k9VRc
H7oQnJPlOLEsRMgie0HrDb+VjYbjCQq8PUqM3SsFdLgF8B20PMUSV2/G0PIuP19L
m9FQbR/Vbh3RT4CPBz4auifRs1BJ25Ouyxo0Kag11G5ElULbJGvUEcF0FpNjI7M=
=ADP/
-----END PGP SIGNATURE-----