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

2017-11-17 Thread Bike dernikov1
On Fri, Nov 17, 2017 at 3:53 AM, Amos Jeffries wrote: > On 17/11/17 03:49, Bike dernikov1 wrote: >> >> On Thu, Nov 16, 2017 at 8:58 AM, Amos Jeffries wrote: >>> >>> On 16/11/17 01:32, Bike dernikov1 wrote: >>>> >>>> >>>> &g

Re: [squid-users] Is it possible to apply squid delay pools on users/groups from AD ?

2017-11-17 Thread Bike dernikov1
On Fri, Nov 17, 2017 at 3:39 AM, Amos Jeffries wrote: > On 17/11/17 03:40, Bike dernikov1 wrote: >> >> Thanks for info, we searched for solution but found that is not >> possible to combine delay polls, and forum is our last hope, so far we >> solved almost everything

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

2017-11-16 Thread Bike dernikov1
On Thu, Nov 16, 2017 at 8:58 AM, Amos Jeffries wrote: > On 16/11/17 01:32, Bike dernikov1 wrote: >> >> >> If i can ask under same title: >> Yesterday we had error in logs: syslog, cache.log, dmesg,access.log >> >> segfault at 8 ip ... sp . error

Re: [squid-users] Is it possible to apply squid delay pools on users/groups from AD ?

2017-11-16 Thread Bike dernikov1
example but couldn't find it. Thanks for help. On Thu, Nov 16, 2017 at 9:02 AM, Amos Jeffries wrote: > On 16/11/17 01:43, Bike dernikov1 wrote: >> >> Hi, >> this is my second topic, i wouldn't wan to mix with first. I hope that is >> ok. >> i hope that someo

[squid-users] Is it possible to apply squid delay pools on users/groups from AD ?

2017-11-15 Thread Bike dernikov1
Hi, this is my second topic, i wouldn't wan to mix with first. I hope that is ok. i hope that someone succeeded to apply delay pools on users/groups from AD. We are now using delay pool on whole 10.0.0.0/8, but that is a problem as different users have different requirements. We have 30 locati

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

2017-11-15 Thread Bike dernikov1
On Tue, Nov 14, 2017 at 6:12 PM, Alex Rousskov wrote: > On 11/14/2017 08:41 AM, Bike dernikov1 wrote: >> On Mon, Nov 13, 2017 at 4:36 PM, Alex Rousskov wrote: >>> On 11/13/2017 02:34 AM, Bike dernikov1 wrote: >>>> Swap could be used to translate back data to mem

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

2017-11-14 Thread Bike dernikov1
On Mon, Nov 13, 2017 at 4:36 PM, Alex Rousskov wrote: > 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

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

2017-11-14 Thread Bike dernikov1
On Mon, Nov 13, 2017 at 2:32 PM, Marcus Kool wrote: > > > 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: >>>

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

2017-11-13 Thread Bike dernikov1
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&#x

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

2017-11-13 Thread Bike dernikov1
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&#x

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

2017-11-13 Thread Bike dernikov1
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: >>> [

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

2017-11-13 Thread Bike dernikov1
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 > configuration

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

2017-11-10 Thread Bike dernikov1
On Thu, Nov 9, 2017 at 5:13 PM, Marcus Kool wrote: > > > On 09/11/17 11:04, Bike dernikov1 wrote: > [snip] >>>> >>>> Memory compsumption:squid use largest part of memory (12GB now, >>>> second proces use 300MB memory), 14GB used by all process.

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

2017-11-10 Thread Bike dernikov1
On Thu, Nov 9, 2017 at 4:03 PM, Alex Rousskov wrote: > On 11/09/2017 06:49 AM, Bike dernikov1 wrote: >>>> On 11/08/2017 02:26 AM, Bike dernikov1 wrote: > >> So why didn't swap hop in? > > As I implied earlier, I do not recommend researching swap-related > de

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

2017-11-09 Thread Bike dernikov1
>>On 11/08/2017 02:26 AM, Bike dernikov1 wrote: >> I hope that someone can explain what happened, why squid stopped working. >I can suggest a working theory: You did not have enough RAM before >vm.swappiness changes and the same insufficient RAM problem led to >failed system

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

2017-11-09 Thread Bike dernikov1
On Wed, Nov 8, 2017 at 3:48 PM, Marcus Kool wrote: > > On 08/11/17 11:36, Bike dernikov1 wrote: >> >> Hi, >> >> We stumbled on ufdbGuard, but licence/price was problem, we didn't >> read documentation carefully. > > yes, ufdbguard is free. > >

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

2017-11-08 Thread Bike dernikov1
Hi, I hope that someone can explain what happened, why squid stopped working. The problem is related to memory/swap handling. After we changed vm.swappiness parameter from 60 to 10 (tuning attempt, to lower a disk usage, because we have only 4 disks in a RAID10, so disk subsystem is a weak link)