Topic: spamassassin and rkhunter

[mophilly]

I used Greg Swallow's wonderful update script; very nice indeed.

This morning SpamAssassin performed an auto update.

Code: [Select]

The following updates were downloaded and installed:
  - spamassassin-3.0.2-1.i386.rpm
  - spamassassin-tools-3.0.2-1.i386.rpm
  - perl-Mail-SpamAssassin-3.0.2-1.i386.rpm

regards,
The e-smith-USA script



And then rkhunter complained about SpamAssassin's auto update feature:

Code: [Select]

/etc/cron.daily/rkhunter:

ClamAV 0.80/634/Sun Dec 19 13:21:52 2004
/etc/cron.daily/run_usa:

Shutting down spamd: [   OK   ]
Starting spamd: ERROR!  spamassassin script is v3.000002, but using modules v3.000001!
[ FAILED ]

Shutting down spamd: [ FAILED ]
Starting spamd: [   OK   ]

Am I right to see this as a failure to update?

What can be done to allow this to work without raising an error?

TIA

[NickR]

Am I right to see this as a failure to update?

No - SA has updated OK, it's just that it seems to run the newer version of the script and reports this error.  The final "Starting spamd: [   OK   ]" tells you it started OK.

BTW, it's not rkhunter that's reporting all this, it's actually SA - it's confusing because it's all lumped in together as the /etc/cron.daily report.

[mophilly]

Thanks, NickR, for the reassurance.

Does the script need to be updated?

[NickR]

Does the script need to be updated?

No, I think the problem seems to be that the new script gets downloaded & run against the old version of SA - I saw the same problem when it went from v3.000000 to v3.000001 some time ago.

It's just cosmetic.

[jok11n]

I got the exact same error and checked here to see if anyone else did, I thought all was ok but spamassasin is definately not working now. Any tips on what to do to get it working? Or should this question go to Jesper?

[NickR]

Any tips on what to do to get it working?

Does doing this help at all?:

# service spamassassin restart

[jok11n]

Have tried that now, it did appear to stop and restart the service which might suggest it was running, it wasn't working though. I'll let you know if it works. Perhaps there is some error in the script.

[NickR]

As long as you are seeing something like this:

# service spamassassin status
spamd (pid 5529 5528 5527 5526 5525 5521) is running...

then SA is running.

[rexgaylord]

Maybe it's PROCMAIL that isn't running?  I've had to reenable all the users to use procmail to process mail after a SA update, but not on this one so far.