Re: [squid-users] Proxy does not send response for internal host

On 14/11/17 11:21, tappdint wrote: I'm quite new to proxies/networking so I'll try and be as verbose as I can. I have a VM that will request access to an internal host (dev.abc.com). This host container and other containers which are dependencies are created locally on my mac (using docker for

[squid-users] Proxy does not send response for internal host

I'm quite new to proxies/networking so I'll try and be as verbose as I can. I have a VM that will request access to an internal host (dev.abc.com). This host container and other containers which are dependencies are created locally on my mac (using docker for mac). So I also run a docker squid

Re: [squid-users] OCSP stapling and must-staple

On 11/13/2017 03:21 AM, Niklas Bachmaier wrote: > The last post I found on OCSP with Squid is from 2015 where it says > that Squid does not support OCSP by any means. For the record, here is that 2015 thread: http://lists.squid-cache.org/pipermail/squid-users/2015-October/005831.html > For

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

On 11/13/2017 02:34 AM, Bike dernikov1 wrote: > On Fri, Nov 10, 2017 at 4:43 PM, Alex Rousskov wrote: >> Squid swapping in production is an arguably worse disaster, as you have >> learned. In many cases, it is better to deal with a lack of swap than to >> rely on swap's magical effects that most

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

On 13/11/17 10:46, Bike dernikov1 wrote: On Mon, Nov 13, 2017 at 12:15 PM, Marcus Kool wrote: On 13/11/17 07:46, Bike dernikov1 wrote: are you saying that you have cache_mem 14G If yes, you should read the memory FAQ and reduce this. 'cache_mem 14G'

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

On Mon, Nov 13, 2017 at 12:15 PM, Marcus Kool wrote: > > > On 13/11/17 07:46, Bike dernikov1 wrote: > >>> are you saying that you have >>> cache_mem 14G >>> If yes, you should read the memory FAQ and reduce this. >>> 'cache_mem 14G' explains that Squid starts

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

On Mon, Nov 13, 2017 at 12:15 PM, Marcus Kool wrote: > > > On 13/11/17 07:46, Bike dernikov1 wrote: > >>> are you saying that you have >>> cache_mem 14G >>> If yes, you should read the memory FAQ and reduce this. >>> 'cache_mem 14G' explains that Squid starts

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

On 13/11/17 07:46, Bike dernikov1 wrote: are you saying that you have cache_mem 14G If yes, you should read the memory FAQ and reduce this. 'cache_mem 14G' explains that Squid starts 'small' and grows over time. For our case, what do you recomend. 10GB or even lower ? Plan reading

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

On Fri, Nov 10, 2017 at 11:11 PM, Marcus Kool wrote: > > > On 10/11/17 12:11, Bike dernikov1 wrote: >> >> On Thu, Nov 9, 2017 at 5:13 PM, Marcus Kool >> wrote: >>> >>> >>> >>> On 09/11/17 11:04, Bike dernikov1 wrote: >>> [snip] >>

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

On Fri, Nov 10, 2017 at 4:43 PM, Alex Rousskov wrote: > On 11/10/2017 06:16 AM, Bike dernikov1 wrote: > >> So you suggest that we totally disable disk swap (or just for >> debuging) ? > > I would aim for totally disabling disk swap, but getting to that >

Re: [squid-users] url_rewrite_program and ACLs

From: Amos Jeffries >> >> File descriptor usage for squid: >> Maximum number of file descriptors: 65536 >> Largest file desc currently in use: 6980 >> Number of file desc currently in use: 6627 >> Files queued for open: 0 >> Available number