Thanks, I have reduced the size in local.cf - bayes_expiry_max_db_size 80000, however this has no effect because token expiry never takes place and the database just grows and grows, this is what check_bayes_db looks like. Note that no tokens have expired even though the last expiry ran today and there are over 4 million tokens in the db.
0.000 0 2 0 non-token data: bayes db version 0.000 0 632763 0 non-token data: nspam 0.000 0 619631 0 non-token data: nham 0.000 0 4176952 0 non-token data: ntokens 0.000 0 952965268 0 non-token data: oldest atime 0.000 0 1735776000 0 non-token data: newest atime 0.000 0 1092751853 0 non-token data: last journal sync atime 0.000 0 1092721838 0 non-token data: last expiry atime 0.000 0 736899888 0 non-token data: last expire atime delta 0.000 0 0 0 non-token data: last expire reduction count Emails now take nearly 30 seconds to process through spamassassin, see the maillog below. I agree that the timestamps on the tokens are corrupt. What are my options? Are there any tools available for fixing an SA 2.60 database or should I get rid of the database completely and start over again? Thanks, Zoe Aug 17 00:05:02 mail-in-1 spamd[82829]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:03 mail-in-1 spamd[82832]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:10 mail-in-1 spamd[82829]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:10 mail-in-1 spamd[82838]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:10 mail-in-1 spamd[82829]: identified spam (7.9/5.0) for exim:99 in 16.6 seconds, 2246 bytes. Aug 17 00:05:10 mail-in-1 spamd[82836]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:11 mail-in-1 spamd[82843]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:11 mail-in-1 spamd[82832]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:11 mail-in-1 spamd[82832]: identified spam (9.3/5.0) for exim:99 in 17.4 seconds, 2125 bytes. Aug 17 00:05:13 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 3987 Aug 17 00:05:13 mail-in-1 spamd[82862]: processing message <[EMAIL PROTECTED]> for exim:99. Aug 17 00:05:15 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 3988 Aug 17 00:05:15 mail-in-1 spamd[82864]: processing message <[EMAIL PROTECTED]> for exim:99. Aug 17 00:05:19 mail-in-1 spamd[82836]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:20 mail-in-1 spamd[82838]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:20 mail-in-1 spamd[82838]: clean message (2.2/5.0) for exim:99 in 20.4 seconds, 28360 bytes. Aug 17 00:05:22 mail-in-1 spamd[82843]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:22 mail-in-1 spamd[82843]: clean message (-0.6/5.0) for exim:99 in 20.5 seconds, 4272 bytes. Aug 17 00:05:23 mail-in-1 spamd[82864]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:24 mail-in-1 spamd[82862]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:24 mail-in-1 spamd[82836]: clean message (-1.8/5.0) for exim:99 in 25.7 seconds, 27514 bytes. Aug 17 00:05:25 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 3994 Aug 17 00:05:25 mail-in-1 spamd[82874]: processing message <[EMAIL PROTECTED]> for exim:99. Aug 17 00:05:28 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 3997 Aug 17 00:05:28 mail-in-1 spamd[82878]: processing message <[EMAIL PROTECTED]> for exim:99. Aug 17 00:05:33 mail-in-1 spamd[82862]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:33 mail-in-1 spamd[82864]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:33 mail-in-1 spamd[82874]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:36 mail-in-1 spamd[82862]: clean message (-0.6/5.0) for exim:99 in 23.0 seconds, 17989 bytes. Aug 17 00:05:37 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 4001 Aug 17 00:05:37 mail-in-1 spamd[82884]: processing message <[EMAIL PROTECTED]> for exim:99. Aug 17 00:05:38 mail-in-1 spamd[82864]: identified spam (8.8/5.0) for exim:99 in 23.1 seconds, 4567 bytes. Aug 17 00:05:38 mail-in-1 spamd[82878]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Zo� Rogers dns ltd 83 princes street, edinburgh, eh2 2er t: +44 (0) 870 085 8555 f: +44 (0) 870 085 8556 m: +44 (0) 776 475 7127 w: www.dns.co.uk -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: 05 August 2004 18:16 To: Rogers, Zo� A.; Fraser, Stuart J.; Rogers, Zo� A.; [EMAIL PROTECTED] Subject: Re: Bayes database At 12:00 PM 8/5/2004, Rogers, Zo� A. wrote: >I'm still trying to reduce the size of our bayes database. I've tried >putting bayes_expiry_max_db_size 1000000 into local.cf and restarting >services - this didn't have much effect > If you're trying to REDUCE the size of your bayes database, don't increase the value of bayes_expiry_max_db_size... decrease it. However, your problem is not related to this setting. It's related to the timestamps on your tokens being corrupt. --------------------------------------------------- This email from dns has been validated by dnsMSS Managed Email Security and is free from all known viruses. For further information contact [EMAIL PROTECTED]
