You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ruleqa@spamassassin.apache.org by Jari Fredrisson <ja...@iki.fi> on 2014/11/04 11:56:06 UTC

My submission

I have some problems now, have to use an old VM with two cores only, and my run takes 12 hours.

This submission yesterday did not make it to the results? What is the problem? The time is in EET.

Does it take so long that the downloaded mass-check package is too old when this arrives?

br. jarif

Syncing nightly_mass_check
+ ./mass-check --hamlog=ham-jarif.log --spamlog=spam-jarif.log -j 2 --progress --reuse ham:dir:/home/jarif/Maildir/.Confirmed-HAM spam:dir:/home/jarif/Maildir/.Confirmed-SPAM
status: starting scan stage                              now: 2014-11-03 05:00:12
status: completed scan stage, 64432 messages             now: 2014-11-03 06:38:22
status: starting run stage                               now: 2014-11-03 06:38:22
status:  10% ham: 5580   spam: 864    date: 2011-09-21   now: 2014-11-03 07:41:19
status:  20% ham: 11158  spam: 1730   date: 2012-04-29   now: 2014-11-03 08:43:43
status:  30% ham: 16736  spam: 2596   date: 2012-08-15   now: 2014-11-03 09:29:37
status:  40% ham: 22315  spam: 3461   date: 2014-08-16   now: 2014-11-03 10:25:51
status:  50% ham: 27891  spam: 4329   date: 2013-03-29   now: 2014-11-03 11:26:16
status:  60% ham: 33464  spam: 5200   date: 2013-07-30   now: 2014-11-03 12:26:24
status:  70% ham: 39037  spam: 6071   date: 2013-11-06   now: 2014-11-03 13:24:20
status:  80% ham: 44614  spam: 6938   date: 2014-03-04   now: 2014-11-03 14:17:12
status:  90% ham: 50189  spam: 7807   date: 2014-07-23   now: 2014-11-03 15:30:08
status: completed run stage                              now: 2014-11-03 16:31:11
+ LOGLIST=' ham-jarif.log spam-jarif.log'
+ set +x
rsync -Pcqz  ham-jarif.log spam-jarif.log ....


Re: My submission

Posted by Jari Fredrisson <ja...@iki.fi>.
On 4.11.2014 13:22, Axb wrote:
> iirc, you need to submit after 9 AM GMT which means starting the
> masscheck, in your case at 11:00 EET
>
> if you start before that you risk the logs landing in "yesterday'" job.
>
> I know it may not make sense... but that is what I'm doing...
>

Thanks, I'll discuss with my crontab.

br. jarif

>
> On 11/04/2014 11:56 AM, Jari Fredrisson wrote:
>> I have some problems now, have to use an old VM with two cores only,
>> and my run takes 12 hours.
>>
>> This submission yesterday did not make it to the results? What is the
>> problem? The time is in EET.
>>
>> Does it take so long that the downloaded mass-check package is too
>> old when this arrives?
>>
>> br. jarif
>>
>> Syncing nightly_mass_check
>> + ./mass-check --hamlog=ham-jarif.log --spamlog=spam-jarif.log -j 2
>> --progress --reuse ham:dir:/home/jarif/Maildir/.Confirmed-HAM
>> spam:dir:/home/jarif/Maildir/.Confirmed-SPAM
>> status: starting scan stage                              now:
>> 2014-11-03 05:00:12
>> status: completed scan stage, 64432 messages             now:
>> 2014-11-03 06:38:22
>> status: starting run stage                               now:
>> 2014-11-03 06:38:22
>> status:  10% ham: 5580   spam: 864    date: 2011-09-21   now:
>> 2014-11-03 07:41:19
>> status:  20% ham: 11158  spam: 1730   date: 2012-04-29   now:
>> 2014-11-03 08:43:43
>> status:  30% ham: 16736  spam: 2596   date: 2012-08-15   now:
>> 2014-11-03 09:29:37
>> status:  40% ham: 22315  spam: 3461   date: 2014-08-16   now:
>> 2014-11-03 10:25:51
>> status:  50% ham: 27891  spam: 4329   date: 2013-03-29   now:
>> 2014-11-03 11:26:16
>> status:  60% ham: 33464  spam: 5200   date: 2013-07-30   now:
>> 2014-11-03 12:26:24
>> status:  70% ham: 39037  spam: 6071   date: 2013-11-06   now:
>> 2014-11-03 13:24:20
>> status:  80% ham: 44614  spam: 6938   date: 2014-03-04   now:
>> 2014-11-03 14:17:12
>> status:  90% ham: 50189  spam: 7807   date: 2014-07-23   now:
>> 2014-11-03 15:30:08
>> status: completed run stage                              now:
>> 2014-11-03 16:31:11
>> + LOGLIST=' ham-jarif.log spam-jarif.log'
>> + set +x
>> rsync -Pcqz  ham-jarif.log spam-jarif.log ....
>>
>>
>



Re: My submission

Posted by Axb <ax...@gmail.com>.
iirc, you need to submit after 9 AM GMT which means starting the 
masscheck, in your case at 11:00 EET

if you start before that you risk the logs landing in "yesterday'" job.

I know it may not make sense... but that is what I'm doing...


On 11/04/2014 11:56 AM, Jari Fredrisson wrote:
> I have some problems now, have to use an old VM with two cores only, and my run takes 12 hours.
>
> This submission yesterday did not make it to the results? What is the problem? The time is in EET.
>
> Does it take so long that the downloaded mass-check package is too old when this arrives?
>
> br. jarif
>
> Syncing nightly_mass_check
> + ./mass-check --hamlog=ham-jarif.log --spamlog=spam-jarif.log -j 2 --progress --reuse ham:dir:/home/jarif/Maildir/.Confirmed-HAM spam:dir:/home/jarif/Maildir/.Confirmed-SPAM
> status: starting scan stage                              now: 2014-11-03 05:00:12
> status: completed scan stage, 64432 messages             now: 2014-11-03 06:38:22
> status: starting run stage                               now: 2014-11-03 06:38:22
> status:  10% ham: 5580   spam: 864    date: 2011-09-21   now: 2014-11-03 07:41:19
> status:  20% ham: 11158  spam: 1730   date: 2012-04-29   now: 2014-11-03 08:43:43
> status:  30% ham: 16736  spam: 2596   date: 2012-08-15   now: 2014-11-03 09:29:37
> status:  40% ham: 22315  spam: 3461   date: 2014-08-16   now: 2014-11-03 10:25:51
> status:  50% ham: 27891  spam: 4329   date: 2013-03-29   now: 2014-11-03 11:26:16
> status:  60% ham: 33464  spam: 5200   date: 2013-07-30   now: 2014-11-03 12:26:24
> status:  70% ham: 39037  spam: 6071   date: 2013-11-06   now: 2014-11-03 13:24:20
> status:  80% ham: 44614  spam: 6938   date: 2014-03-04   now: 2014-11-03 14:17:12
> status:  90% ham: 50189  spam: 7807   date: 2014-07-23   now: 2014-11-03 15:30:08
> status: completed run stage                              now: 2014-11-03 16:31:11
> + LOGLIST=' ham-jarif.log spam-jarif.log'
> + set +x
> rsync -Pcqz  ham-jarif.log spam-jarif.log ....
>
>