Hello,
I'm trying to test Squid 3.5.1 configured with digest authentication, and with
high load Squid eats 100% CPU
I had no problem with 3.4 and the patch from your previous message (
http://www.mail-archive.com/squid-users@lists.squid-cache.org/msg00925.html )
The problem is gone with BASIC
I removed that MSNT from my configure options but I still get the error.
To be honest, I don't know what to do next.
On 19 January 2015 at 05:22, Amos Jeffries squ...@treenet.co.nz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/01/2015 10:03 a.m., Odhiambo Washington wrote:
Quoting Jason Haar jason_h...@trimble.com:
On 19/01/15 16:30, sq...@proxyplayer.co.uk wrote:
Your systems have detected unusual traffic from your computer network.
Some computers it presents a captcha, on others it just plain refuses
to show search results.
Umm, your email address is
after downgrade to 3.4.11 the problem still here !!
dont say i need to install fresh system
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/BUG-3279-HTTP-reply-without-Date-tp4669162p4669184.html
Sent from the Squid - Users mailing list archive at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow,
3.4.x and 3.5 has incompatible cache format???
No, I'm just thinking about cache corruption, this could explain that the
problem still present with 3.4 returns
It's just an idea.
Regards,
Fred
http://numsys.eu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think, now 3.5.1 is not ready for production use yet. Just for testing.
19.01.2015 20:36, HackXBack пишет:
I think the solution is to go back to 3.4
Thanks
--
View this message in context:
I have installed squid on FreeBSD and it's crashing with errors as seen
from http://pastebin.com/yC6YZ7Bg.
My squid.conf is seen at http://pastebin.com/hJpPXJ0K
I am using the Squid in a tranparent proxy mode with PF firewall.
Squid is installed from FreeBSD ports:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/01/2015 4:20 a.m., Odhiambo Washington wrote:
On 19 January 2015 at 17:55, Yuri Voinov wrote:
Your use CLang. This is the single point.
You can get any effects. Looks like this is not Squid problem.
Just system.
Are you
I think the solution is to go back to 3.4
Thanks
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/BUG-3279-HTTP-reply-without-Date-tp4669162p4669180.html
Sent from the Squid - Users mailing list archive at Nabble.com.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/01/2015 3:36 a.m., HackXBack wrote:
I think the solution is to go back to 3.4
If you note the BUG 3279 is reported by people since 3.2 series. So
3.4 is also seeing it when built and used in the same way. It seems to
be most common on AUFS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow,
3.4.x and 3.5 has incompatible cache format???
19.01.2015 20:59, FredB пишет:
- Mail original -
De: HackXBack hack.b...@hotmail.com
À: squid-users@lists.squid-cache.org
Envoyé: Lundi 19 Janvier 2015 15:53:20
Objet: Re:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/01/2015 4:48 a.m., Odhiambo Washington wrote:
On 19 January 2015 at 17:13, Odhiambo Washington
odhia...@gmail.com wrote:
On 19 January 2015 at 16:56, Eliezer Croitoru
elie...@ngtech.co.il wrote:
On 19/01/2015 15:26, Odhiambo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yep, agreed. It is possible.
19.01.2015 21:14, FredB пишет:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow,
3.4.x and 3.5 has incompatible cache format???
No, I'm just thinking about cache corruption, this could explain that
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/01/2015 9:06 a.m., mattatrmc wrote:
hey Francessco,
I actually tried to troubleshoot the problem on my own while I was
waiting to hear from other people. I'm using OpenBSD 5.6, which I
would assume would be one of the OS's trialled by the
On 19/01/2015 15:56, HackXBack wrote:
after upgrading to 3.5.1 i have bug
BUG 3279: HTTP reply without Date
how to solve it ??
To make sure I understand the issue:
Is it crashing squid? or just shows a warning in the logs?
Thanks,
Eliezer
___
Still have problems... I've tried in different ways and i'm unable to get it
work...
This is my config:
#
# Recommended minimum configuration:
#
### cache manager
cache_mgr cache...@domain.com
visible_hostnameServ07.domain.com
authenticate_ip_ttl 1 hour
### negotiate kerberos and ntlm
16 matches
Mail list logo
