Re: [squid-users] problem with squid_ldap_auth

2014-10-23 Thread squid-list
Hi, I think the error is not with squid version, it might be the connection problem between proxy server and LDAP server. Please, check the reachability of LDAP server from the proxy server and also Just check the DNS configuration whether you have correctly configured it in proxy server.

[squid-users] Large rock supporting with stable squid version

2014-10-23 Thread Ahmed Allzaeem
Hi I want to ask about Large rock supporting. In large rock supporting wts the max size for disk store ? and max size of ram store? I need someone tried large rock with squid 3.head version and have seen a stability , I used last time squid3.head but it hanged after sometime I need a he

[squid-users] problem with squid_ldap_auth

2014-10-23 Thread Julie Xu
Hi I have squid installed and trying to contact Ldap. Below command is working for older squid, but not new one and both server are Redhat 6.5 (Santiago) auth_param basic program /usr/lib64/squid/squid_ldap_auth -b ou=xx,dc=xx,dc=xx,dc=xx,dc=xx -f (&(cn=%s)(objectClass=*)) -u cn -s sub -P -c 5

Re: [squid-users] Server Failure: The name server was unable to process this query.

2014-10-23 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/10/2014 6:41 a.m., Natxo Asenjo wrote: > On Thu, Oct 23, 2014 at 3:10 PM, Yassin CHOUCHANE wrote: >> root [~] > nslookup cafeServer Server: 192.168.1.3 >> Address:192.168.1.3#53 >> >> Name: cafeServer.sonsofanarchy.fr Address:

Re: [squid-users] Server Failure: The name server was unable to process this query.

2014-10-23 Thread Natxo Asenjo
On Thu, Oct 23, 2014 at 3:10 PM, Yassin CHOUCHANE wrote: > root [~] > nslookup cafeServer > Server: 192.168.1.3 > Address:192.168.1.3#53 > > Name: cafeServer.sonsofanarchy.fr > Address: 192.168.1.50 > > > but when i lunch it on my webrowser i have the message > Server Failure: Th

Re: [squid-users] 3.3.x -> 3.4.x: huge performance regression

2014-10-23 Thread masterx81
Same here, i'm waiting the right time to go to the customer and try the debug suggested by Amos Jeffries on 3.4.x codes to help to find where is the performance issue. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/3-3-x-3-4-x-huge-performance-regression-tp4

[squid-users] OT: Re: 3.3.x -> 3.4.x: huge performance regression

2014-10-23 Thread Andreas . Reschke
I've had nearly the same Problem. 5 Server with squid 3.4.X and high load till deadlock on squid. Then version changed to 3.3.13 and the load so low that I only need 3 Server with reserve. Enviroment: 5000 User, no logging, no caching on the disk, NTLM-Auth Mit freundlichen Grüßen / Kind regardsM

Re: [squid-users] Squid, Kerberos and FireFox (Was: Re: leaking memory in squid 3.4.8 and 3.4.7.)

2014-10-23 Thread Carlos Defoe
no, rhel 6 On Thu, Oct 23, 2014 at 9:51 AM, Eugene M. Zheganin wrote: > Hi. > > On 23.10.2014 18:13, Carlos Defoe wrote: >> I had this kind of 100% CPU problem with auth helpers when upgrading >> to squid 3.4. I use negotiate_wrapper, kerberos, ntlm and basic auth. >> Then I had to fall back to 3

[squid-users] Server Failure: The name server was unable to process this query.

2014-10-23 Thread Yassin CHOUCHANE
Hello, ok now i have a dns issue for my intranet serveur. so an my squid serveur with dnslookup the serveur is found : root [~] > nslookup cafeServer Server: 192.168.1.3 Address:192.168.1.3#53 Name: cafeServer.sonsofanarchy.fr Address: 192.168.1.50 but when i lunch it on my

Re: [squid-users] Probléme Squid to Java application

2014-10-23 Thread Yassin CHOUCHANE
ok thanks that's works :) this my squid.Conf # ACL Definitions # acl noauth dstdomain "/etc/squid3/conf.d/noauth" # website not use proxy acl auth proxy_auth REQUIRED include /etc/squid3/conf.d/std_acl_definitions.conf include /etc/squid3/conf.d/my_acl_definitions.conf # # Caching Options # incl

Re: [squid-users] Squid, Kerberos and FireFox (Was: Re: leaking memory in squid 3.4.8 and 3.4.7.)

2014-10-23 Thread Eugene M. Zheganin
Hi. On 23.10.2014 18:13, Carlos Defoe wrote: > I had this kind of 100% CPU problem with auth helpers when upgrading > to squid 3.4. I use negotiate_wrapper, kerberos, ntlm and basic auth. > Then I had to fall back to 3.3 and it is production until now, with > some troubles with broken clients, but

Re: [squid-users] Squid, Kerberos and FireFox (Was: Re: leaking memory in squid 3.4.8 and 3.4.7.)

2014-10-23 Thread Carlos Defoe
I had this kind of 100% CPU problem with auth helpers when upgrading to squid 3.4. I use negotiate_wrapper, kerberos, ntlm and basic auth. Then I had to fall back to 3.3 and it is production until now, with some troubles with broken clients, but with normal cpu usage most of the time. Can you try w

Re: [squid-users] Squid, Kerberos and FireFox (Was: Re: leaking memory in squid 3.4.8 and 3.4.7.)

2014-10-23 Thread Victor Sudakov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Amos Jeffries wrote: > > And about the basic issues that you were having with > > performance, does it help to run Kerberos instead of NTLM > > (it should...)? > > I have even moved squid to a new virtual machine (FreeBSD >

Re: [squid-users] Squid, Kerberos and FireFox (Was: Re: leaking memory in squid 3.4.8 and 3.4.7.)

2014-10-23 Thread Victor Sudakov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eliezer Croitoru wrote: > > I don't know what's happening with squid but this kind of CPU > > consumption is just not normal: > > > > Victor are you using workers by any chance? I doubt it. I have compiled it from the FreeBSD ports, there was no "w

Re: [squid-users] Squid, Kerberos and FireFox (Was: Re: leaking memory in squid 3.4.8 and 3.4.7.)

2014-10-23 Thread Amos Jeffries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/10/2014 7:27 p.m., Victor Sudakov wrote: > Victor Sudakov wrote: > And about the basic issues that you were having with > performance, does it help to run Kerberos instead of NTLM > (it should...)? I have even moved s

Re: [squid-users] Squid 3.5.0.1 beta is available

2014-10-23 Thread Eliezer Croitoru
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/23/2014 02:40 AM, Amos Jeffries wrote: > If you are seeing this old content constantly or round-robin style > between page loads you can use west.squid-cache.org temporarily in > the URLs instead of www. > > Amos It's the same issue for me: htt

Re: [squid-users] 3.3.x -> 3.4.x: huge performance regression

2014-10-23 Thread Eliezer Croitoru
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey, What is the network load? how many users? Have you been using workers at all in the past? Can you see the avg requests per second on the cache manager page? Eliezer On 10/22/2014 09:02 AM, Eugene M. Zheganin wrote: > Hi. > > I was using the 3.