>From: John Hardin <jhar...@impsec.org> >>On Thu, 1 Jun 2017, David Jones wrote:
>> I am working pretty hard to get the ruleqa processing going >> again on our new server. We are so close to having enough >> contributors and ham/spam to get some new rules generated: >> This is from the run minutes ago: >> >> HAM CONTRIBUTORS FOUND: 9 (required 10) >> SPAM CONTRIBUTORS FOUND: 9 (required 10) >> >> We need to recruit some more masscheck'ers to get over the hump so I can >> do some final testing of the rules updates and start the DNS updates >> again for sa-update. >I upload my corpora, not my results - I suppose that my corpora didn't >survive the migration, and I haven't yet brought my submission bot and >rsync account up-to-date for the new hardware - my apologies. I may be >able to give that some cycles this weekend. So, about that. I just started helping as a sysadmin a month or so ago. We had some hosting issues that we are trying to recover from with very little documentation of the infrastructure 3 months ago. I am having to dig through logs, cron output, and old (outdated) documentation to try to put the puzzle back together again. If anyone has any knowledge or documentation of how things were setup in the past, I would love to talk with you. We do have backups from one of the servers but I think there were two or three servers before based on the fact that I can't find any evidence where buildbot was running that I think was running the centralized masscheck. >However, I don't recall seeing confirmation that the central masscheck was >actually working; can you confirm that? Or do I need to change over to >local masscheck and uploading results like most others do? I have not found enough details yet on the central masscheck so I have started with getting the remote masscheck processing working first so we can get sa-update going again. > P.S. After spending the past month learning how this works, I have some > ideas on how to make the nightly masschecks become hourly fairly easily > so we can test and promote rule changes faster. >How do you guarantee all the contributors can perform the checks within >an hour? Wow! I just started collecting ham/spam for masscheck back in January and my (apparently) tiny corpus only takes under a minute to run on a low end 2 core VM. I didn't realize that there would be some that take a long time to run. Still pretty new to all of this backend processing. Dave
