From owner-freebsd-questions@FreeBSD.ORG Wed Feb 6 12:45:42 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D77B516A41A for ; Wed, 6 Feb 2008 12:45:42 +0000 (UTC) (envelope-from lachlan@lkla.org) Received: from paul.kawaguchichurch.org (pd5e374.sitmff01.ap.so-net.ne.jp [202.213.227.116]) by mx1.freebsd.org (Postfix) with ESMTP id 338DB13C458 for ; Wed, 6 Feb 2008 12:45:41 +0000 (UTC) (envelope-from lachlan@lkla.org) Received: from sm.lkla.org (localhost [127.0.0.1]) by paul.kawaguchichurch.org (8.14.2/8.14.2) with ESMTP id m16CjZwO069972; Wed, 6 Feb 2008 21:45:36 +0900 (JST) (envelope-from lachlan@lkla.org) Received: from 137.153.0.25 (SquirrelMail authenticated user lachlan) by sm.lkla.org with HTTP; Wed, 6 Feb 2008 21:45:36 +0900 (JST) Message-ID: <28742.137.153.0.25.1202301936.squirrel@sm.lkla.org> In-Reply-To: <47A99B4E.1080707@dial.pipex.com> References: <1153.137.153.0.37.1202210274.squirrel@sm.lkla.org> <69739C80-0639-4808-B5EB-0D9553826559@dpcsys.com> <30396.137.153.0.36.1202264253.squirrel@sm.lkla.org> <47A99B4E.1080707@dial.pipex.com> Date: Wed, 6 Feb 2008 21:45:36 +0900 (JST) From: "Lachlan Michael" To: "Alex Zbyslaw" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-2022-jp Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-questions@freebsd.org Subject: Re: Memory Error using Mailman on FreeBSD. How to debug? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lachlan@lkla.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2008 12:45:43 -0000 > Lachlan Michael wrote: > >># su mailman >>This account is currently not available. >> >>I'm not sure about the syntax but limits -U mailman doesn't seem to make >>the user mailman, but just use the class default. >> >> > su -m mailman > > will do what you want. Ah, thanks! That's a much better way to do it. The result was unchanged however. > However, to be sure what your limits are, I > would stick ulimit -a in the script that starts mailman, just to be > sure. If the output from that is reasonable, and it doesn't seem to be > messing with limits anywhere, then that's probably not the problem. I start mailman as /usr/local/etc/rc.d/mailman start I put ulimit -a in that script, and the values were the same as previous reported. # /usr/local/etc/rc.d/mailman start cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 524288 stack size (kbytes, -s) 65536 core file size (512-blocks, -c) unlimited max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) unlimited max user processes (-u) 5547 open files (-n) 11095 virtual mem size (kbytes, -v) unlimited sbsize (bytes, -b) unlimited > Perhaps it's something about the attachment itself. Can you try some > different, similarly sized, attachment? Different attachments produce the same result. > How big does the mailman process actually get? top will tell you. Mailman values don't budge. None of the mailman processes go over about 8.5M, which is what they are during idle time. > Python and mailman presumably came from ports? Yes. > Last I looked, python > had a build option HUGE_STACK_SIZE which I've needed for some apps in > the distant past, IIRC. Can you re-install python with that opt and see > if it helps? (It's just a SWAG, and could be wrong!). I saw that too, and am currently running with it enabled. It doesn't seem to make a difference though. Thanks for all the tips!