Problem upgrading from 3.1.8 to 3.1.20, check.pm

[li...@ruben.cn]

Hi,

   I've been upgrading several stable servers running 3.1.8 for months  
without any issues to 3.1.20, and got a problem in one of them. When  
trying to restart spamd, I get this:

@40000000463ee4f622539324 [5532] error: check: no loaded plugin  
implements 'check_main': cannot scan! at  
/usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line 164.
@40000000463ee4f622543f04 check: no loaded plugin implements  
'check_main': cannot scan! at  
/usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line 164.

The file v320.pre has its corresponding:

loadplugin Mail::SpamAssassin::Plugin::Check

And the Check.pm file is at  
/usr/local/share/perl/5.8.4/Mail/SpamAssassin/Plugin/ with the rest of  
plugins, being worldwide read accesible.

Is this some kind of bug or am I doing something wrong (or maybe I'm  
missing something).

TIA,

Ruben

Re: Problem upgrading from 3.1.8 to 3.1.20, check.pm

[Michael Parker <pa...@pobox.com>]

lists@ruben.cn wrote:
> Hi,
> 
>   I've been upgrading several stable servers running 3.1.8 for months
> without any issues to 3.1.20, and got a problem in one of them. When
> trying to restart spamd, I get this:
> 
> @40000000463ee4f622539324 [5532] error: check: no loaded plugin
> implements 'check_main': cannot scan! at
> /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line 164.
> @40000000463ee4f622543f04 check: no loaded plugin implements
> 'check_main': cannot scan! at
> /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line 164.
> 
> The file v320.pre has its corresponding:
> 
> loadplugin Mail::SpamAssassin::Plugin::Check
> 
> And the Check.pm file is at
> /usr/local/share/perl/5.8.4/Mail/SpamAssassin/Plugin/ with the rest of
> plugins, being worldwide read accesible.
> 
> Is this some kind of bug or am I doing something wrong (or maybe I'm
> missing something).
> 

I doubt there is some kind of bug, otherwise a lot more people would be
having an issue.  What does spamassassin -D --lint say?  Are you sure
its finding the v320.pre file?  Feel free to reply with the output.

Michael

Re: Problem upgrading from 3.1.8 to 3.1.20, check.pm

[sleepjet <ty...@boss.cs.ohiou.edu>]

On Wed, May 09, 2007 at 12:14:24AM -0500, Gabriel Millerd wrote:
>   Beyond the s/3.1.20/v3.2.0/ issue that some people cannot get past.
>> I have the same issue. I had to juggle my cf/pre files entries for
>> quite some time to get past the check_scan problem you describe for
>> spamd to run peachy. I, like you I suspect, loaded up one single file
> >with all my config entries. The v3.2 suite seems to want these in a
>> number of files. Where v3.1.x was forgiving I guess.

>The config code didn't really change between 3.1 and 3.2.  3.2 doesn't
>care if you have one pre file or twenty.  However, what does matter is
>that you have all the loadplugin lines that you need to have.  In 3.2,
>the check() function was pluginized, and so you need to load a plugin
>that implements the function or else you don't have a check() function.
>Without that function, SA can't scan anything, and so it helpfully alerts
>you to the fact that you don't have this functionality.

  There is 1 configuration change, and that is the directory the updates are
store in.
The installation process failed to update the sa-update in my local bin
directory,
so it was using the old 3.001... directory, instead of the 3.002... one.
I manually copied the sa-update program over, and the problem is gone.
.
-- 
View this message in context: http://www.nabble.com/Problem-upgrading-from-3.1.8-to-3.1.20%2C-check.pm-tf3702543.html#a10622653
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.