You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Steven W. Orr" <st...@syslang.net> on 2007/06/13 23:02:43 UTC
Error on startup after upgrade to 3.2.1:CompiledRegexps
[root@saturn ~]# rpm -Uvh
/usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm
/usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm
Preparing... ########################################### [100%]
1:perl-Mail-SpamAssassin ########################################### [ 50%]
2:spamassassin ########################################### [100%]
Stopping spamd: [ OK ]
Starting spamd: [13775] error: Can't locate
Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC contains:
/var/lib/spamassassin/compiled/3.002001
/var/lib/spamassassin/compiled/3.002001/auto lib
/usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.6
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4
/usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi
/usr/lib/perl5/5.8.6) at (eval 570) line 1.
[ OK ]
Am I concerned? Where is CompiledRegexps supposed to be and why is it not
there?
TIA
--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
Re: Error on startup after upgrade to 3.2.1:CompiledRegexps
Posted by Theo Van Dinter <fe...@apache.org>.
On Thu, Jun 14, 2007 at 08:45:17AM -0400, Steven W. Orr wrote:
> I downloaded the tarfile and built an rpm. When I installed the rpm, the
> rpm was smart enough to restart SA. Should this postinst code in the rpm
> not also have rerun sa-compile before the restart? Seems logical to me.
The script has no way to know how you're doing your config, so I wouldn't
expect it to compile rules automatically in the same way that I wouldn't
expect it to run sa-update or any other "do something with my configs"
program automatically.
--
Randomly Selected Tagline:
"They sell cans of fresh Maine air ... probably vacuum-sealed." - Theo
RE: Error on startup after upgrade to 3.2.1:CompiledRegexps
Posted by "Steven W. Orr" <st...@syslang.net>.
On Wednesday, Jun 13th 2007 at 17:14 -0400, quoth Rosenbaum, Larry M.:
=>> From: Steven W. Orr [mailto:steveo@syslang.net]
=>>
=>> [root@saturn ~]# rpm -Uvh
=>> /usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm
=>> /usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm
=>> Preparing...
=>###########################################
=>> [100%]
=>> 1:perl-Mail-SpamAssassin
=>> ########################################### [ 50%]
=>> 2:spamassassin
=>> ########################################### [100%]
=>> Stopping spamd: [ OK ]
=>> Starting spamd: [13775] error: Can't locate
=>> Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC contains:
=>...
=>>
=>> Am I concerned? Where is CompiledRegexps supposed to be and why is it
=>> not
=>> there?
=>
=>I think it means you have Rule2XSBody uncommented in v320.pre but you
=>don't have a compiled ruleset. Perhaps you ran sa-compile under v3.2.0
=>but you haven't run it under v3.2.1.
Thanks to Larry for the answer. This leads to a question about how SA is
packaged:
I downloaded the tarfile and built an rpm. When I installed the rpm, the
rpm was smart enough to restart SA. Should this postinst code in the rpm
not also have rerun sa-compile before the restart? Seems logical to me.
--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
RE: Error on startup after upgrade to 3.2.1:CompiledRegexps
Posted by "Rosenbaum, Larry M." <ro...@ornl.gov>.
> From: Steven W. Orr [mailto:steveo@syslang.net]
>
> [root@saturn ~]# rpm -Uvh
> /usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm
> /usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm
> Preparing...
###########################################
> [100%]
> 1:perl-Mail-SpamAssassin
> ########################################### [ 50%]
> 2:spamassassin
> ########################################### [100%]
> Stopping spamd: [ OK ]
> Starting spamd: [13775] error: Can't locate
> Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC contains:
...
>
> Am I concerned? Where is CompiledRegexps supposed to be and why is it
> not
> there?
I think it means you have Rule2XSBody uncommented in v320.pre but you
don't have a compiled ruleset. Perhaps you ran sa-compile under v3.2.0
but you haven't run it under v3.2.1.