You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Theo Van Dinter <fe...@apache.org> on 2006/10/13 16:40:26 UTC
Nightly run OOMs during scan...
Second day in a row, I haven't started debugging yet, but fyi.
-----
status: starting scan stage now: 2006-10-13 05:11:54
Out of memory!
mass-check: no messages to process
-----
--
Randomly Selected Tagline:
"Good news, good news abounds." - Prof. Branche
Re: Nightly run OOMs during scan...
Posted by Duncan Findlay <du...@debian.org>.
On Fri, Oct 13, 2006 at 10:40:26AM -0400, Theo Van Dinter wrote:
> Second day in a row, I haven't started debugging yet, but fyi.
I've been getting "too many open files" for a few weeks now. Also
haven't debugged.
--
Duncan Findlay
Re: Nightly run OOMs during scan...
Posted by Theo Van Dinter <fe...@apache.org>.
On Fri, Oct 13, 2006 at 10:40:26AM -0400, Theo Van Dinter wrote:
> Second day in a row, I haven't started debugging yet, but fyi.
> -----
> status: starting scan stage now: 2006-10-13 05:11:54
> Out of memory!
> mass-check: no messages to process
> -----
Hrm. Lame. It really is OOMing, just because of the number of messages, and
the fact that it's all stored in RAM during the scan. We'll have to fix that.
For now, I played some reference games and got it to not use as much memory
for -n:
status: completed scan stage, 343891 messages now: 2006-10-19 03:31:18 PM
I'll open a ticket for 3.2 about it. <sigh>
--
Randomly Selected Tagline:
"The universe is already insane, anything else would be redundant."
- Londo on Babylon 5