You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by René Berber <r....@computer.org> on 2010/01/28 21:54:35 UTC
sa-compile and 3.3.0
Hi,
I'm having a problem with spamassassin 3.3.0 after doing sa-compile.
The operation didn't return any error and seems to go as usual, but
running 'spamassassin --lint' hangs, and it didn't before using
sa-compile (it doesn't after using the solution below).
I know I'm not giving enough info to diagnose the problem, but this was
in a production server so I just went for the fast solution: 'rm -rf
/var/lib/spamassassin/compiled'.
Anyone seen this? or anyone using sa-compile doesn't see this?
--
René Berber
Re: sa-compile and 3.3.0
Posted by René Berber <r....@computer.org>.
Jason Bertoch wrote:
> Can you post the output of 'spamassassin -D --lint' to pastebin?
Here's the current working output: http://pastebin.com/m35634489
--
René Berber
Re: sa-compile and 3.3.0
Posted by René Berber <r....@computer.org>.
Justin Mason wrote:
> On Fri, Jan 29, 2010 at 14:59, Mark Martinec <Ma...@ijs.si> wrote:
>> On Friday 29 January 2010 04:20:15 René Berber wrote:
>>> Jason Bertoch wrote:
>>>> What version of re2c are you using? Can you post the output of
>>>> 'spamassassin -D --lint' to pastebin?
>>> Now using re2c 1.3.5 same problem, to be precise it doesn't hang, it
>>> loops (the CPU usage goes up and down, RSS the same, up and down) at the
>>> same point.
>>>
>>> Here's the output http://pastebin.com/m438000e0
>> Indeed, it looks like spinning in
>> zoom: run_body_fast_scan for body_0
>>
>> Could well be due to some problematic rule (SARE?),
>> combined with some unusual mail.
>>
>> The re2c and the 'zoom:' plugins are beyond my expertise.
>> I suggest you open a problem report, and attach
>> your above log there, so that it does not get lost.
>
> +1.
>
> Typically the best approach is to binary-search the list of "body"
> rules until you identify the subset that cause the problem, then use
> "sa-compile --keep-tmps" to capture the re2c output and attach it.
About SARE, I cleaned up my configuration before running the test,
perhaps I missed something because I still end up with one compiled 70_
rule.
The idea about keep-temps sounds good, I could take a look at the source
code produced by re2c for possible problems in the "zoom" rule(s).
--
René Berber
Re: sa-compile and 3.3.0
Posted by Justin Mason <jm...@jmason.org>.
On Fri, Jan 29, 2010 at 14:59, Mark Martinec <Ma...@ijs.si> wrote:
> On Friday 29 January 2010 04:20:15 René Berber wrote:
>> Jason Bertoch wrote:
>> > What version of re2c are you using? Can you post the output of
>> > 'spamassassin -D --lint' to pastebin?
>>
>> Now using re2c 1.3.5 same problem, to be precise it doesn't hang, it
>> loops (the CPU usage goes up and down, RSS the same, up and down) at the
>> same point.
>>
>> Here's the output http://pastebin.com/m438000e0
>
> Indeed, it looks like spinning in
> zoom: run_body_fast_scan for body_0
>
> Could well be due to some problematic rule (SARE?),
> combined with some unusual mail.
>
> The re2c and the 'zoom:' plugins are beyond my expertise.
> I suggest you open a problem report, and attach
> your above log there, so that it does not get lost.
+1.
Typically the best approach is to binary-search the list of "body"
rules until you identify the subset that cause the problem, then use
"sa-compile --keep-tmps" to capture the re2c output and attach it.
--
--j.
Re: sa-compile and 3.3.0
Posted by Mark Martinec <Ma...@ijs.si>.
On Friday 29 January 2010 04:20:15 René Berber wrote:
> Jason Bertoch wrote:
> > What version of re2c are you using? Can you post the output of
> > 'spamassassin -D --lint' to pastebin?
>
> Now using re2c 1.3.5 same problem, to be precise it doesn't hang, it
> loops (the CPU usage goes up and down, RSS the same, up and down) at the
> same point.
>
> Here's the output http://pastebin.com/m438000e0
Indeed, it looks like spinning in
zoom: run_body_fast_scan for body_0
Could well be due to some problematic rule (SARE?),
combined with some unusual mail.
The re2c and the 'zoom:' plugins are beyond my expertise.
I suggest you open a problem report, and attach
your above log there, so that it does not get lost.
Mark
Re: sa-compile and 3.3.0
Posted by René Berber <r....@computer.org>.
René Berber wrote:
> Jason Bertoch wrote:
>
>> What version of re2c are you using? Can you post the output of
>> 'spamassassin -D --lint' to pastebin?
>
> Now using re2c 1.3.5 same problem, to be precise it doesn't hang, it
Oops! 0.13.5
> loops (the CPU usage goes up and down, RSS the same, up and down) at the
> same point.
>
> Here's the output http://pastebin.com/m438000e0
--
René Berber
Re: sa-compile and 3.3.0
Posted by René Berber <r....@computer.org>.
Jason Bertoch wrote:
> On 1/28/2010 10:20 PM, René Berber wrote:
>>
>> Now using re2c 13.5 same problem, to be precise it doesn't hang, it
>> loops (the CPU usage goes up and down, RSS the same, up and down) at the
>> same point.
>>
>> Here's the output http://pastebin.com/m438000e0
>>
>
> Assuming you recompiled your rules after the re2c upgrade, I'll have to
> defer to the devs for interpreting your debug output hang.
Yes, the rules where recompiled just before running that test.
--
René Berber
Re: sa-compile and 3.3.0
Posted by Jason Bertoch <ja...@i6ix.com>.
On 1/28/2010 10:20 PM, René Berber wrote:
>
> Now using re2c 13.5 same problem, to be precise it doesn't hang, it
> loops (the CPU usage goes up and down, RSS the same, up and down) at the
> same point.
>
> Here's the output http://pastebin.com/m438000e0
>
Assuming you recompiled your rules after the re2c upgrade, I'll have to
defer to the devs for interpreting your debug output hang.
Re: sa-compile and 3.3.0
Posted by René Berber <r....@computer.org>.
Jason Bertoch wrote:
> What version of re2c are you using? Can you post the output of
> 'spamassassin -D --lint' to pastebin?
Now using re2c 1.3.5 same problem, to be precise it doesn't hang, it
loops (the CPU usage goes up and down, RSS the same, up and down) at the
same point.
Here's the output http://pastebin.com/m438000e0
--
René Berber
Re: sa-compile and 3.3.0
Posted by René Berber <r....@computer.org>.
Mark Martinec wrote:
> It hasn't been determined exactly which is the minimal working version,
> the 0.12 was chosen just as a version whose predecessors are known to fail.
> Actually SpamAssassin 3.3.0 was tested with 0.13.5, which worked fine.
I'll try that version tonight.
> Not sure which is which. I'd find interesting the output of:
> $ spamassassin -D -t <test.msg >test.log 2>&1
>
> and if it hangs during evaluation of regexp rules, it would
> be worth trying with a newer re2c.
Sounds like a plan. Thanks.
--
René Berber
Re: sa-compile and 3.3.0
Posted by Mark Martinec <Ma...@ijs.si>.
René,
> > What version of re2c are you using? Can you post the output of
> > 'spamassassin -D --lint' to pastebin?
>
> re2c is version 0.12.1. The script sa-compile checks the version so I
> don't think there's a problem there.
It hasn't been determined exactly which is the minimal working version,
the 0.12 was chosen just as a version whose predecessors are known to fail.
Actually SpamAssassin 3.3.0 was tested with 0.13.5, which worked fine.
> About the lint output, you mean the current working output? or the one
> that hangs? If its the later I would have to get it tonight, in about 8
> hours.
>> Can you post the output of 'spamassassin -D --lint' to pastebin?
> Here's the current working output: http://pastebin.com/m35634489
Not sure which is which. I'd find interesting the output of:
$ spamassassin -D -t <test.msg >test.log 2>&1
and if it hangs during evaluation of regexp rules, it would
be worth trying with a newer re2c.
Mark
Re: sa-compile and 3.3.0
Posted by René Berber <r....@computer.org>.
Jason Bertoch wrote:
> On 1/28/2010 3:54 PM, René Berber wrote:
>> Hi,
>>
>> I'm having a problem with spamassassin 3.3.0 after doing sa-compile.
>>
>> The operation didn't return any error and seems to go as usual, but
>> running 'spamassassin --lint' hangs, and it didn't before using
>> sa-compile (it doesn't after using the solution below).
>>
>
> What version of re2c are you using? Can you post the output of
> 'spamassassin -D --lint' to pastebin?
re2c is version 0.12.1. The script sa-compile checks the version so I
don't think there's a problem there.
About the lint output, you mean the current working output? or the one
that hangs? If its the later I would have to get it tonight, in about 8
hours.
--
René Berber
Re: sa-compile and 3.3.0
Posted by Jason Bertoch <ja...@i6ix.com>.
On 1/28/2010 3:54 PM, René Berber wrote:
> Hi,
>
> I'm having a problem with spamassassin 3.3.0 after doing sa-compile.
>
> The operation didn't return any error and seems to go as usual, but
> running 'spamassassin --lint' hangs, and it didn't before using
> sa-compile (it doesn't after using the solution below).
>
What version of re2c are you using? Can you post the output of
'spamassassin -D --lint' to pastebin?
/Jason