On 9/20/2018 7:18 AM, Matus UHLAR - fantomas wrote: >> On Wed, 5 Sep 2018 10:08:24 +0200 Matus UHLAR - fantomas wrote: >>> I (imho too often) get problems when running sa-update (Debian 8, SA >>> 3.4.0) >>> >> >>> found at /usr/bin/curl Sep 5 07:38:31.810 [16137] dbg: >>> http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 >>> --connect-timeout 30 --max-time 300 --fail -o 1840016.tar.gz -z >>> 1840016.tar.gz -- http://sa-update.secnap.net/1840016.tar.gz Sep 5 >>> 07:38:33.211 [16137] dbg: http: process [16166], exit status: 0 ... >>> Sep 5 07:38:33.799 [16137] dbg: sha1: verification wanted: >>> ea88487c6e9cd48fb3e546606eac2effe4a3a91c Sep 5 07:38:33.799 [16137] >>> dbg: sha1: verification result: >>> 953efe8f531a5a87f6d2d5a65b78b05e55599abc channel: SHA1 verification >>> failed, channel failed >> ... >>> or should I dig into that deeper to find out what happens? > > On 06.09.18 18:27, RW wrote: >> I'd start by editing sa-update and removing the --fail argument to curl. > > according to curl documentation, it would only cause to output error > message > instead of the file itself. > > Is this what you advise me to achieve? > > ...according to my reading of sa-update, the sa-update selects mirror > and only > fetches from it. possibility of fetching from multiple mirrors would help > here. > Dave, is secnap one of the mirrors using a CDN?
-- Kevin A. McGrail VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
