Bug 7121 - masscheck under limit script
Summary: masscheck under limit script
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: RuleQA (show other bugs)
Version: 3.4.1
Hardware: All All
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-21 20:19 UTC by Joe Quinn
Modified: 2018-08-25 14:28 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Darxus' script for monitoring rule updates text/x-perl None Kevin A. McGrail [HasCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Quinn 2015-01-21 20:19:52 UTC 
Darxus has a script to notify the dev list that ruleQA is under a 150k limit for spam and ham samples. The source of the script is here: http://www.chaosreigns.com/sa/update-version-mon.pl

The script does a scrape of ruleqa.spamassassin.org, but would be much better as a part of the SA repo. It can then get more support and development, and it can run on spamassassin-vm.
Comment 1 Kevin A. McGrail 2015-06-04 14:49:28 UTC 
Here's some ideas to improve the script

1 - Have the script ALSO check the DNS entries and list them in the email as well as checking ruleqa?  If DNS is changed, we published a rule, for example:


    TXT 1.4.3.updates.spamassassin.org
    TXT 0.4.3.updates.spamassassin.org
    TXT 3.3.3.updates.spamassassin.org

2 - Perhaps post the entries from the last few days?    That will show the trend much more accurately I think.

3 - In general, the script helps me know when a rule publishing did not occur but it is not always accurate.  There is a deviation between ruleqa and the masscheck scripts on counts that I have not identified the source.  

4 - The script that runs that does updates is:
    Cron <updatesd@spamassassin-vm> bash /export/home/updatesd/svn/mkupdates-with-scores/do-stable-update-with-scores

The output of that script arrives about 10:30PM Eastern and 

5 - If that script fails, it emails the ruleqa list like

[auto] do-nightly-rescore-example 8

6 - I then can look at the cron output for do-stable-update-with-scores to find out why it failed.

7 - if we publish a rule, there is a cron like Output from your job      104 from Rule Updates Daemon
Comment 2 Kevin A. McGrail 2015-06-04 14:50:00 UTC 
Created attachment 5306 [details]
Darxus' script for monitoring rule updates
Comment 3 Kevin A. McGrail 2018-08-25 14:28:01 UTC 
Dave Jones wrote a bash script and have it running on the sa-vm1 server that will (and has) notify us when the ruleQA corpus is too low.

He thinks we can close this BZ as resolved.