Hi Agnello,
as Johann stated all SA-childs are "busy" ... so no more mail can be checked at
that point of time.
We encountered same problems on our systems (approx. 20.000 mails /day) and
looked into depth.
Normally the problems arose, when checks like FuzzyOCR took tooooo long to
complete or things hung up on the system.
So i wrote a little script which permanently (via crontab every 5 minutes)
checks my system-health and restarts sa if needed.
The script checks:
1.) wheter SA is still running (or fu**ed up)
2.) if load is to high (which normally comes from hanging sa-tasks)
and is restarting sa if needed, sends email to admin and logs to
/home/spam/hohelast.now
# Script by Ove Starckjohann - 2007-01-26 for checking SA-health
# *************************** Check if SA is running on port 783 *************
SARUNNING=`netstat -anp|grep spamd.pid|grep -c 783`
if [ $SARUNNING -lt 1 ]
then
echo "SA not running"
date >> /home/spam/hohelast.history
date > /home/spam/hohelast.now
echo "**********************************************************" >>
/home/spam/hohelast.now
top b n 1 >> /home/spam/hohelast.now
ps aux >> /home/spam/hohelast.now
sar >> /home/spam/hohelast.now
SUBJECT="ADMIN05-Warnung: hohe Systemlast - LOAD groesser 5"
mail -s "$SUBJECT" [EMAIL PROTECTED] < /home/spam/hohelast.now
exit 1
fi
# ************** Check auf hohe Systemlast LOAD groesser 5 im 15 min-Schnitt
LOADLAST=`cat /proc/loadavg|awk '{print $3 }'|cut -c1-1`
if [ $LOADLAST -ge 5 ]
then
echo "high load"
date > /home/spam/hohelast.now
date >> /home/spam/hohelast.history
echo "**********************************************************" >>
/home/spam/hohelast.now
top b n 1 >> /home/spam/hohelast.now
ps aux >> /home/spam/hohelast.now
sar >> /home/spam/hohelast.now
SUBJECT="ADMIN05-Warnung: hohe Systemlast - LOAD groesser 5"
mail -s "$SUBJECT" [EMAIL PROTECTED] < /home/spam/hohelast.now
exit 1
fi
aahh...i do have a script "sar" added which consists of these some lines:
admin05:/etc# cat /usr/bin/sar
/etc/init.d/spamassassin stop
killall spamd
killall ocrad
rm /home/spam/.spamassassin/bayes.lock*
/etc/init.d/spamassassin restart
With this script running my sa-server performs well over the last year .-)
GreetinX Ove
-----Ursprüngliche Nachricht-----
Von: Agnello George [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 7. März 2008 14:34
An: Spamassassin
Betreff: prefork: child states: BBBBBBB
I see in my log the following what does it mean ??
Fri Mar 7 21:07:12 2008 [11800] info: prefork: child states: BBBBBBB
Fri Mar 7 21:07:12 2008 [11800] info: prefork: server reached
--max-children setting, consider raising it
--
Regards
Agnello Dsouza
www.linux-vashi.blogspot.com
www.bible-study-india.blogspot.com
