From owner-freebsd-questions@FreeBSD.ORG Thu Sep 25 16:55:40 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 116B5E0F for ; Thu, 25 Sep 2014 16:55:40 +0000 (UTC) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 71039E20 for ; Thu, 25 Sep 2014 16:55:39 +0000 (UTC) X-Virus-Scanned: by clamd daemon 0.98.1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.tomsk.ru (account sudakov@sibptus.tomsk.ru [212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 36665897; Thu, 25 Sep 2014 23:55:37 +0700 Received: from admin.sibptus.tomsk.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.tomsk.ru (8.14.9/8.14.7) with ESMTP id s8PGtXGD082299; Thu, 25 Sep 2014 23:55:36 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.14.9/8.14.7/Submit) id s8PGtXmS082298; Thu, 25 Sep 2014 23:55:33 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Thu, 25 Sep 2014 23:55:33 +0700 From: Victor Sudakov To: Dennis Glatting Subject: Re: squid-3.4.8_1 leaking memory Message-ID: <20140925165533.GB81782@admin.sibptus.tomsk.ru> References: <20140925045657.GA71070@admin.sibptus.tomsk.ru> <1411642468.3895.847.camel@btw.pki2.com> <20140925110428.GA79336@admin.sibptus.tomsk.ru> <1411644140.3895.860.camel@btw.pki2.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1411644140.3895.860.camel@btw.pki2.com> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.5.23 (2014-03-12) 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 16:55:40 -0000 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. All right, what other options do I have? Just restart the leaky 3.4.8_1 every hour and hope for a future fix? Besides, I have found that libexec/squid/ntlm_smb_lm_auth is seriously broken. It did work fine in squid27 (was called ntlm_auth at that time) but now it just asks infinitely for the users's domain credentials and never permits the user. In fact, if I use the squid27 ntlm_auth binary with 3.4.8, authentication works again. In short, what do I do? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru