Spamassassin not working after update

12 posts / 0 new
Last post
#1 Wed, 03/24/2010 - 22:11
flameproof

Spamassassin not working after update

I logged in to webmin today and updated (beside some others) Spamassassin.

After the update (and reboot) Spamassassin seems not to work. Here is what a restart did:

[root@vps]# /etc/init.d/spamassassin restart Stopping spamd: [FAILED] Starting spamd: child process [5857] exited or timed out without signaling production of a PID file: exit 255 at /usr/bin/spamd line 2588. [FAILED] [root@vps]#

(Since SPAM really annoys me and I am a bit impatient too I googled while checking this issue and found:)

I should after the upgrade run:

sa-update -D

I did that, and then:

/etc/init.d/spamassassin restart

...and it worked fine.

I post that solved issue anyway in case somebody else got this error.

Wed, 03/24/2010 - 23:21
andreychek

Huh, I've never actually run into an issue where sa-update needed to be manually run after the SpamAssassin update.

Do you know if you by chance pulled SpamAssassin in from another repository other than the standard one provided by your distro?

I'm glad you got it working though!

-Eric

Wed, 03/24/2010 - 23:35
flameproof

I don't know, I can check that if you like to know. But then, how to check?

Thu, 03/25/2010 - 11:32
andreychek

What Linux distribution are you using?

-Eric

Sun, 03/28/2010 - 21:17
flameproof

I use CentOS (not the very latest)

Sun, 03/28/2010 - 21:23
andreychek

Cool -- what do you see if you run this command:

rpm -qa | grep spamassassin

Thanks!

-Eric

Sun, 03/28/2010 - 23:17
flameproof

Here is what I get:

[root@vps]# rpm -qa | grep spamassassin

spamassassin-3.3.1-3.el5.rf

Sun, 03/28/2010 - 23:25
andreychek

Yeah, that SpamAssassin package you're using came from an RPMForce/DAG repository (that's what the .rf at the end means).

I'd suggest being cautious about using packages from alternate repositories, as unusual things can sometimes happen ;-)

-Eric

Sun, 03/28/2010 - 23:31
flameproof

Here is what I did now:

[root@vps]# cd /etc/yum.repos.d

[root@vps yum.repos.d]# dir

CentOS-Base.repo
CentOS-Media.repo
mirrors-rpmforge
rpmforge.repo
virtualmin.repo

Is there anything harmful or dangerous? I rather use only one source, if that's possible. I just want a basic stable system that runs fine.

Sun, 03/28/2010 - 23:49
andreychek

The rpmforge related repositories you have there aren't default repos for a CentOS system with Virtualmin.

Some packages in it may work great, but others are known to conflict with Virtualmin packages.

So, my suggestion is that if you want to use it, to only pull down certain packages from it, the ones you require.

-Eric

Mon, 03/29/2010 - 01:46
flameproof

Ok, I deleted mirrors-rpmforge & rpmforge.repo

BTW, the new Spamassassin seem to work much better. Spam rate is way down.

Mon, 05/17/2010 - 10:29
vijaykumar

"sa-update -D" fixed it and made sense.

Thanks a bunch