Milter-greylist

--- In milter-greylist@yahoogroups.com, Emmanuel Dreyfus <manu@...> wrote:
>
> On Tue, Aug 28, 2007 at 02:11:13PM -0000, Stuart Freedman wrote:
> > Hi folks!  I have some (heavily loaded) FreeBSD 4.11 boxes on which
> > milter-greylist 4.0b1 is crashing frequently with a "milter-greylist:
> > malloc() failed: Cannot allocate memory" error being logged in the
> > syslog.  
> 
> Raise memory limits (ulimit with sh/ksh/bash, limit with csh/tcsh).
> 
> -- 
> Emmanuel Dreyfus
> manu@...
>

I don't think that ulimit is the problem, as the memory limit is
supposedly "unlimited" (both soft & hard)...

Current ulimit –aS output is:
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)  24000
virtual mem size        (kbytes, -v)  unlimited
sbsize                   (bytes, -b)  unlimited

Current ulimit –aH output is:
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)  24000
virtual mem size        (kbytes, -v)  unlimited
sbsize                   (bytes, -b)  unlimited

One thing I noticed yesterday was that it appeared that mxsync
sessions got disconnected & reconnected a lot.  Is this supposed to
happen?  Could there be an issue related to not freeing resources
before re-initiating such connections?  Should I try to get a core
dump/stack trace?

Thanks again,

        Stuart