Re: [squid-users] ssl-bump not working in non transparent mode

2014-06-28 Thread Eliezer Croitoru

Hey Nil,

Are you aware that you need to use the "ssl-bump" flags and 
dynamic_cert_mem  etc on the forward regular proxy mode?

such as:
http_port 10.10.16.56:3128 ssl-bump ...(all other settings)

For it to work?

Eliezer

On 06/27/2014 03:45 PM, Nil Nik wrote:

http_port 10.10.16.56:3127 intercept
http_port 10.10.16.56:3128
https_port 10.10.16.56:3129 generate-host-certificates=on 
dynamic_cert_mem_cache_size=4MB cert=/etc/squid/mycert.pem intercept ssl-bump




Re: [squid-users] What is a reasonable size for squid.conf?

2014-06-28 Thread Eliezer Croitoru

On 06/27/2014 10:51 PM, Owen Crow wrote:

My squid.conf is currently clocking in 60k lines (not including
comments or blank lines). Combined with the conf files in my conf.d
directory, I have a total of 89k lines in configuration.


Hey,

Consider that I am Writing from my own mind, knowledge and experience.

This is no way close to the original conf file of squid...(the last time 
I have seen it)

You have a very special setup.
There is no documentation about it and I assume that the admin assumes 
couple levels of sanity of the file structure VS complexity of the software.


I have not seen Samba settings file that will consume 30k of settings 
line just because on many environments it's not really sane to run such 
a server.
I cannot compare squid to other services but it's not the first time 
that this kind of question is being asked.


I am not sure what you are expecting, are you asking for less time or 
just to know more about the subject?


I am also not sure that squid.conf is the place to configure couple 
special setups.

There are cases which squid is not the right tool for the the task.

So consider:
- You are expecting too much from squid(which is overwhelming, in the 
good way..)

- You are using a special setup which is more complex then the basic.
- You are maybe wrongly comparing "grep" or similar tools which are not 
parsing a complex conf file.


In any of the above cases 20 seconds can be considered a reasonable time 
to load a complex proxy setup.
There are software systems which I have seen that takes more then 20 
seconds to just show a tiny sign of life due to their complexity.


From my point of view when you go above the basic squid conf file you 
should ask your self if you expect these static rules to stay for a long 
time and if not then you should consider using another way to implement 
the idea.


If you can share the reason which the conf file is so big some might 
give you an idea about it.


Eliezer


Re: [squid-users] What is a reasonable size for squid.conf?

2014-06-28 Thread Kinkie
On Fri, Jun 27, 2014 at 9:51 PM, Owen Crow  wrote:
> I am running a non-caching reverse proxy using version 3.3.10.
>
> My squid.conf is currently clocking in 60k lines (not including
> comments or blank lines). Combined with the conf files in my conf.d
> directory, I have a total of 89k lines in configuration.

Hi Owen,
  I suspect you have embedded in your squid.conf some very long ACL,
haven't you?
If so, what type is it, and how many lines?
As a general advice, you may want to consider moving these ACLs to
external files and reference them from the config-file.

> I have definitely noticed "-k reconfigure" calls taking on the order
> of 20 seconds to run when it used to be less than a couple seconds.
> (Same results with "-k test").

20 seconds is quite a bit. What has changed in the configuration file
since then?

> I've tried searching for anything related to max lines and similar,
> but it usually talks about squid.conf configuration options and not
> the file itself.
> If this is not documented per se, are there any anecdotal examples
> that have this many lines or more? I only see this growing over time.

There is no hard limit to the configuration file that I know of. Are
you experiencing any performance issues other than during
reconfiguration?

-- 
Kinkie


[squid-users] Squid 3.4.6 is not caching anything

2014-06-28 Thread liam
Hi

First post here, kinda a bit of a squid noob. but anyway, I am trying to set
up a squid cache on my Debian 7 system. I have Squid 3.4.6 compiled from
source downloaded from squid-cache.org. Here is the output of squid -v

Squid Cache: Version 3.4.6
configure options:  '--disable-arch-native' '--enable-ssl'
'--enable-ssl-crtd' '--prefix=/usr' '--localstatedir=/var'
'--libexecdir=/lib/squid3' '--srcdir=.' '--datadir=/share/squid3'
'--sysconfdir=/etc/squid3' '--with-defualt-user=proxy'
'--with-logdir=/var/log' '--with-pidfile=/var/run/squid.pid'

It is set up to cache in /var/cache/squid. I have run squid -z, and it has
created folders in /var/cache/squid. The permissions on /var/cache/squid are
all set to 777, and the folder is owned by "proxy". 
Note that when I run squid -z, it creates all the folders, but when it
finishes, rather than exiting, it just freezes. Nothing is logged to
cache.log, access.log or syslog.

My squid.conf is almost the default config. Just with the cache_dir line
uncommented. Here is a link to my squid.conf

http://pastebin.com/pv1JbwZE

Here is output from cache.log

http://pastebin.com/WghnfyLb

And my access.log only has TCP_MISS and TCP_CLIENT_REFRESH_MISS. I know that
the objects are cacheable, as they do cache with one of my other squid
servers.

Thanks for any help.



Re: [squid-users] What is a reasonable size for squid.conf?

2014-06-28 Thread Owen Crow
Consider this a reply to Kinkie and Eliezer.

