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 2018/04/11 08:02:43 UTC

[Bug 7575] New: "SHA1 verification failed" for sa-update.bitwell.fi

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

            Bug ID: 7575
           Summary: "SHA1 verification failed" for sa-update.bitwell.fi
           Product: Spamassassin
           Version: 3.4.1
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sa-update
          Assignee: dev@spamassassin.apache.org
          Reporter: larsen007@web.de
                CC: davej@apache.org, kmcgrail@apache.org,
                    larsen007@web.de
  Target Milestone: Undefined

As has been the case before in bug #7566, servers started to report a problem
for mirror "sa-update.bitwell.fi"

/etc/cron.daily/60sa-update:
channel: SHA1 verification failed, channel failed
run-parts: /etc/cron.daily/60sa-update exited with return code 4


Apr 11 06:39:41.457 [5379] dbg: channel: selected mirror
http://sa-update.bitwell.fi
Apr 11 06:39:41.457 [5379] dbg: http: url:
http://sa-update.bitwell.fi/1828798.tar.gz
Apr 11 06:39:41.457 [5379] dbg: http: downloading to:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/1828798.tar.gz, new
Apr 11 06:39:41.457 [5379] dbg: util: executable for curl was found at
/usr/bin/curl
Apr 11 06:39:41.457 [5379] dbg: http: /usr/bin/curl -s -L -O --remote-time -g
--max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1828798.tar.gz --
http://sa-update.bitwell.fi/1828798.tar.gz
Apr 11 06:39:41.592 [5379] dbg: http: process [5380], exit status: 0
Apr 11 06:39:41.593 [5379] dbg: http: url:
http://sa-update.bitwell.fi/1828798.tar.gz.sha1
Apr 11 06:39:41.593 [5379] dbg: http: downloading to:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/1828798.tar.gz.sha1,
new
Apr 11 06:39:41.593 [5379] dbg: util: executable for curl was found at
/usr/bin/curl
Apr 11 06:39:41.593 [5379] dbg: http: /usr/bin/curl -s -L -O --remote-time -g
--max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o
1828798.tar.gz.sha1 -- http://sa-update.bitwell.fi/1828798.tar.gz.sha1
Apr 11 06:39:41.649 [5379] dbg: http: process [5382], exit status: 0
Apr 11 06:39:41.649 [5379] dbg: http: url:
http://sa-update.bitwell.fi/1828798.tar.gz.asc
Apr 11 06:39:41.649 [5379] dbg: http: downloading to:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/1828798.tar.gz.asc, new
Apr 11 06:39:41.649 [5379] dbg: util: executable for curl was found at
/usr/bin/curl
Apr 11 06:39:41.649 [5379] dbg: http: /usr/bin/curl -s -L -O --remote-time -g
--max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1828798.tar.gz.asc
-- http://sa-update.bitwell.fi/1828798.tar.gz.asc
Apr 11 06:39:41.702 [5379] dbg: http: process [5384], exit status: 0
Apr 11 06:39:41.702 [5379] dbg: sha1: verification wanted:
284ff19512c725e50ee91b2c11f6cec48553dce7
Apr 11 06:39:41.702 [5379] dbg: sha1: verification result:
e3766f40615972e0c31ff0043b03ebd818ae2b63
channel: SHA1 verification failed, channel failed

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

[Bug 7575] "SHA1 verification failed" for sa-update.bitwell.fi

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

--- Comment #3 from Kevin A. McGrail <km...@apache.org> ---
+1 to anything that gets rid of two PUBLISHED files with the same name.

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

[Bug 7575] "SHA1 verification failed" for sa-update.bitwell.fi

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

--- Comment #2 from Dave Jones <da...@apache.org> ---
I think this could still be the result of caching.

I have been thinking about the best way to handle our problem with the same SVN
version having two different rulesets built (tick from rule promotions and tock
from the masscheck score updates).

For now I think we can disable the ruleset build from the rule promotions since
the masscheck has been running well for a while.  Then I can figure out some
logic to best detect when the masscheck doesn't update the ruleset so the rule
promotions can build a new ruleset.

Bottom line is we only want one ruleset to be built per SVN tagged revision so
there has to be some coordination between the tick and tock.  Maybe I can do
something as simple as check the last ruleset build easily with the find
command for being more than ~20 hours old in the rule promotion script.

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

[Bug 7575] "SHA1 verification failed" for sa-update.bitwell.fi

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

--- Comment #1 from Kevin A. McGrail <km...@apache.org> ---
I think we still have a race condition where a mirror can grab a file and we
need to create the temp file in a non sync'd location.  So 7566 is still not
100% resolved.

Dave, would this fall under the time period for the race condition?  I'm
guessing no and that this is just a transient issue.  I downloaded manually and
bitwell.fi seems fine.

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

[Bug 7575] "SHA1 verification failed" for sa-update.bitwell.fi

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|dev@spamassassin.apache.org |davej@apache.org

--- Comment #4 from Dave Jones <da...@apache.org> ---
Trying to resolve this with commit rev 1828938.  I will continue to monitor
this situation until I can make this recent ruleset from the mkupdates
(masscheck) detection work.

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