"dbz.c: Can't malloc" during expire
Alex Kiernan
alexk at demon.net
Tue Apr 9 08:14:55 UTC 2002
Elizabeth Zaenger <liz at eecs.umich.edu> writes:
> Hi Alex,
>
> Thanks, but what does this mean? Or rather, what's the fix?
>
Larger ulimit, more swap, more physical RAM, move to 64 bit
architecure (probably in that order).
> (Someone suggested I needed more swap, but I can't see any evidence of
> that....)
>
> > From: Alex Kiernan <alexk at demon.net>
> >
> > Elizabeth Zaenger <liz at eecs.umich.edu> writes:
> >
> > > expire begin Mon Apr 1 12:10:24 EST 2002: (-v1)
> > > dbz.c:1283 Can't malloc 259001196 bytes: Cannot allocate memoryexpire end Mon Apr 1 12:10:27 EST 2002
> >
> > You ran out of memory when the history hash spilled from one table to
> > two (or from two to three etc.).
> >
> >
> > --
> > Alex Kiernan, Principal Engineer, Development, Thus PLC
> >
> >
--
Alex Kiernan, Principal Engineer, Development, Thus PLC
More information about the inn-workers
mailing list