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

[Alex Rousskov]

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 calls after you told the OS to free RAM (into swap) less
aggressively. The changes effectively decreased the amount of
immediately available RAM.

If Squid is the primary service on your server, then consider:

1. Removing RAID (for Squid disk cache).

2. Removing swap (or at least not counting on it and treating
   any non-trivial swap usage as a system misconfiguration).

3. Identify the primary RAM consumers and
   the factors that influence their memory usage.

The above actions may not solve your "insufficient RAM" problem (unless
RAID was the primary culprit) but they will give you a better starting
point for finding the solution. Others on the list can help you get
there, especially if you have specific questions.


Good luck,

Alex.

> The server has 24GB DDR3 memory,  disk swap set to 24GB, 12 CPU (24HT cores).
> We have 2800 users, using  kerberos authentication, squidguard for
> filtering, ldap authorization.