From owner-freebsd-stable@FreeBSD.ORG Fri Jan 6 11:15:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C3A916A41F for ; Fri, 6 Jan 2006 11:15:35 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A98343D48 for ; Fri, 6 Jan 2006 11:15:34 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail05.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k06BFWfg004956 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Jan 2006 22:15:32 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k06BFWHh052071; Fri, 6 Jan 2006 22:15:32 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k06BFVfx052070; Fri, 6 Jan 2006 22:15:31 +1100 (EST) (envelope-from pjeremy) Date: Fri, 6 Jan 2006 22:15:31 +1100 From: Peter Jeremy To: Todor Dragnev Message-ID: <20060106111531.GC51452@cirb503493.alcatel.com.au> References: <20060106090854.GA36654@linuxfan.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060106090854.GA36654@linuxfan.org> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: [jonathan.glass@oit.gatech.edu: Re: [Flow-tools] Memory leak ?] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 11:15:35 -0000 [flow-capture process too large] On Fri, 2006-Jan-06 11:08:54 +0200, Todor Dragnev wrote: >Can someone help with this ? Help how? AFAIK, flow-control/flow-capture is not a FreeBSD port so finding someone here with knowledge of it may be difficult. If you think it's a problem with FreeBSD, you're going to need to supply more information so that we can help you. >>>I use flow-control from about 1 week. My OS is FreeBSD 6.0-RELEASE #0 >>>for AMD64. All works fine but yesterday I found this in dmesg: >>> >>>Jan 4 21:30:58 katana kernel: swap_pager_getswapspace(16): failed >>>Jan 4 21:30:58 katana kernel: swap_pager_getswapspace(12): failed >>>Jan 4 21:30:58 katana kernel: swap_pager_getswapspace(6): failed ... >>>518 root 1 96 0 2648M 104M select 0:33 0.00% flow-capture This means you've run out of swap space. The top output shows that the offending process was flow-capture. Presumably you already knew this much. >>>My starting line for flow-capture is: >>> >>>/usr/local/bin/flow-capture -p /var/run/flow-capture.pid -n 287 -N 0 -w >>>/var/log/netflows/ -S 5 /127.0.0.1/8899 >>> >>>Is that huge memory usage is memory leak or I do something wrong ? The command line means nothing to me. How big a process size were you expecting? If you kill and restart the process, how big is it initially? What libraries is it using? What does it do? >>I think the easiest way to start looking at this would be to run >>flow-capture under a memory debugger of some sort, like efence >>(Electric Fence Malloc Debugger). Have you tried this suggestion? Note that phkmalloc (the standard FreeBSD malloc) has some good debugging facilities built in - check malloc(3) for details. >I'm running flow-capture on AMD64 on Fedora Core 3 with no problems. >The only issue I run into is lack of disk space! Sometimes 50GB is not >enough! Unfortunately, Jonathan didn't say what the process size he saw was so this doesn't help much. -- Peter Jeremy