You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@spamassassin.apache.org on 2021/04/18 10:31:51 UTC

[Bug 3563] rethink Bayes locking to avoid "db version 0" warnings

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=3563

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |6901
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
                 CC|                            |apache@hege.li

--- Comment #12 from Henrik Krohns <ap...@hege.li> ---
Closing as Bug 6901 supposedly fixed this.


Referenced Bugs:

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6901
[Bug 6901] untie db first to fix "bayes db version 0 is not able to be used,
aborting!" problem
-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: [Bug 3563] rethink Bayes locking to avoid "db version 0" warnings

Posted by John Hardin <jh...@impsec.org>.
On Sun, 9 May 2021, Henrik K wrote:

> On Tue, Apr 20, 2021 at 07:21:04AM -0700, John Hardin wrote:
>> On Sun, 18 Apr 2021, bugzilla-daemon@spamassassin.apache.org wrote:
>>
>>> Referenced Bugs:
>>>
>>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6901
>>> [Bug 6901] untie db first to fix "bayes db version 0 is not able to be used,
>>> aborting!" problem
>>
>> ...and what should pop up in last night's masscheck run but:
>>
>>   bayes: bayes db version 0 is not able to be used, aborting! at
>>   /home/jhardin-masscheck/spamassassin/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/BayesStore/DBM.pm
>> line 202.
>
> Umm..  popped in my logs too around 18-04-2021 / r1888881.  Only seems to
> happen when parallel -j=x is used.
>
> There shouldn't be any reason to have Bayes plugin active in masschecks
> anyway, it just wastes CPU time tokenizing stuff.  It always starts from an
> empty database and bayes_auto_learn 0 is set, so it really doesn't do
> anything.
>
> Not sure why it's not default in automasscheck-minimal.sh, but everyone
> should add --cf 'use_bayes 0' to run_masscheck arguments or CUSTOM_PREFS.

+1, that's what I did.


-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org                         pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   It is not the business of government to make men virtuous
   or religious, or to preserve the fool from the consequences
   of his own folly.                                   -- Henry George
-----------------------------------------------------------------------
  5 days until the 73rd anniversary of Israel's independence

Re: [Bug 3563] rethink Bayes locking to avoid "db version 0" warnings

Posted by John Hardin <jh...@impsec.org>.
On Sun, 9 May 2021, Henrik K wrote:

> On Tue, Apr 20, 2021 at 07:21:04AM -0700, John Hardin wrote:
>> On Sun, 18 Apr 2021, bugzilla-daemon@spamassassin.apache.org wrote:
>>
>>> Referenced Bugs:
>>>
>>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6901
>>> [Bug 6901] untie db first to fix "bayes db version 0 is not able to be used,
>>> aborting!" problem
>>
>> ...and what should pop up in last night's masscheck run but:
>>
>>   bayes: bayes db version 0 is not able to be used, aborting! at
>>   /home/jhardin-masscheck/spamassassin/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/BayesStore/DBM.pm
>> line 202.
>
> Umm..  popped in my logs too around 18-04-2021 / r1888881.  Only seems to
> happen when parallel -j=x is used.
>
> There shouldn't be any reason to have Bayes plugin active in masschecks
> anyway, it just wastes CPU time tokenizing stuff.  It always starts from an
> empty database and bayes_auto_learn 0 is set, so it really doesn't do
> anything.
>
> Not sure why it's not default in automasscheck-minimal.sh, but everyone
> should add --cf 'use_bayes 0' to run_masscheck arguments or CUSTOM_PREFS.

+1, that's what I did.


-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org                         pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   It is not the business of government to make men virtuous
   or religious, or to preserve the fool from the consequences
   of his own folly.                                   -- Henry George
-----------------------------------------------------------------------
  5 days until the 73rd anniversary of Israel's independence

Re: [Bug 3563] rethink Bayes locking to avoid "db version 0" warnings

