Hi misc@ I upgraded my mail server to an amd64 snapshot from Sep 2nd and found the server stuck delivering mail in the morning with spamassasin churning at 90% CPU usage.
Quick investigation lead me to a huge bayes_toks file of 65.3G in /var/spampd/.spamassasin/. $ ls -alh total 4738352 drwx------ 2 _spampd _spampd 512B Sep 4 10:00 . drwxr-xr-x 3 _spampd _spampd 512B Sep 3 15:57 .. -rw------- 1 _spampd _spampd 36B Sep 4 09:53 bayes.lock -rw------- 1 _spampd _spampd 9.8M Sep 3 22:52 bayes_seen -rw------- 1 _spampd _spampd 65.3G Sep 3 22:55 bayes_toks $ file bayes_toks bayes_toks: Berkeley DB 1.85 (Hash, version 2, native byte-order) Interestingly I don't see that much space used with df (anyone knows why?): $ df -h Filesystem Size Used Avail Capacity Mounted on /dev/sd0a 1008M 90.1M 868M 9% / /dev/sd0k 9.8G 80.3M 9.3G 1% /home /dev/sd0d 3.9G 118K 3.7G 0% /tmp /dev/sd0f 3.9G 1.0G 2.7G 28% /usr /dev/sd0g 1001M 212M 738M 22% /usr/X11R6 /dev/sd0h 9.8G 572M 8.8G 6% /usr/local /dev/sd0j 3.9G 2.0K 3.7G 0% /usr/obj /dev/sd0i 2.0G 2.0K 1.9G 0% /usr/src /dev/sd0e 598G 4.3G 564G 1% /var I removed the file and disk usage dropped by 2.3G on /var. Did anyone experience issues with spamassasin/spampd similar to the one reported above? p5-Mail-SpamAssassin-3.4.1p2 (installed) spampd-2.30p3 (installed) After deleting the file, restarting the service processing a single email brought the DB to reported size 37.9M, few emails later it's already reported as 113M I have a hunch that it will bloat again really fast. Regards, Adam
