script error?

[Stefan Suurmeijer <st...@raptorweb.nl>]

Hi list,

this is probably some easy configuration issue, but it's now almost 1am 
and I just spent the last 4 hours upgrading my system so by now I 
wouldn't see a solution if it hit me in the face.

I have everything working, except for spamassassin. I had it working 
earlier, but I decided to get the newest version of SA from CPAN and now 
when I try to start spamd I get the following error:

ERROR!  spamassassin script is v3.000000, but using modules v3.000001!

which is great in not telling me anything useful about what is wrong. 
Can anybody point me in the right direction? Any help would be GREATLY 
appreciated

TIA
Stefan

Re: script error?

[Stefan Suurmeijer <st...@raptorweb.nl>]

tried it but didn't work. There's probably some statement in a startup 
script that is no longer available in v3.000001, but I have no idea 
what. Anyone?

Noel K Hall II wrote:

>First, shutdown the running spamd process (if it is), and any process that
>calls the use of spamassassin.
>
>Then from the CPAN shell  use 'force install Mail::SpamAssassin'
>
>Then restart everything and see what happens.
>
>-Noel
>
>-----Original Message-----
>From: Stefan Suurmeijer [mailto:stefan@raptorweb.nl] 
>Sent: Thursday, November 18, 2004 6:52 PM
>To: users@spamassassin.apache.org
>Subject: script error?
>
>Hi list,
>
>this is probably some easy configuration issue, but it's now almost 1am and
>I just spent the last 4 hours upgrading my system so by now I wouldn't see a
>solution if it hit me in the face.
>
>I have everything working, except for spamassassin. I had it working
>earlier, but I decided to get the newest version of SA from CPAN and now
>when I try to start spamd I get the following error:
>
>ERROR!  spamassassin script is v3.000000, but using modules v3.000001!
>
>which is great in not telling me anything useful about what is wrong. 
>Can anybody point me in the right direction? Any help would be GREATLY
>appreciated
>
>TIA
>Stefan
>
>
>  
>

RE: script error?

[Noel K Hall II <no...@physicianrecruiting.com>]

First, shutdown the running spamd process (if it is), and any process that
calls the use of spamassassin.

Then from the CPAN shell  use 'force install Mail::SpamAssassin'

Then restart everything and see what happens.

-Noel

-----Original Message-----
From: Stefan Suurmeijer [mailto:stefan@raptorweb.nl] 
Sent: Thursday, November 18, 2004 6:52 PM
To: users@spamassassin.apache.org
Subject: script error?

Hi list,

this is probably some easy configuration issue, but it's now almost 1am and
I just spent the last 4 hours upgrading my system so by now I wouldn't see a
solution if it hit me in the face.

I have everything working, except for spamassassin. I had it working
earlier, but I decided to get the newest version of SA from CPAN and now
when I try to start spamd I get the following error:

ERROR!  spamassassin script is v3.000000, but using modules v3.000001!

which is great in not telling me anything useful about what is wrong. 
Can anybody point me in the right direction? Any help would be GREATLY
appreciated

TIA
Stefan

RE: script error?

[Martin <ma...@ntlworld.com>]

|-----Original Message-----
|From: Stefan Suurmeijer [mailto:stefan@raptorweb.nl] 
|Sent: 18 November 2004 23:52
|To: users@spamassassin.apache.org
|Subject: script error?
|
|Hi list,
|
|this is probably some easy configuration issue, but it's now 
|almost 1am and I just spent the last 4 hours upgrading my 
|system so by now I wouldn't see a solution if it hit me in the face.
|
|I have everything working, except for spamassassin. I had it 
|working earlier, but I decided to get the newest version of SA 
|from CPAN and now when I try to start spamd I get the following error:
|
|ERROR!  spamassassin script is v3.000000, but using modules v3.000001!
|
|which is great in not telling me anything useful about what is wrong. 
|Can anybody point me in the right direction? Any help would be 
|GREATLY appreciated
|

I had exactly the same when I upgraded, turned out I had two versions of
spamd on, one in /usr/bin/spamd and the other /usr/sbin/spamd, one was the
old one and the other was the new one, cant remember which way round now,
shouldn't be hard to figure though. The startup script was finding the old
one, just delete it and/or copy the new one over.

Martin