Probably dns issues not related to squid version in any way.
This is a known issue that is not related to squid
Not very clear: Probably not related to squid OR known issue not related
to squid ???
--
View this message in context:
Probably dns issues not related to squid version in any way.
This is a known issue that is not related to squid but I'm happy you
posted about this issue.
Regards,
Eliezer
I appreciate the reply, I don't follow your logic though sorry. You think my
issue is probably DNS related? I tried to
Hi,
I am using squid 3.3.1 to enable the dynamic certificate
generation functionality and it works fine with a self signed
certificate. I now have a actual signed certificate and the ssl chain
is such that my certificate - CA1 - Root CA.
I cleared the previous cert db directory and re
I have the following settings in my squid.conf file relating to the
memory usage:
cache_mem 200 MB
maximum_object_size_in_memory 512 KB
cache_replacement_policy heap GDSF
memory_replacement_policy heap GDSF
cache_dir diskd /var/spool/squid 200 16 256
cache_swap_high 100%
cache_swap_low 80%
With only 200mb available to the system I would turn the size in memory
down to 64k or lower.
-
Signed,
Fix Nichols
http://www.squidblacklist.org
On Tue, 09 Apr 2013 17:43:58 +0100
Mr Dash Four mr.dash.f...@googlemail.com wrote:
I have the following settings in my squid.conf file relating to the
memory usage:
cache_mem 200 MB
maximum_object_size_in_memory 512 KB
cache_replacement_policy heap GDSF
memory_replacement_policy heap
Squidblacklist wrote:
With only 200mb available to the system I would turn the size in memory
down to 64k or lower.
In other words change maximum_object_size_in_memory 512 KB to
maximum_object_size_in_memory 64 KB or less? Is that what is causing
this? The cache logs tell me this:
Local
I have the following settings in my squid.conf file relating to the
memory usage:
cache_mem 200 MB
maximum_object_size_in_memory 512 KB
cache_replacement_policy heap GDSF
memory_replacement_policy heap GDSF
cache_dir diskd /var/spool/squid 200 16 256
200kb? thats less than 1 mb
Well you can have max cachemem object set to 512k, but only if you give
it something reasonable like, 2GB of ram or more, as opposed to the
200mb it currently has. Because with it set to 512k its filling your
ram up very quickly with large objects, if you insist on only allowing
200mb ram for
Squidblacklist wrote:
Well you can have max cachemem object set to 512k, but only if you give
it something reasonable like, 2GB of ram or more, as opposed to the
200mb it currently has. Because with it set to 512k its filling your
ram up very quickly with large objects, if you insist on only
I believe I have seen similar issues before when users set the max ram
and the disk size to the same exact settings, might I suggest you
increase the storage available from 200mb to 300mb, and test. Its worth
a shot.
-
Signed,
Fix Nichols
http://www.squidblacklist.org
Squidblacklist wrote:
I believe I have seen similar issues before when users set the max ram
and the disk size to the same exact settings, might I suggest you
increase the storage available from 200mb to 300mb, and test. Its worth
a shot.
OK, I'll give it a go. Do I have to completely
On 4/9/2013 4:12 PM, Duncan, Brian M. wrote:
I would really like to move on from the 2.x and take advantage of how much
better the newer version supposedly scale.
Thanks again.
Sorry if I wasn't clear.
I will try to rephrase the logic.
I went from the buttom up.
curl + wget + simple ruby
Sorry if I wasn't clear.
I will try to rephrase the logic.
I went from the buttom up.
curl + wget + simple ruby script = slow response.
notice that this address is a redirection.
I am unsure now about the dns issue that I have seen this morning.
The main problem is not the page but the ssl.
After looking for in google, and reading some post around here and
other forums, made the same question in other webs, i finally decided
to post a question.
I'm trying to setup a `squid reverse proxy`, first tried with version
3.1.18, and now i'm trying with 3.3 stable, but the result is almost
Hello,
Is there any recent figures about max throughput to be expected from a
squid 3.x install (on recent hardware) in the scenario of a single stream
downloading a large file ( 1GB) (read not cacheable)
I'm aware that's not a performance metric per se, but it's one of the
Hi ..
I just configure squid for ftp. When listing directory contents in
ftp, squid always display file size in human-readable format (for
example: 110K, etc). I want squid to display file size in exact size
(in bytes) when listing directory contents in FTP, not in
'human-readable' format.
Can
Is there any way to influence the order in which Squid sends the
Proxy-Authenticate headers to the client? I already tried changing
the order in the config file to no avail.
Background:
I have a squid 3.3.3 proxy using both kerberos and radius. A capture
shows it offers both Basic and Negotiate
18 matches
Mail list logo
