Hi.
I was using the 3.4.x branch for quite some time, it was working just
fine on small installations.
Yesterday I upgraded my largest cache installation from 3.3.13 to 3.4.8
(same config, diskd, NTLM/GSS-SPNEGO auth helpers, external helpers).
Today morning I noticed that squid is spiking to 100%
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/10/2014 5:11 a.m., Eugene M. Zheganin wrote:
> Hi.
>
> Is someone getting this too ? I get this with sad regularity:
>
> # grep lm_request /var/log/squid/cache.log 2014/10/06 14:32:12
> kid1| assertion failed: UserRequest.cc:229: "lm_request->w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/10/2014 5:40 a.m., Mike wrote:
> I was reading through the release notes for squid 3.5, and in
> section 2.4 regarding HTTPS, it mentions "When Squid is built with
> the GnuTLS encryption library the tool is able to open TLS (or
> SSL/3.0) connec
Hi,
it depends on how your helpers are implemented: the helpers
themselves are restarted upon reconfiguration, but if they use a
persistent storage for sessions, that is not touched.
Ongoing transfers are not stopped and are in any case allowed to complete.
On Wed, Oct 22, 2014 at 12:42 AM, Job
Hello,
integrating squid in a captive portal environment, i have to setup different
profiles in order to apply restrictions dinamically.
The squid -k reconfigure kill active sessione/connections?
I tried when downloading a file, it stops for one/two seconds and then
continues download, but i
I was reading through the release notes for squid 3.5, and in section
2.4 regarding HTTPS, it mentions "When Squid is built with the GnuTLS
encryption library the tool is able to open TLS (or SSL/3.0) connections
to servers", and the wording makes me think that when openssl is in use,
squid can
Hi.
Is someone getting this too ? I get this with sad regularity:
# grep lm_request /var/log/squid/cache.log
2014/10/06 14:32:12 kid1| assertion failed: UserRequest.cc:229:
"lm_request->waiting"
2014/10/07 16:06:10 kid1| assertion failed: UserRequest.cc:229:
"lm_request->waiting"
2014/10/16 16
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 9:32 p.m., saleh madi wrote:
> Hello Amos,
>
> For squid 3.4.8, In the server we have 2xssd 240GB and 4XHDD
> 2000GB, Internet bandwidth 600Mbits and four squid instances,
> please what is the suggestion settings for cache_dir for SSD
There are some other message that may be helpful.
I used to configure squid to load ecap-adapter module as following on windows.
---configure---
ecap_enable on
adaptation_send_client_ip on
loadable_modules /usr/local/lib/ecap_adapter_modifying.so
ecap_se
Hello Amos,
For squid 3.4.8, In the server we have 2xssd 240GB and 4XHDD 2000GB, Internet
bandwidth 600Mbits and four squid instances, please what is the suggestion
settings for cache_dir for SSD and HDD to cover the high http traffic request.
Thank you and Best Regards,
Saleh
- Original M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 8:52 p.m., lionx...@gmail.com wrote:
>
> Hi. I‘m coming again.
>
> Now, I have compiled squid-3.3.3 with --enable-ecap option
> successfully on cygwin and run it successfully on windows. But,
> there are another question about compilin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 7:36 p.m., saleh madi wrote:
> Hello Amos,
>
> Many thanks for your reply. Before two years I have tested squid
> 2.7 it's very stable and in the high http traffic request is very
> stable no crash. But for squid-3 I see too many differe
Hi. I‘m coming again.
Now, I have compiled squid-3.3.3 with --enable-ecap option successfully on
cygwin and run it
successfully on windows.
But, there are another question about compiling ecap-adapter module？
I'm not sure that I should ask this question here, maybe I should ask eCAP
develope
13 matches
Mail list logo