Posted by Henrik K <he...@hege.li>.
On Tue, Apr 20, 2021 at 07:21:04AM -0700, John Hardin wrote:
> On Sun, 18 Apr 2021, bugzilla-daemon@spamassassin.apache.org wrote:
> 
> > https://bz.apache.org/SpamAssassin/show_bug.cgi?id=3563
> > 
> > Henrik Krohns <ap...@hege.li> changed:
> > 
> >           What    |Removed                     |Added
> > ----------------------------------------------------------------------------
> >         Depends on|                            |6901
> >             Status|NEW                         |RESOLVED
> >         Resolution|---                         |FIXED
> >                 CC|                            |apache@hege.li
> > 
> > --- Comment #12 from Henrik Krohns <ap...@hege.li> ---
> > Closing as Bug 6901 supposedly fixed this.
> > 
> > 
> > Referenced Bugs:
> > 
> > https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6901
> > [Bug 6901] untie db first to fix "bayes db version 0 is not able to be used,
> > aborting!" problem
> 
> ...and what should pop up in last night's masscheck run but:
> 
>   bayes: bayes db version 0 is not able to be used, aborting! at
>   /home/jhardin-masscheck/spamassassin/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/BayesStore/DBM.pm
> line 202.

Umm..  popped in my logs too around 18-04-2021 / r1888881.  Only seems to
happen when parallel -j=x is used.

There shouldn't be any reason to have Bayes plugin active in masschecks
anyway, it just wastes CPU time tokenizing stuff.  It always starts from an
empty database and bayes_auto_learn 0 is set, so it really doesn't do
anything.

Not sure why it's not default in automasscheck-minimal.sh, but everyone
should add --cf 'use_bayes 0' to run_masscheck arguments or CUSTOM_PREFS.


Re: [Bug 3563] rethink Bayes locking to avoid "db version 0" warnings

Posted by Henrik K <he...@hege.li>.
On Tue, Apr 20, 2021 at 07:21:04AM -0700, John Hardin wrote:
> On Sun, 18 Apr 2021, bugzilla-daemon@spamassassin.apache.org wrote:
> 
> > https://bz.apache.org/SpamAssassin/show_bug.cgi?id=3563
> > 
> > Henrik Krohns <ap...@hege.li> changed:
> > 
> >           What    |Removed                     |Added
> > ----------------------------------------------------------------------------
> >         Depends on|                            |6901
> >             Status|NEW                         |RESOLVED
> >         Resolution|---                         |FIXED
> >                 CC|                            |apache@hege.li
> > 
> > --- Comment #12 from Henrik Krohns <ap...@hege.li> ---
> > Closing as Bug 6901 supposedly fixed this.
> > 
> > 
> > Referenced Bugs:
> > 
> > https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6901
> > [Bug 6901] untie db first to fix "bayes db version 0 is not able to be used,
> > aborting!" problem
> 
> ...and what should pop up in last night's masscheck run but:
> 
>   bayes: bayes db version 0 is not able to be used, aborting! at
>   /home/jhardin-masscheck/spamassassin/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/BayesStore/DBM.pm
> line 202.

Umm..  popped in my logs too around 18-04-2021 / r1888881.  Only seems to
happen when parallel -j=x is used.

There shouldn't be any reason to have Bayes plugin active in masschecks
anyway, it just wastes CPU time tokenizing stuff.  It always starts from an
empty database and bayes_auto_learn 0 is set, so it really doesn't do
anything.

Not sure why it's not default in automasscheck-minimal.sh, but everyone
should add --cf 'use_bayes 0' to run_masscheck arguments or CUSTOM_PREFS.


Re: [Bug 3563] rethink Bayes locking to avoid "db version 0" warnings

Posted by John Hardin <jh...@impsec.org>.
On Sun, 18 Apr 2021, bugzilla-daemon@spamassassin.apache.org wrote:

> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=3563
>
> Henrik Krohns <ap...@hege.li> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>         Depends on|                            |6901
>             Status|NEW                         |RESOLVED
>         Resolution|---                         |FIXED
>                 CC|                            |apache@hege.li
>
> --- Comment #12 from Henrik Krohns <ap...@hege.li> ---
> Closing as Bug 6901 supposedly fixed this.
>
>
> Referenced Bugs:
>
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6901
> [Bug 6901] untie db first to fix "bayes db version 0 is not able to be used,
> aborting!" problem

...and what should pop up in last night's masscheck run but:

   bayes: bayes db version 0 is not able to be used, aborting! at
   /home/jhardin-masscheck/spamassassin/masscheckwork/nightly_mass_check/masses/../lib/Mail/SpamAssassin/BayesStore/DBM.pm 
line 202.


-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org                         pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79