You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2016/06/25 00:16:50 UTC

[Bug 7331] New: channel: SHA1 verification failed, channel failed

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331

            Bug ID: 7331
           Summary: channel: SHA1 verification failed, channel failed
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: sa-update
          Assignee: dev@spamassassin.apache.org
          Reporter: jidanni@jidanni.org

Why is this happening for my United States machine, but not my Asian machines?

Jun 25 08:02:55.439 [29035] dbg: channel: parsing MIRRORED.BY file for channel
updates.spamassassin.org
Jun 25 08:02:55.440 [29035] dbg: channel: found mirror
http://sa-update.dnswl.org/ weight=1
Jun 25 08:02:55.440 [29035] dbg: channel: found mirror
http://www.sa-update.pccc.com/ weight=5
Jun 25 08:02:55.440 [29035] dbg: channel: found mirror
http://sa-update.secnap.net/ weight=5
Jun 25 08:02:55.440 [29035] dbg: channel: found mirror
http://sa-update.space-pro.be/ weight=1
Jun 25 08:02:55.706 [29035] dbg: channel: selected mirror
http://sa-update.secnap.net
Jun 25 08:02:55.707 [29035] dbg: http: url:
http://sa-update.secnap.net/1749638.tar.gz
Jun 25 08:02:55.707 [29035] dbg: http: downloading to:
/home/jidanni1/.spamassassin-tree/var/spamassassin/4.000000/updates_spamassassin_org/1749638.tar.gz,
update
Jun 25 08:02:55.707 [29035] dbg: util: executable for curl was found at
/usr/bin/curl
Jun 25 08:02:55.707 [29035] dbg: http: /usr/bin/curl -s -L -O --remote-time -g
--max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1749638.tar.gz -z
1749638.tar.gz -- http://sa-update.secnap.net/1749638.tar.gz
Jun 25 08:02:55.934 [29035] dbg: http: process [29049], exit status: exit 0
Jun 25 08:02:55.934 [29035] dbg: http: url:
http://sa-update.secnap.net/1749638.tar.gz.sha1
Jun 25 08:02:55.934 [29035] dbg: http: downloading to:
/home/jidanni1/.spamassassin-tree/var/spamassassin/4.000000/updates_spamassassin_org/1749638.tar.gz.sha1,
update
Jun 25 08:02:55.935 [29035] dbg: util: executable for curl was found at
/usr/bin/curl
Jun 25 08:02:55.935 [29035] dbg: http: /usr/bin/curl -s -L -O --remote-time -g
--max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o
1749638.tar.gz.sha1 -z 1749638.tar.gz.sha1 --
http://sa-update.secnap.net/1749638.tar.gz.sha1
Jun 25 08:02:56.160 [29035] dbg: http: process [29051], exit status: exit 0
Jun 25 08:02:56.161 [29035] dbg: http: url:
http://sa-update.secnap.net/1749638.tar.gz.asc
Jun 25 08:02:56.161 [29035] dbg: http: downloading to:
/home/jidanni1/.spamassassin-tree/var/spamassassin/4.000000/updates_spamassassin_org/1749638.tar.gz.asc,
update
Jun 25 08:02:56.161 [29035] dbg: util: executable for curl was found at
/usr/bin/curl
Jun 25 08:02:56.161 [29035] dbg: http: /usr/bin/curl -s -L -O --remote-time -g
--max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1749638.tar.gz.asc
-z 1749638.tar.gz.asc -- http://sa-update.secnap.net/1749638.tar.gz.asc
Jun 25 08:02:56.389 [29035] dbg: http: process [29053], exit status: exit 0
Jun 25 08:02:56.389 [29035] dbg: sha1: verification wanted:
5f08b36a5dc56c81b758f1aafe4cfb0afa5dcfad
Jun 25 08:02:56.389 [29035] dbg: sha1: verification result:
da3fe29840d7b717c0931b331dcb671b23cf4b5a
channel: SHA1 verification failed, channel failed
Jun 25 08:02:56.390 [29035] dbg: generic: cleaning up temporary directory/files
Jun 25 08:02:56.390 [29035] dbg: generic: cleaning directory
/tmp/.spamassassin29035fVUynftmp
Jun 25 08:02:56.390 [29035] dbg: diag: updates complete, exiting with code 4

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7331] channel: SHA1 verification failed, channel failed

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331

