From owner-freebsd-questions@FreeBSD.ORG Thu Sep 25 11:22:32 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D2B24629 for ; Thu, 25 Sep 2014 11:22:32 +0000 (UTC) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C9C5D86 for ; Thu, 25 Sep 2014 11:22:32 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by btw.pki2.com (8.14.9/8.14.9) with ESMTP id s8PBMLop002820; Thu, 25 Sep 2014 04:22:21 -0700 (PDT) (envelope-from freebsd@pki2.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pki2.com; s=pki2; t=1411644141; bh=Ptpw+L6tjx1uq1a8JTlqhQzEJki615sXT4uI5dI0z+0=; h=Subject:From:To:Cc:In-Reply-To:References:Date; b=BpI1c5g2FbFz+iqwL15DBTYrix1mreaMhZgPR4bkCE3U6ojLFmroc3wVQQGxSvDwW f4G0yx79lUPLN594M7ekItA101RqAF6O42FMg9g1/59TedqOAZpa4g94+ybhV/p74/ uCh611rddsh5w+Eem3IkUeJ0bbE757fjc1PFiKK9WIXwgwD0Sn5wTUBxoAwV/8jxSf rMYKGebzVmZYM7PbKoqaRSDZ+hi4vgmM1a8t+nCcgZhpQIxGAPIiI73+zY6AyYiKOV +3D1fN96iqLdV6zAdx6Ux94rbXwVXpZAEHyZ8dN4K5zbPe+SMAKt81GtUlQBtGw4kh EqGCgbTPuLirQ== Subject: Re: squid-3.4.8_1 leaking memory From: Dennis Glatting To: Victor Sudakov In-Reply-To: <20140925110428.GA79336@admin.sibptus.tomsk.ru> References: <20140925045657.GA71070@admin.sibptus.tomsk.ru> <1411642468.3895.847.camel@btw.pki2.com> <20140925110428.GA79336@admin.sibptus.tomsk.ru> Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 25 Sep 2014 04:22:20 -0700 Message-ID: <1411644140.3895.860.camel@btw.pki2.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-SoftwareMunitions-MailScanner-Information: Dennis Glatting X-SoftwareMunitions-MailScanner-ID: s8PBMLop002820 X-SoftwareMunitions-MailScanner: Found to be clean X-MailScanner-From: freebsd@pki2.com Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 11:22:32 -0000 On Thu, 2014-09-25 at 18:04 +0700, Victor Sudakov wrote: > Dennis Glatting wrote: > > > > > > squid-3.4.8_1 seems to be leaking memory heavily. Its SIZE and RES are > > > growing several MB per minute until eventually swapping begins. > > > > > > Is anyone using it? Have you encountered this problem? > > > > > > The relevant entries in squid.conf are: > > > > > > cache_mem 128 MB > > > cache_dir ufs /webcache/cache 512 16 256 > > > memory_pools off # neither "on" nor "off" have any effect on leaking. > > > > > > As you see, the memory requirements should be rather modest. > > > > > > Running on 8.4-RELEASE-p16 i386. > > > > > > > The Squid Cache web site DOES NOT list 3.4.8 as the stable release, > > rather 3.4.7 is listed as the stable release. > > Well, what is 3.4.8 doing in the ports collection then? Someone was > too quick to adopt it as www/squid ? > There was a long thread last week(?). I read half the messages when I got home when it seemed things were in good hands. I'm sure there was good reason. I am running 3.4.7 (no change sets) on four servers without problems however these are lower use servers (application proxies, AV proxies, etc -- with exceptions, generally no longer user proxies). I haven't noticed a problem but that does not mean there isn't one. Also, they just went through a security patch cycle and were booted, so I don't have useful data. > > There are also 18 change > > sets listed for 3.4.7 and three for 3.4.8. > > Is there a quick and easy way to to downgrade www/squid to 3.4.7? > > Tonight I'll be trying to replace it with www/squid33 anyway. > 3.3 is EoL or near EoL. > > > > I did not follow the thread where we went from 3.4.7 to 3.4.8. > > >