SpamAssassin Upgrade (action needed)

We’ve upgraded our Spam Assassin packages to the latest version. We’ve also changed the package structure of the SA packages to more closely follow the “standard” naming scheme for SA on most distros. The only downside is that a “yum update” won’t grab this new package becuase of the name change. You’ll have to execute a “yum upgrade” to grab the new SA binary and it will clobber the old one (replacing it and upgrading it).

Sorry for the inconvenience but it’s needs for easier longer term maintenance of all the packages, distros etc.

Chris

A “yum upgrade” gives the follwing on RH9 box.

[update: spamassassin 3.1.0-100.rht90.iworx.i386]
[update: mysql 3.23.58-1.90.6.legacy.i386]

Doing a “YUM upgrade spamassassin” gives nothing.

I dont think I want to update mysql to an old version

While it should be ok I’m not ready to take responsibility if it’s not ;). I’d exclude mysql either via the command line or the yum.conf excludes line Justin.

Chris

yum --exclude=mysql upgrade did the trick!

Can’t seem to get the update to go, do I cantact you or Sago?

What does it say when you type in “yum upgrade”?

[#####@#####]# yum upgrade
Gathering header information file(s) from server(s)
Server: Red Hat Linux 9 - Base
Server: Red Hat Linux 9 - Fedora Legacy - Updates
Server: InterWorx-CP - Generic
Server: InterWorx-CP - Red Linux 9
Server: Red Hat Linux 9 - Updates
Finding updated packages
Downloading needed headers
Finding obsoleted packages
Resolving dependencies
…Unable to satisfy dependencies
Package rrdtool-devel needs rrdtool = 1.0.48, this is not available.

Sorry for the delay stuck out of town.

I did the upgrade…

Good morning.

I followed the instructions given and (after an accounts backup) performed the yum upgrade. All seemed to go well, but I noticed that following a reboot the Spam Filtering was not running. I clicked the button to start it and it did start, but I’m concerned that it won’t autostart if the server is rebooted in the future.

Any thoughts?

Phil Malmstrom
philm@diamondcomputer.com

Hi Phil,

As root, run:

chkconfig --list spamassassin

You should see output like:

spamassassin 0:off 1:off 2:off 3:on 4:on 5:on 6:off

If you see “3:on”, then that means Spamassassin is set to start at bootup. If you don’t see that, run the following command:

chkconfig --level 345 spamassassin on

That will tell the server to start Spamassassin when it enters runlevel 3 (the default runlevel), 4 or 5.

Hope that helps,
Socheat

Adding spamassassin to chkconfig…

Hi Socheat and thanks for the reply.

I’m familliar with the runlevel settings and I have set it to start on 3,4 and 5. My concern is that it was set to autostart prior to the yum upgrade and wasn’t after the fact. I just wanted to make sure someone knew as it might be missed accidentally by other users.

I also noted that when doing the “chkconfig --list spamassassin” initially after the upgrade that chkconfig indicated that while spamassassin was able to be set this way, it wasn’t referenced in any runlevels currently. A “chkconfig --add spamassassin” quickly remedied these issues and I could then set the runlevels to autostart.

Either way, thanks for your prompt reply. I continue to be impressed with Interworx and with you all. Take care.

Phil Malmstrom
philm@diamondcomputer.com

[SIZE=2]Am I SOL since I am on Red Hat 9?[/SIZE]

godboko,

do a:

yum --exclude rrdtool upgrade

And see if that fixes.

Chris

[root@s1 root]# yum --exclude rrdtool upgrade
Gathering header information file(s) from server(s)
Server: Red Hat Linux 9 - Base
Server: Red Hat Linux 9 - Fedora Legacy - Updates
Server: InterWorx-CP - Generic
Server: InterWorx-CP - Red Linux 9
Server: Red Hat Linux 9 - Updates
Finding updated packages
Downloading needed headers
rrdtool-devel-0-1.2.11-1. 100% |=========================| 1.6 kB 00:00
Finding obsoleted packages
Resolving dependencies
…Unable to satisfy dependencies
Package rrdtool-devel needs rrdtool = 1.2.11, this is not available.
[root@s1 root]#

Try it now godboko, I’ve added the -devel packages to our respository. A “yum --exclude rrdtool-devel” would have probably worked but regardless a yum upgrade should work now.

Chris

That seemed to have worked :slight_smile:

Thank you.