<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I have tested v4 to work properly on Amazon Linux 2 in the past.</p><p class=MsoNormal>If RPM’s are needed, let me know.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Eliezer</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----<o:p></o:p></p><p class=MsoNormal>Eliezer Croitoru<o:p></o:p></p><p class=MsoNormal>Tech Support<o:p></o:p></p><p class=MsoNormal>Mobile: +972-5-28704261<o:p></o:p></p><p class=MsoNormal>Email: ngtech1ltd@gmail.com<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:rousskov@measurement-factory.com">Alex Rousskov</a><br><b>Sent: </b>Tuesday, June 9, 2020 11:33 PM<br><b>To: </b><a href="mailto:Ankit.Dixit@eurostar.com">DIXIT Ankit</a>; <a href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br><b>Subject: </b>Re: [squid-users] Squid memory consumption problem</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 6/5/20 2:38 PM, DIXIT Ankit wrote:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> We are facing memory issues on Squid proxy. We have squid proxy server</p><p class=MsoNormal>> running on AWS Cloud(Amazon Linux 2). Server is having total 8 GB RAM</p><p class=MsoNormal>> and 100 GB hard disk.</p><p class=MsoNormal>> </p><p class=MsoNormal>> The problem is that squid is eating all of system memory and not freeing</p><p class=MsoNormal>> up the objects. Server memory lasts for maximum 15 days and after that</p><p class=MsoNormal>> squid process start crashing. Please suggest.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I would start by making sure that you are not suffering from Squid bug</p><p class=MsoNormal>#4005: https://bugs.squid-cache.org/show_bug.cgi?id=4005</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>After that, if you are sure that there is a memory leak, then I suggest</p><p class=MsoNormal>upgrading to v4 (or v5) as the next step. IMHO, it is unlikely that</p><p class=MsoNormal>somebody would volunteer to triage a v3.5 memory leak these days.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>HTH,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Alex.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> [root@eaa-lpx-003-p ~]# squid -version</p><p class=MsoNormal>> </p><p class=MsoNormal>> Squid Cache: Version 3.5.27-20180318-r1330042</p><p class=MsoNormal>> </p><p class=MsoNormal>> Service Name: squid</p><p class=MsoNormal>> </p><p class=MsoNormal>> This binary uses OpenSSL 1.0.2k-fips 26 Jan 2017.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>squid-users mailing list</p><p class=MsoNormal>squid-users@lists.squid-cache.org</p><p class=MsoNormal>http://lists.squid-cache.org/listinfo/squid-users</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>