Mark Martinec writes: > Daryl C. W. O'Shea writes: > > > AIcache: no access to > > > /home/dos/sa-mass-check-server/scan-cache/home/dos/SA-corpus/spam/traps/n > > >ew/20080920/.spamassassin_cache: No such file or directory at > > > /home/dos/sa-mass-check-server/nightly_mass_check/masses/../lib/Mail/Spam > > >Assassin/AICache.pm line 74. > > This one is a warning. Previously it went by unnoticed. > > > > cannot open AI cache file > > > (/home/dos/sa-mass-check-server/scan-cache/home/dos/SA-corpus/spam/traps/ > > >new/20080920/.spamassassin_cache): No such file or directory at > > > /home/dos/sa-mass-check-server/nightly_mass_check/masses/../lib/Mail/Spam > > >Assassin/AICache.pm line 102. > > This one is now fatal (open failing), previously it went by unnoticed. > I'll change it to a warning to retain previous behavior, but the underlying > reason should eventually be investigated and fixed.
looking at them now -- yep, both are easily recoverable, and should not abort mass-checks. AICache files are disposable and easily rebuilt. > Theo writes: > > > I started seeing these the other day: > > Out of memory! > > mass-check: no messages to process > > It could just be that I need to allocate more memory to mass-check now, but > > the 256M limit that I've given it has run fine for a long long time and > > there were recent changes to things like ArchiveIterator which is what's > > running here... > > I don't see how any of the recent changes could cause this. > Let's keep an eye on this one. > > Mark
