Topic: Knuddi's SA broken after automatic upgrade this morning?

[chris burnat]

Spamassassin updated at 04:16 Australian time today.  Three of my servers are now leaking like a sieve.  From the logs:

Jun 20 04:16:37 aleph1 spamd[2171]: server killed by SIGTERM, shutting down
Jun 20 04:16:43 aleph1 spamc[13803]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused

Jun 20 04:16:46 aleph1 spamc[13804]: connection attempt to spamd aborted after 3 retries
Jun 20 04:17:08 aleph1 spamd[13882]: spamd starting

Jun 20 04:17:10 aleph1 spamd[13884]: configuration file "/usr/share/spamassassin/20_body_tests.cf" requires version 3.000003 of SpamAssassin, but this is code version 3.000004. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/Conf/Parser.pm line 332.

Note: there are 12 such entries covering a number of criteria, followed by:

Jun 20 04:17:13 aleph1 spamd[13884]: server started on port 783/tcp (running version 3.0.4)

I tried to re-install, no progress.
Any assistance would be great
chris

[raem]

burnat

What does the following show ?
rpm -q spamassassin
rpm -q spamassassin-tools
rpm -q perl-Mail-SpamAssassin

[chris burnat]

[root@mail chris]# rpm -q spamassassin
spamassassin-3.0.4-1

[root@mail chris]# rpm -q spamassassin-tools
spamassassin-tools-3.0.4-1

[root@mail chris]# rpm -q perl-Mail-SpamAssassin
perl-Mail-SpamAssassin-3.0.3-1

aha.... What do you suggest?
Thanks
chris

[raem]

burnat

> [root@mail chris]# rpm -q perl-Mail-SpamAssassin
> perl-Mail-SpamAssassin-3.0.3-1
> aha.... What do you suggest?

I thought that would be obvious !

Go to
http://sme.swerts-knudsen.com/downloads/SpamFilter/
download
perl-Mail-SpamAssassin-3.0.4-1.i386.rpm
and do
rpm -Uvh perl-Mail-SpamAssassin-3.0.4-1.i386.rpm

Something went wrong in the auto update and that rpm didn't install. It probably timed out during download (when everyone else was trying to automatically download it too) as it is a larger file (554Kb).

[chris burnat]

Thank you Ray.  What is obvious to an experienced person such as you is not so obvious to a relative beginner such as me and many others.... Hence you imparting of your knowledge is very appreciated, as always. chris.

[Brenno]

My home server (with auto-download and update,) also suffered from the same problem of having the wrong perl-Mail-SpamAsassin on it. Ray's fix worked.

My work server (with auto-download and warn,) downloaded the update to my /tmp/USA directory.  When I tried to install via rpm -Uvh *.rpm, I got the following error:

Code: [Select]

Preparing...                ########################################### [100%]
   1:perl-Mail-SpamAssassin error: unpacking of archive failed on file /usr/shar                      e/spamassassin/50_scores.cf;42b6d836: cpio: read failed - Bad file descriptor

Running rpm -q perl-Mail-Spamassassin replies with:

Code: [Select]

perl-Mail-SpamAssassin-3.0.3-1

So perhaps it's not a timeout issue?

[electroman00]

Did
rpm -Uvh perl-Mail-SpamAssassin-3.0.4-1.i386.rpm

and received this

error: failed dependencies:
        perl-Mail-SpamAssassin = 3.0.3-1 is needed by spamassassin-3.0.3-1
        perl-Mail-SpamAssassin = 3.0.3-1 is needed by spamassassin-tools-3.0.3-1

That may be why its not updating.

Looks like up rpm is borked.

[chris burnat]

Electroman, you need to add a switch to your command: --nodeps The alternative is to install them using the upfate system panel in server manager. Click on "advanced options" and select require nodeps = YES.  You can install one by one, it should be OK.

Brenno, I experienced the same type of errors for all three rpms on one of my server. Had to do "nodeps" to fix it.

