Date: Tue, 03 Mar 2009 08:26:02 -0800 From: Andrew Moran <sneepre@me.com> To: Mel <fbsd.questions@rachie.is-a-geek.net> Cc: freebsd-questions@freebsd.org Subject: Re: SpamAssassin/Perl eating enormous amounts of memory? Message-ID: <649E6643-413F-41B4-AEFA-D94CFC809D00@me.com> In-Reply-To: <9B2E2AAB-0866-4D91-9A4A-4E2D81A342E6@mac.com> References: <8806A36E-A839-481A-8E59-9F79DEB6B51A@me.com> <200903021439.55092.fbsd.questions@rachie.is-a-geek.net> <19C0CCFC-CBD5-4822-8838-4F10C4792C23@mac.com> <200903030640.25554.fbsd.questions@rachie.is-a-geek.net> <9B2E2AAB-0866-4D91-9A4A-4E2D81A342E6@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 3, 2009, at 8:01 AM, Andrew Moran wrote: > > In Mar 3, 2009, at 7:40 AM, Mel wrote: > >> On Monday 02 March 2009 16:21:53 Andrew Moran wrote: >> >>>> What's even weirder is that the process gets that far. Did you play >>>> with >>>> kern.maxdsiz loader tuneable? >>>> If so, set it lower, so you can at least have the machine in a >>>> usable state at >>>> all times. 4G should be enough for any process and should give >>>> enough time >>>> for you to spot the leak and get a ktrace. >>> >>> Nope, I haven't tweaked any kernel settings, just using the generic >>> DEFAULT amd64 kernel. I've been way about tweaking settings >>> because >>> I don't fully understand what the 'correct' values for my setup are. >> >> Could you show kenv kern.maxdsiz and if unset limits -H -d? Looks >> like it's >> 32G on my 6.x amd64, in which case setting it is a good idea. >> echo 'kern.maxdsiz="8G"' >> /boot/loader.conf >> echo 'kern.defdsiz="4G"' >> /boot/loader.conf > > > Thank you for helping me. The earlier suggestion of toggling > Perl Malloc didn't work, nor did syncing sources and installing new > kernel and new world which is what I did lsat night. > > As for kernel settings, I don't have anything in my loader.conf, > and I'm not entirely sure how to show things that aren't sysctls, as > this one doesn't seem to be: > > celebrian# sysctl -a | grep kern.maxdsiz > celebrian# sysctl -a | grep kern.defdsiz > celebrian# > Ok sadly that didn't seem to do much: celebrian# cat /boot/loader.conf kern.maxdsiz="8G" kern.defdsiz="4G" celebrian# I rebooted, but still see my memory being chewed up. Almost immediately after booting, one of my spamassassin processes spun out of control. Here's the top with it eating 16 gigs of memory: PID UID THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 1611 1030 1 68 0 15062M 818M CPU2 2 0:44 20.65% perl5.8.9 and from dmesg: <snip> swap_pager_getswapspace(16): failed swap_pager_getswapspace(16): failed swap_pager_getswapspace(16): failed swap_pager_getswapspace(16): failed swap_pager_getswapspace(3): failed swap_pager_getswapspace(16): failed pid 1611 (perl5.8.9), uid 1030, was killed: out of swap space The computer gets pretty unresponsive during this, unless swapoff my swap, then the process eats the memory faster and gets killed faster. Did I type in the wrong variables? --Andy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?649E6643-413F-41B4-AEFA-D94CFC809D00>