Yes, I expect my setup is unusual, but that's why I'm trying to get
advice from others who might have a similar setup.

I run the proxy as the main destination for a wildcard DNS. This is
our many tenants use URLs in the wildcard domain (lets call it
"*.wild.com") and the proxy connects them to the various backend
services based on the hostname such as:

acme-www.wild.com connects to the WWW server for Acme customer
beta-www.wild.com connects to a similar but different WWW server for
Beta customer.

For each customer there are 5-10 unique hostnames to keep the services
separate. We do this as it is much simpler than URL-rewriting (or at
least it seemed so to me at the beginning).

In addition, our proxy listens on about 8 different ports
(80/443/8080, etc) for different services. The different ports require
7 ACLs that excludes the other ports that are not for that one
service/port combination.

I can get more specific if anyone is interested.

I use make+M4 macros to generate the squid.conf file from a source
file and then separate all the customers into individual configuration
files based on a conf.d directory.

Zero caching is happening, it is all just forwarded traffic.

When I started with ~50 customers, squid cpu was <5% at all times. Now
with closer to 200 customers it sticks around 20%, so I'm just
thinking about the future. And if things keep going well, I can only
expect the number to rise.

Thanks for all the replies! And if anyone is wondering how I counted
lines I used something like this to eliminate comments and blank
lines:

egrep -vc '(^#|^$)' squid.conf

Owen

On Sat, Jun 28, 2014 at 3:50 PM, Kinkie  wrote:
> On Fri, Jun 27, 2014 at 9:51 PM, Owen Crow  wrote:
>> I am running a non-caching reverse proxy using version 3.3.10.
>>
>> My squid.conf is currently clocking in 60k lines (not including
>> comments or blank lines). Combined with the conf files in my conf.d
>> directory, I have a total of 89k lines in configuration.
>
> Hi Owen,
>   I suspect you have embedded in your squid.conf some very long ACL,
> haven't you?
> If so, what type is it, and how many lines?
> As a general advice, you may want to consider moving these ACLs to
> external files and reference them from the config-file.
>
>> I have definitely noticed "-k reconfigure" calls taking on the order
>> of 20 seconds to run when it used to be less than a couple seconds.
>> (Same results with "-k test").
>
> 20 seconds is quite a bit. What has changed in the configuration file
> since then?
>
>> I've tried searching for anything related to max lines and similar,
>> but it usually talks about squid.conf configuration options and not
>> the file itself.
>> If this is not documented per se, are there any anecdotal examples
>> that have this many lines or more? I only see this growing over time.
>
> There is no hard limit to the configuration file that I know of. Are
> you experiencing any performance issues other than during
> reconfiguration?
>
> --
> Kinkie


Re: [squid-users] Squid 3.4.6 is not caching anything

2014-06-28 Thread Eliezer Croitoru

Can you please clean your squid.conf file from comments etc using:
egrep -vc '(^#|^$)' squid.conf (was mentioned in another post).

I do not know what site it is and why it is cachable but reading the 
logs might be tricky..

What browser\client are you using?

Can you share the access.log relevant parts?

Eliezer

On 06/29/2014 03:22 AM, l...@kzz.se wrote:

My squid.conf is almost the default config. Just with the cache_dir line
uncommented. Here is a link to my squid.conf

http://pastebin.com/pv1JbwZE

Here is output from cache.log

http://pastebin.com/WghnfyLb

And my access.log only has TCP_MISS and TCP_CLIENT_REFRESH_MISS. I know that
the objects are cacheable, as they do cache with one of my other squid
servers.

Thanks for any help.




RE: [squid-users] Squid 3.4.6 is not caching anything

2014-06-28 Thread liam
I have removed all comments from my config file:
http://pastebin.com/kqvNszyp

And here is a short excerpt from my access.log - don't think it will be too
helpful though. I have removed some IP addresses and URLs.

http://pastebin.com/bZiZ3tUN

Note that I do get some TCP_MEM_HIT/200 sometimes.

I have tried using Firefox 29, Internet Explorer 11 and the latest version
of Chrome for Debian 7 stable.

>Från: Eliezer Croitoru [mailto: elie...@ngtech.co.il]
>Skickat: söndag, 29 juni, 2014 08:83
>Till: squid-users@squid-cache.org
>Subject: Re: [squid-users] Squid 3.4.6 is not caching anything
>
>Can you please clean your squid.conf file from comments etc using:
>egrep -vc '(^#|^$)' squid.conf (was mentioned in another post).
>
>I do not know what site it is and why it is cachable but reading the 
>logs might be tricky..
>What browser\client are you using?
>
>Can you share the access.log relevant parts?
>
>Eliezer
>
>>On 06/29/2014 03:22 AM, l...@kzz.se wrote:
>> My squid.conf is almost the default config. Just with the cache_dir line
>>uncommented. Here is a link to my squid.conf
>>
>>http://pastebin.com/pv1JbwZE
>>
>> Here is output from cache.log
>>
>> http://pastebin.com/WghnfyLb
>>
>> And my access.log only has TCP_MISS and TCP_CLIENT_REFRESH_MISS. I know
that
>> the objects are cacheable, as they do cache with one of my other squid
>> servers.
>>
>> Thanks for any help.