You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ruleqa@spamassassin.apache.org by Bill Cole <bi...@apache.org> on 2022/06/15 02:38:25 UTC
Re: RuleQA is broken.
On 2022-06-14 at 09:41:30 UTC-0400 (Tue, 14 Jun 2022 09:41:30 -0400)
Bill Cole <sy...@spamassassin.apache.org>
is rumored to have said:
> I see no QA runs since 2022-06-06. Anyone have insight to this?
OK, it seems to me that what has happened is that we've run out of
masscheck logs. With zero logs, we definitely shouldn't be rescoring and
have nothing for the QA site to show.
I'm unable to dig deeply into this any time before the weekend.
--
Bill Cole
Re: RuleQA is broken.
Posted by Benny Pedersen <me...@junc.eu>.
On 2022-06-15 14:15, Henrik K wrote:
> On Tue, Jun 14, 2022 at 10:38:25PM -0400, Bill Cole wrote:
>> On 2022-06-14 at 09:41:30 UTC-0400 (Tue, 14 Jun 2022 09:41:30 -0400)
>> Bill Cole <sy...@spamassassin.apache.org>
>> is rumored to have said:
>>
>> > I see no QA runs since 2022-06-06. Anyone have insight to this?
>>
>> OK, it seems to me that what has happened is that we've run out of
>> masscheck
>> logs. With zero logs, we definitely shouldn't be rescoring and have
>> nothing
>> for the QA site to show.
>>
>> I'm unable to dig deeply into this any time before the weekend.
>
> Seems server reboot 8 days ago left a stale lockdir for
> /usr/local/spamassassin/automc/bin/runRuleQArefresh.sh. The locking
> mechanism is so dumb that I can't be bothered to rewrite it.
>
> Solution for next time:
> rm -rf /usr/local/spamassassin/automc/tmp/runRuleQArefresh
use tmpfs not ssd storage :=)
Re: RuleQA is broken.
Posted by Henrik K <he...@hege.li>.
On Tue, Jun 14, 2022 at 10:38:25PM -0400, Bill Cole wrote:
> On 2022-06-14 at 09:41:30 UTC-0400 (Tue, 14 Jun 2022 09:41:30 -0400)
> Bill Cole <sy...@spamassassin.apache.org>
> is rumored to have said:
>
> > I see no QA runs since 2022-06-06. Anyone have insight to this?
>
> OK, it seems to me that what has happened is that we've run out of masscheck
> logs. With zero logs, we definitely shouldn't be rescoring and have nothing
> for the QA site to show.
>
> I'm unable to dig deeply into this any time before the weekend.
Seems server reboot 8 days ago left a stale lockdir for
/usr/local/spamassassin/automc/bin/runRuleQArefresh.sh. The locking
mechanism is so dumb that I can't be bothered to rewrite it.
Solution for next time:
rm -rf /usr/local/spamassassin/automc/tmp/runRuleQArefresh
Re: RuleQA is broken.
Posted by Henrik K <he...@hege.li>.
On Tue, Jun 14, 2022 at 10:38:25PM -0400, Bill Cole wrote:
> On 2022-06-14 at 09:41:30 UTC-0400 (Tue, 14 Jun 2022 09:41:30 -0400)
> Bill Cole <sy...@spamassassin.apache.org>
> is rumored to have said:
>
> > I see no QA runs since 2022-06-06. Anyone have insight to this?
>
> OK, it seems to me that what has happened is that we've run out of masscheck
> logs. With zero logs, we definitely shouldn't be rescoring and have nothing
> for the QA site to show.
>
> I'm unable to dig deeply into this any time before the weekend.
Seems server reboot 8 days ago left a stale lockdir for
/usr/local/spamassassin/automc/bin/runRuleQArefresh.sh. The locking
mechanism is so dumb that I can't be bothered to rewrite it.
Solution for next time:
rm -rf /usr/local/spamassassin/automc/tmp/runRuleQArefresh