This all business raises the issue of automatic update... Technology will fail at some stage.  Two of the boxes affected are at remote locations.  There were no warning, I only noticed it because all of a sudden, my own server started to collect spams in my mail own box.  I am now turning automatic update on manual on all my servers to be on the safe side...  chris.

[raem]

electroman00

> rpm -Uvh perl-Mail-SpamAssassin-3.0.4-1.i386.rpm
> error: failed dependencies:
> perl-Mail-SpamAssassin = 3.0.3-1 is needed by spamassassin-3.0.3-1
> perl-Mail-SpamAssassin = 3.0.3-1 is needed by spamassassin-tools-3.0.3-1

That sounds like none of the new versions of the three rpms were updated as the older version stll appear to be installed. Check all 3 with rpm -q .....

I would manually download all three to an empty folder, cd /foldername and then do rpm -Uvh *.rpm

[raem]

burnat

>...I am now turning automatic update on manual on all my servers to be on the safe side

I totally agree with that approach, I have the setting at "Warn when new release are available" and then when I receive the email message I can manually download the files, run the update and make sure everything went correctly (using ssh).

[chris burnat]

Yes, and just think of the fun waiting for us with YUM set in automatic mode on SME7...

Found this administrative email this morning on 3 servers:
/etc/cron.daily/run_usa:
/usr/sbin/USA: [: too many arguments

On the 20/6/05, I had received this administrative email:
"The following updates have been downloaded and installed:
  - spamassassin-3.0.4-1.i386.rpm
  - spamassassin-tools-3.0.4-1.i386.rpm
  - perl-Mail-SpamAssassin-3.0.4-1.i386.rpm
regards, The automatic SpamAssassin updater"

Knowing there was an issue, I checked the logs for these boxes, all appeared OK. Of course, with hindsight (and some help from Ray) I should have drilled a bit more...  

[root@mail chris]# rpm -q spamassassin
spamassassin-3.0.3-1
[root@mail chris]# rpm -q perl-Mail-SpamAssassin
perl-Mail-SpamAssassin-3.0.3-1
[root@mail chris]# rpm -q spamassassin-tools
spamassassin-tools-3.0.3-1


It has not been updated, obviously.
Re-install the 3 rpms with --nodeps ----> OK
Same story for the other two servers.
Let see how it pans out.
chris

[Brenno]

Apparently, this problem isn't limited to just SpamAssassin!  Notice this new thread this morning:

http://forums.contribs.org/index.php?topic=27865.0

Fortunately, I also have that set to download and warn, so I can peek at the files first to see if they're okay.

[Jasonuocs]

Same here, Three sites I have SME Server installed with swerts AV & Anti Spam I had a phone call from all 3 of them to say they were not getting their emails! I noticed it was dumping them into the problem directory & manually updated Swerts AV all seems better... Thank christ its a good system and easy to use!!
Thanks to all  the hard work of the folks that give us a good reliable system that doesnt cost the earth.

[stiperstones]

Log into server manager using terminal or putty as root

Code: [Select]

mkdir spamit

Code: [Select]

cd spamit
issue this command

Code: [Select]

wget http://sme.swerts-knudsen.com/downloads/SpamFilter/spamfilter_install.sh
wait for download to complete
issue this command

Code: [Select]

sh spamfilter_install.sh
wait until all installed
exit terminal
Go to http://your-server-name/server-manager
go to spamassin page
go to bottom of page and click on save
wait until complete "says return to spamassin page"

[electroman00]

Well I could not install the rpm after using wget to DL.
However if I winscp the RPM's they extract and install.

I'm seeing this trend also with the Snort updates.

I believe it's an issue with wget and possibly a newer version gzipper that may be in use.

I noticed (myself included) that a lot of people were
having problems with Snort rulesets and auto update
rulesets software.
Yes I know Snort made some changes to rulesets, however
after adjusting the auto update rulesets software the
extraction was failing and that's whats happening with the rpm update.

Not sure at this point exactly what the problem is.

[jokern]

On my newly installed 6.5RC1 the upgrade went without a hitch.
Could there be other mods/contribs that are interferring?