bayes expire tokens

Julian Field MailScanner at ecs.soton.ac.uk
Tue Mar 8 22:05:30 GMT 2005 

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Looks like I need to take another look at this again.
One process doing a Bayes rebuild should lock out all the other
processes from trying to use SA, or it should make them wait.
What is the value of your "Wait For Bayes Rebuild" setting?

It may be a little while until I manage to fix this, but it is top of
the list of problems to be resolved.

Fortunately I have just had a new server delivered this afternoon, and
should get my hands on it tomorrow morning, so I will be able to try out
some of this stuff on a clean system.

Official (and unofficial) thanks are due to the University of
Southampton for their very kind donation of a new testing server. I
intend making good use of it.

Chris Conn wrote:

>>> Am I doing something wrong?  I have read and re-read the docs regarding
>>> this and I have never been able to not have these annoying expire files
>>> appear.
>>
>>
>>
>> Very good question. I don't know the answer to that one at the moment.
>>
>
> Hello,
>
> Does this mean I am alone?  I have 3 servers that do this, however they
> are in essense clones of each other (they were 12 months ago when they
> were set up, they have been upgraded MailScanner versions independantly
> since then).  I am not running spamd and  only MailScanner can reference
> SpamAssassin on these boxes.
>
> More logs I found:
>
> Mar  7 22:03:10 mx2 MailScanner[10568]: Delete bayes lockfile for 11073
> Mar  7 22:13:26 mx2 MailScanner[10568]: Delete bayes lockfile for 12709
> Mar  7 22:19:20 mx2 MailScanner[10568]: Delete bayes lockfile for 13541
> Mar  7 22:24:35 mx2 MailScanner[10568]: Delete bayes lockfile for 14207
> Mar  7 22:30:06 mx2 MailScanner[10568]: Delete bayes lockfile for 15013
> Mar  7 22:35:15 mx2 MailScanner[10568]: Delete bayes lockfile for 15666
> Mar  7 22:40:20 mx2 MailScanner[10568]: Delete bayes lockfile for 16569
> Mar  7 22:46:09 mx2 MailScanner[10568]: Delete bayes lockfile for 17311
> Mar  7 22:51:13 mx2 MailScanner[10568]: Delete bayes lockfile for 18116
> Mar  7 22:56:33 mx2 MailScanner[10568]: Delete bayes lockfile for 18905
> Mar  7 23:01:55 mx2 MailScanner[10568]: Delete bayes lockfile for 19619
> Mar  7 23:07:51 mx2 MailScanner[10568]: Delete bayes lockfile for 20537
> Mar  7 23:13:20 mx2 MailScanner[10568]: Delete bayes lockfile for 21248
> Mar  7 23:18:45 mx2 MailScanner[10568]: Delete bayes lockfile for 22052
> Mar  7 23:23:49 mx2 MailScanner[10568]: Delete bayes lockfile for 22802
> Mar  7 23:28:59 mx2 MailScanner[10568]: Delete bayes lockfile for 23494
> Mar  7 23:34:09 mx2 MailScanner[10568]: Delete bayes lockfile for 24158
> Mar  7 23:39:21 mx2 MailScanner[10568]: Delete bayes lockfile for 24781
> Mar  7 23:44:54 mx2 MailScanner[10568]: Delete bayes lockfile for 25327
> Mar  7 23:49:54 mx2 MailScanner[10568]: Delete bayes lockfile for 25930
> Mar  7 23:55:39 mx2 MailScanner[10568]: Delete bayes lockfile for 26710
> Mar  8 00:00:48 mx2 MailScanner[10568]: Delete bayes lockfile for 27390
> Mar  8 00:06:21 mx2 MailScanner[10568]: Delete bayes lockfile for 28351
> Mar  8 00:12:32 mx2 MailScanner[10568]: Delete bayes lockfile for 29198
> Mar  8 00:17:38 mx2 MailScanner[10568]: Delete bayes lockfile for 30081
> Mar  8 00:22:52 mx2 MailScanner[10568]: Delete bayes lockfile for 30748
> Mar  8 00:27:59 mx2 MailScanner[10568]: Delete bayes lockfile for 31316
> Mar  8 00:33:03 mx2 MailScanner[10568]: Delete bayes lockfile for 31978
> Mar  8 00:39:29 mx2 MailScanner[10568]: Delete bayes lockfile for 460
> Mar  8 00:44:50 mx2 MailScanner[10568]: Delete bayes lockfile for 1211
> Mar  8 00:50:33 mx2 MailScanner[10568]: Delete bayes lockfile for 1958
> Mar  8 00:55:39 mx2 MailScanner[10568]: Delete bayes lockfile for 2551
> Mar  8 01:01:16 mx2 MailScanner[10568]: Delete bayes lockfile for 3174
> Mar  8 01:06:26 mx2 MailScanner[10568]: Delete bayes lockfile for 3845
> Mar  8 01:11:36 mx2 MailScanner[10568]: Delete bayes lockfile for 4458
> Mar  8 01:16:45 mx2 MailScanner[10568]: Delete bayes lockfile for 5055
> Mar  8 01:22:37 mx2 MailScanner[10568]: Delete bayes lockfile for 5617
> Mar  8 01:28:14 mx2 MailScanner[10568]: Delete bayes lockfile for 6292
> Mar  8 01:34:25 mx2 MailScanner[10568]: Delete bayes lockfile for 6996
> Mar  8 01:40:04 mx2 MailScanner[10568]: Delete bayes lockfile for 7772
> Mar  8 01:45:13 mx2 MailScanner[10568]: Delete bayes lockfile for 8319
> Mar  8 01:51:47 mx2 MailScanner[10568]: Delete bayes lockfile for 9002
> Mar  8 01:57:52 mx2 MailScanner[10568]: Delete bayes lockfile for 9720
>
> and
>
> Mar  7 22:03:09 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 1 of 20
> Mar  7 22:13:25 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 22:19:19 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 22:24:34 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 22:30:05 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 22:35:14 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 22:40:19 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 22:46:08 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 22:51:12 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 1 of 20
> Mar  7 22:56:32 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:01:54 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:07:50 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:13:19 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:18:44 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 2 of 20
> Mar  7 23:23:48 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:28:58 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:34:08 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:39:20 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:44:53 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:49:53 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  7 23:55:38 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:00:47 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:06:20 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:12:31 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:17:37 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:22:51 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:27:58 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:33:02 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:39:28 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:44:49 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:50:32 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 00:55:38 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:01:15 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:06:25 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:11:35 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:16:44 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:22:36 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:28:13 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 2 of 20
> Mar  8 01:34:24 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:40:03 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:45:12 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:51:46 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 0 of 20
> Mar  8 01:57:51 mx2 MailScanner[10568]: SpamAssassin timed out and was
> killed, failure 1 of 20
>
> Each file was created after these events.  Is it possible that
> MailScanner is not pausing while it is doing the expiry?  I ask this
> because:
>
>
> Mar  7 21:58:12 mx2 MailScanner[10568]: Bayes database rebuild is due
> Mar  7 21:58:12 mx2 MailScanner[10568]: SpamAssassin Bayes database
> rebuild preparing
> Mar  7 21:58:12 mx2 MailScanner[10568]: SpamAssassin Bayes database
> rebuild starting
>
> and
>
> Mar  7 21:58:18 mx2 MailScanner[29837]: New Batch: Scanning 3 messages,
> 231876 bytes
> Mar  7 21:58:18 mx2 MailScanner[29837]: Spam Checks: Starting
>
> Mar  7 21:59:38 mx2 MailScanner[10568]: SpamAssassin Bayes database
> rebuild completed
> Mar  7 21:59:38 mx2 MailScanner[10568]: Rebuilding SpamAssassin Bayes
> database
>
> Mar  7 21:59:51 mx2 MailScanner[29837]: Message j282w4N6010556 from
> 210.243.155
> Mar  7 21:59:51 mx2 MailScanner[29837]: Spam Checks: Found 1 spam
> messages
> Mar  7 21:59:51 mx2 MailScanner[29837]: Spam Actions: message
> j282w4N6010556 ac
> Mar  7 21:59:52 mx2 MailScanner[29837]: Virus and Content Scanning:
> Starting
> Mar  7 21:59:52 mx2 MailScanner[29837]: Content Checks: Detected and
> will disar
> Mar  7 21:59:52 mx2 MailScanner[29837]: Uninfected: Delivered 2 messages
> Mar  7 21:59:52 mx2 MailScanner[29837]: MailScanner child dying of old
> age
> Mar  7 21:59:52 mx2 MailScanner[10673]: MailScanner E-Mail Virus Scanner
> versio
>
> Another MailScanner child was scanning while the first one was
> rebuilding?
>
> Thanks again,
>
> Chris
>
> ------------------------ MailScanner list ------------------------
> To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
> 'leave mailscanner' in the body of the email.
> Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
> the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).
>
> Support MailScanner development - buy the book off the website!
>

--
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!

More information about the MailScanner mailing list