For the last few days (from 31 Jan 2015), sa-update has been failing on my
server. I've checked and can't see that any package updates happened around
then, so I'm puzzled by why this is happening (it's been working fine for
over a year beforehand).

I'm running sa-update version svn1475932 (with Perl version 5.18.2) on a
64-bit Ubuntu 14.04 box.

Running "sa-update -D" shows the following output:

~~~
Feb  4 10:00:43.663 [13904] dbg: generic: lint check of site pre files
succeeded, continuing with channel updates
Feb  4 10:00:43.663 [13904] dbg: channel: protocol family available:
inet,inet6
Feb  4 10:00:43.663 [13904] dbg: channel: reading MIRRORED.BY file
/var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY
Feb  4 10:00:43.663 [13904] dbg: channel: parsing MIRRORED.BY file for
channel updates.spamassassin.org
Feb  4 10:00:43.663 [13904] dbg: channel: found mirror
http://sa-update.dnswl.org/ weight=1
Feb  4 10:00:43.664 [13904] dbg: channel: found mirror
http://www.sa-update.pccc.com/ weight=5
Feb  4 10:00:43.664 [13904] dbg: channel: found mirror
http://sa-update.secnap.net/ weight=5
Feb  4 10:00:43.664 [13904] dbg: channel: found mirror
http://sa-update.space-pro.be/ weight=1
Feb  4 10:00:43.664 [13904] dbg: channel: selected mirror
http://sa-update.space-pro.be
Feb  4 10:00:43.664 [13904] dbg: http: url:
http://sa-update.space-pro.be/1655961.tar.gz
Feb  4 10:00:43.664 [13904] dbg: http: downloading to:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/1655961.tar.gz,
update
Feb  4 10:00:43.664 [13904] dbg: util: executable for curl was found at
/usr/bin/curl
Feb  4 10:00:43.664 [13904] dbg: http: /usr/bin/curl -s -L -O --remote-time
-g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o
1655961.tar.gz -z 1655961.tar.gz --
http://sa-update.space-pro.be/1655961.tar.gz
Feb  4 10:00:43.984 [13904] dbg: http: process [13905], exit status: 0
Feb  4 10:00:43.985 [13904] dbg: http: url:
http://sa-update.space-pro.be/1655961.tar.gz.sha1
Feb  4 10:00:43.985 [13904] dbg: http: downloading to:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/1655961.tar.gz.sha1,
update
Feb  4 10:00:43.985 [13904] dbg: util: executable for curl was found at
/usr/bin/curl
Feb  4 10:00:43.986 [13904] dbg: http: /usr/bin/curl -s -L -O --remote-time
-g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o
1655961.tar.gz.sha1 -z 1655961.tar.gz.sha1 --
http://sa-update.space-pro.be/1655961.tar.gz.sha1
Feb  4 10:00:44.053 [13904] dbg: http: process [13907], exit status: 0
Feb  4 10:00:44.053 [13904] dbg: http: url:
http://sa-update.space-pro.be/1655961.tar.gz.asc
Feb  4 10:00:44.054 [13904] dbg: http: downloading to:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/1655961.tar.gz.asc,
update
Feb  4 10:00:44.054 [13904] dbg: util: executable for curl was found at
/usr/bin/curl
Feb  4 10:00:44.054 [13904] dbg: http: /usr/bin/curl -s -L -O --remote-time
-g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o
1655961.tar.gz.asc -z 1655961.tar.gz.asc --
http://sa-update.space-pro.be/1655961.tar.gz.asc
Feb  4 10:00:44.121 [13904] dbg: http: process [13909], exit status: 0
Feb  4 10:00:44.122 [13904] dbg: sha1: verification wanted:
1d9bedea146ab21a29ccf8c2db69f21f9dada829
Feb  4 10:00:44.122 [13904] dbg: sha1: verification result:
239d865225fcccb48f2b128429cd7b15c6a62206
channel: SHA1 verification failed, channel failed
Feb  4 10:00:44.122 [13904] dbg: generic: cleaning up temporary
directory/files
Feb  4 10:00:44.122 [13904] dbg: generic: cleaning directory
/tmp/.spamassassin13904HYHUBttmp
Feb  4 10:00:44.122 [13904] dbg: diag: updates complete, exiting with code 4
~~~

So the update is not getting the expected sha1 verification. There are 4
mirrors in MIRRORED.BY, and I've tested it with each one selected
individually and the others removed, but I get the same result for each
mirror. I also reinstalled Digest::SHA1 on CPAN, but still no joy.

Has anyone else noticed this problem, or is it just me? Any ideas how I can
fix this? Is it a problem with my installation or with the mirrors?

Thanks!

Tim

Reply via email to