Atomicorp

We have a 7.5.3 server with all the latest patches/updates.

When we run yum update the following apps are ready for update.
Since we are running psa-spamassassin without a hitch, is this spamassassin update going to break our psa-spamassassin?

We have spamassassin set up as an exclude, but it still attempts to update.

Just wanted to check before completing this.

Thanks a bunch.

sort of, it will complain, but spamassassin will still work. Alledgedly PSA 7.5.4 no longer freaks out on the newer generation of spamassassin

scott wrote:

sort of, it will complain

, but spamassassin will still work. Alledgedly PSA 7.5.4 no longer freaks out on the newer generation of spamassassin

That's reassuring..... I think. Don't suppose you'd elaborate on:

sort of, it will complain, but spamassassin will still work

We read an ART post about 1and1, took on a server with them and are now finding ourselves faced with some rather interestingly new challenges to deal with, so . . . . we'd love to know.

We are migrating from a 7.0.x server and 7.5.3 has some new and innovative upgrades, to say the least and we don't wish to break it before getting started.

Granted the 1n1 CP does have one of the best server restoration processes I've seen since forever, I'd rather not be re-imaging our server everytime a yum upgrade is made.

The issue in 7.5.3 is that the control panel wont work with Spamassassin, semi-sorta-kinda. It does work, sometimes, and sometimes it doesnt. It will also complain on startup that something is missing, and sometimes it doesnt. Spamassassin itself works fine, spam detection/deletion/etc all works, its just that PSA has issues. 7.5.4 allegedly does not, however I havent tested that myself so I can say if its true or not.

See why I like to keep these things brief?

Sorta-kinda works for free hosting. Doesn't work for me.

As we have just gotten our new server, we're not ready to do the 7.5.4-BETA on a sorta-kinda option.

Maybe later, but we're out of the beta business.

Thanks

Yes you feel entitled to my exclusive time to solve your selfish problems. I know, youve stated this before.

Great. That clears everything up.

Thanks

phatPhrog wrote:We have a 7.5.3 server with all the latest patches/updates.

When we run yum update the following apps are ready for update.

Code: Select all

[update: php-pear 4.3.11-8.rhfc2.art.i386]
[update: php-xslt 4.3.11-8.rhfc2.art.i386]
[update: spamassassin 1:3.0.3-1.rhfc2.art.i386]
I will install/upgrade these to satisfy the dependencies:
[deps: razor-agents 2.67-3.rhfc2.art.i386]
[deps: dcc 1.3.5-1.rhfc2.art.i386]
[deps: perl-Digest-Nilsimsa 0.06-1.rhfc2.art.i386]

Since we are running psa-spamassassin without a hitch, is this spamassassin update going to break our psa-spamassassin?

We have spamassassin set up as an exclude, but it still attempts to update.

Just wanted to check before completing this.

Thanks a bunch.

We have the same set up, 7.5.3 with psa-spamassassin and all the latest updates. We don't see this problem, must be your set up. (double check yum.conf)

Thanks jamster. Will do.

Scott, jamster and everyone else.

We just ran the updater from 7.5.3 to 7.5.4 without a hitch.

After running yum update our only issue (not much of one really) was to restart mysql and psa-spamassassin from SSH after the update completed.

Not sure of the reason. Looked like a connection problem on our end, but couldn't find any logs stating a problem from the update either through updater or ART yum update.

Bottom line. Successful update without any service interruption and all ART rpms were recognized and configured without conflict. (not that there would have been)

CIAO

(you're still my hero whether it matters or not)

Thats really good news, I haven't even had a chance to try it out myself yet. Were you using mysql 4.0 or 4.1? I dont think it will be an issue, but one thing Ive noticed in the past is that mysql doesn't always shut down/start up fast enough as the psa rpm is being upgraded. When this happens the psa install will fail halfway through, and you end up with both the old and new psa rpms listed in the database.

First, to clear up the mysql restart issue.

After I ran updater a pre-existing cron job ran a psadump. It was psadump that had the problem restarting mysql.

I am using 4.0.25-1.rhfc2.art. Since psadump is a newer version in 7.5.4, that was the source of that problem. Ran psadump manually since and the problem didn't occur again.

So, all in all I had no problems updating 7.5.3 to 7.5.4 with the updater with FC2.

The only problem since running yum update was having to manually restart psa-spamassassin via SSH.

Will let you know if psa-spamassassin gives any problems.