maia_sa_rules_trigered is huge (6.6 million records)

OK. Thanks everyone for the replies. It sounds like my problem is not in the size of the database. Then I’m guessing that it has to do with the combination of components involved.

 

I’m going to post what I’m running below and let you guys see whether you see anything that is known to be problematic.

 

This is a virtual server on a XenServer 4.0 box. All systems run awesome on this platform, so I don’t think virtualization is the problem, but maybe.

We’re running a Quad-core Xeon and have allocated 3 cores to this VM. If we cat /proc/cpu-info we see all 3 CPUs. We’ve also allocated 4GB RAM that is totally dedicated to this VM.

 

Other setup is as follows:

 

Debian Etch

Kernel from cat /proc/version - Linux version 2.6.18.xs4.0.1.900.5799

MySql Server: 5.0.32-7etch5

Maia: 1.0.2a

Spamassassin: 3.2.3-0.volatile1

Clamav-daemon: 0.91.2-1~volatile1

 

Also, we are running the following maint scripts through the amavis user’;s crontab:

 

  0  0  *  *  * /usr/bin/sa-update && /var/amavisd/maia/scripts/load-sa-rules.pl && /etc/init.d/amavisd reload

  30 *  *  *  * /var/amavisd/maia/scripts/process-quarantine.pl > /dev/null

  0  *  *  *  * /var/amavisd/maia/scripts/stats-snapshot.pl > /dev/null

  30 3  *  *  * /var/amavisd/maia/scripts/expire-quarantine-cache.pl

  0  5  *  *  1 /var/amavisd/maia/scripts/send-quarantine-reminders.pl > /dev/null

*/10 *  *  *  * /var/amavisd/maia/scripts/send-quarantine-digests.pl > /dev/null

  0  1  *  *  * /usr/bin/sa-learn --sync --force-expire

  0  4  *  *  * /var/amavisd/maia/scripts/maiadbtool.pl --prune-awl 10 > /dev/null

 

As with my previous post, I REALLY appreciate any help that you guys can give me.

 

Thanks,

__

Douglas Mortensen

 

           ;   CCNA

           ; A+, Linux+, Network+