Re: Rule updates are too old - 2018-03-11 3.3.2:2018-03-10
+1 thanks to you and Dave for your help! -- Kevin A. McGrail Asst. Treasurer & VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Sun, Mar 11, 2018 at 1:49 PM, wrote: > On 03/11, dar...@chaosreigns.com wrote: > > > @darxus, do you know what is going on here with this script? We have > had > > > plenty of corpora for many months now but this email just started > showing up > > > a few days ago. > > > > I have a feeling the updates aren't completing before this script is > > running. Still looking. > > Yup. These are dates and times, and rule versions: > > 2018-03-08-22-30 3.3.2 1826085 > 2018-03-08-22-35 3.3.2 1826189 > > 2018-03-09-04-00 3.3.2 1826189 > 2018-03-09-04-05 3.3.2 1826303 > > 2018-03-10-03-50 3.3.2 1826303 > 2018-03-10-03-55 3.3.2 1826397 > > 2018-03-11-05-35 3.3.2 1826397 > 2018-03-11-05-40 3.3.2 1826431 > > So it last updated between 5:35 and 5:40am. And my script ran at 5am. > > I changed my cron job to run at 7am. > > Thanks for pointing this out to me. >
Re: Rule updates are too old - 2018-03-11 3.3.2:2018-03-10
On 03/11, dar...@chaosreigns.com wrote: > > @darxus, do you know what is going on here with this script? We have had > > plenty of corpora for many months now but this email just started showing up > > a few days ago. > > I have a feeling the updates aren't completing before this script is > running. Still looking. Yup. These are dates and times, and rule versions: 2018-03-08-22-30 3.3.2 1826085 2018-03-08-22-35 3.3.2 1826189 2018-03-09-04-00 3.3.2 1826189 2018-03-09-04-05 3.3.2 1826303 2018-03-10-03-50 3.3.2 1826303 2018-03-10-03-55 3.3.2 1826397 2018-03-11-05-35 3.3.2 1826397 2018-03-11-05-40 3.3.2 1826431 So it last updated between 5:35 and 5:40am. And my script ran at 5am. I changed my cron job to run at 7am. Thanks for pointing this out to me.
Re: Rule updates are too old - 2018-03-11 3.3.2:2018-03-10
On 03/11/2018 12:08 PM, dar...@chaosreigns.com wrote: On 03/11, Dave Jones wrote: On 03/11/2018 04:00 AM, dar...@chaosreigns.com wrote: SpamAssassin version 3.3.2 has not had a rule update since 2018-03-10. 20180310: Spam and ham are above threshold of 150,000: http://ruleqa.spamassassin.org/?daterev=20180310 20180310: Spam: 416659, Ham: 418483 The spam and ham counts on which this script alerts are from http://ruleqa.spamassassin.org/?daterev=20180310 Click "(source details)" (it's tiny and low contrast). It's from the second and third columns of the line that ends with "(all messages)" The source to this script is http://www.chaosreigns.com/sa/update-version-mon.pl It looks like both the weekly and nightly masschecks need to have sufficient corpora in order for an update to be generated. @darxus, do you know what is going on here with this script? We have had plenty of corpora for many months now but this email just started showing up a few days ago. I have a feeling the updates aren't completing before this script is running. Still looking. We are over 800,000 messages in our ham/spam corpora with it nearly 50/50 which is really good. My ena-week* are about half of the 800K messsages. Did someone in the ruleqa group bump up their corpus sizes significantly in the past couple of days? Dave
Re: Rule updates are too old - 2018-03-11 3.3.2:2018-03-10
On 03/11, Dave Jones wrote: > On 03/11/2018 04:00 AM, dar...@chaosreigns.com wrote: > >SpamAssassin version 3.3.2 has not had a rule update since 2018-03-10. > > > >20180310: Spam and ham are above threshold of 150,000: > >http://ruleqa.spamassassin.org/?daterev=20180310 > >20180310: Spam: 416659, Ham: 418483 > > > > > >The spam and ham counts on which this script alerts are from > >http://ruleqa.spamassassin.org/?daterev=20180310 > >Click "(source details)" (it's tiny and low contrast). > >It's from the second and third columns of the line that ends with > >"(all messages)" > > > >The source to this script is > >http://www.chaosreigns.com/sa/update-version-mon.pl > > > >It looks like both the weekly and nightly masschecks need to have sufficient > >corpora in order for an update to be generated. > > > > @darxus, do you know what is going on here with this script? We have had > plenty of corpora for many months now but this email just started showing up > a few days ago. I have a feeling the updates aren't completing before this script is running. Still looking.
Re: Rule updates are too old - 2018-03-11 3.3.2:2018-03-10
On 03/11/2018 04:00 AM, dar...@chaosreigns.com wrote: SpamAssassin version 3.3.2 has not had a rule update since 2018-03-10. 20180310: Spam and ham are above threshold of 150,000: http://ruleqa.spamassassin.org/?daterev=20180310 20180310: Spam: 416659, Ham: 418483 The spam and ham counts on which this script alerts are from http://ruleqa.spamassassin.org/?daterev=20180310 Click "(source details)" (it's tiny and low contrast). It's from the second and third columns of the line that ends with "(all messages)" The source to this script is http://www.chaosreigns.com/sa/update-version-mon.pl It looks like both the weekly and nightly masschecks need to have sufficient corpora in order for an update to be generated. @darxus, do you know what is going on here with this script? We have had plenty of corpora for many months now but this email just started showing up a few days ago. Thanks, Dave
