Ron Freidel wrote:
> Hi All,
>
> We run a relatively small (amount of clients) freebsd email hosting
> server, was running spamassassin: 3.0.2 on a qmail server. We took on a
> new client who was recieving alot of spam, as their old provider kept
> telling them there was nothing that could be done about spam.
>
> Well, our server easily handled the spam prior to this client, then
> suddenly the spam level increased from around 300 a day to about 6000 a
> day. The server itself is a quad xeon with 1Gig of ram, I plan to
> upgrade the ram tomorrow.
>
> I upgraded spamassassin to 3.1.7 to take advantage of the
> features/fixes, and to take care of the fact that while running 3.0.2
> spamassassin eventually took all available ram and swap, then died, I
> had to reboot anyway so did the upgrade.
>
> After the upgrade I began seeing errors like...
> prefork: server reached --max-children setting, consider raising it
>
> This was while running spamassassin under freebsd's stock sa-spamd.sh,
> and during a "spam attack".
>
> I made this change...
> command_args="-d -m 10 -r ${pidfile}"
>
> So it is now running as...
> /usr/local/bin/spamd -c -d -m 10 -r /var/run/spamd/spamd.pid
> (perl5.8.5) root
>
> Now the error has changed to...
> spamd[2817]: spamd: handled cleanup of child pid 9679 due to SIGCHLD
> spamd[2817]:Use of uninitialized value in numeric
> eq (==)
> at /usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm
> line 689
>
> And here's line 689
> 687 foreach my $pid (@pids) {
> 688 my $k = $kids->{$pid};
> 689 if ($k == PFSTATE_IDLE) {
> 690 $statestr .= 'I';
> 691 $num_idle++;
>
> Is this truely a problem with spamassassin? Or could I have a problem
> elsewhere? Do I need to make an additional change in how it is running?
>
> All perl mods and cpan have been updated to latest versions, --lint
> contains no errors.
>
--
This may seem dumb, but change "-m 10" to "-m10". My command line has
"-m5" with no space.
Steve