Kevin A. McGrail <km...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kmcgrail@apache.org

--- Comment #4 from Kevin A. McGrail <km...@apache.org> ---
Please add more logs and if you can, try manually downloading the files.  

The exact update I use is /usr/bin/rsync --timeout=280 -T /tmp -ta --delete
--address=69.171.29.39  rsync.spamassassin.org::updates
/htdocs/sa-update.pccc.com/html 

-delay-updates could make things more atomic but by default it's going to use a
tmp dir for the files.  


My big question is does a subsequent run fix the issue?  Is there a specific
mirror that might be having the issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7331] channel: SHA1 verification failed, channel failed

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331

Bill Cole <sa...@billmail.scconsult.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sa-bugz-20080315@billmail.s
                   |                            |cconsult.com

--- Comment #2 from Bill Cole <sa...@billmail.scconsult.com> ---
(In reply to Jonathan Kamens from comment #1)

> Is there a problem with the SpamAssassin update infrastructure? Is it
> overloaded? Can something be done?

I have not seen this at all. The specific error implies a corrupted rules
tarball, which is unlikely to be a load issue. I don't know if the mirrors are
updated atomically but if they are not, this could be the result, particularly
if you're running sa-update around 08:30 UTC, which is roughly when the daily
updates are ready to go out. KAM or Dave Jones could probably say whether
mirroring is done atomically (i.e. sending the file to a temporary name them
moving it to its accessible name) and when those actually complete.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7331] channel: SHA1 verification failed, channel failed

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331

jidanni@jidanni.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jidanni@jidanni.org

--- Comment #3 from jidanni@jidanni.org ---
I am now getting this error lots these days, maybe every two or three days, and
I update at 10:00 UTC.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7331] channel: SHA1 verification failed, channel failed

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331

Jonathan Kamens <ji...@kamens.us> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jik@kamens.us

--- Comment #1 from Jonathan Kamens <ji...@kamens.us> ---
This has recently started happening to me regularly on my Linode. I've seen it
four times in the last month, after literally not seeing it even once in my
several years of running SpamAssassin.

When I retry the next day it invariably works.

Is there a problem with the SpamAssassin update infrastructure? Is it
overloaded? Can something be done?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7331] channel: SHA1 verification failed, channel failed

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331

Dave Jones <da...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|dev@spamassassin.apache.org |davej@apache.org
             Status|NEW                         |ASSIGNED
                 CC|                            |davej@apache.org

--- Comment #6 from Dave Jones <da...@apache.org> ---
I received some detailed information from one of the mirror hosters that made
me think I need to put back in a delay of the TXT update used by sa-update to
give the mirrors time to pull the new ruleset files.

I have put a 10 minute delay in place on the DNS TXT updates which may clear up
this problem in roughly 12 hours.  It looks like there was about a 6 minute
window when DNS had updated right after 08:31 AM UTC before all mirrors had
updated by 08:41 AM UTC.

Thanks to all of those who enabled debugging.  Please keep them enabled for the
next few days or weeks in case this doesn't complete resolve the issue.

Dave

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7331] channel: SHA1 verification failed, channel failed

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331

--- Comment #5 from Jonathan Kamens <ji...@kamens.us> ---
(In reply to Kevin A. McGrail from comment #4)
> Please add more logs and if you can, try manually downloading the files.

I'm getting the error from sa-update.cron, so (a) I'm not around when it
happens in the middle of the night to retry it immediately, and (b) I have no
idea where, if anywhere, the logs from sa-update.cron are captured.

If you can advise me how to configure or modify the cron job so that it
captures logs, I will be glad to follow your advice to collect additional
information.

> My big question is does a subsequent run fix the issue?  Is there a specific
> mirror that might be having the issue?

When I get the error overnight and then rerun the update during the day when I
notice it, it usually works the second time.

-- 
You are receiving this mail because:
You are the assignee for the bug.