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.
On 9/20/2018 7:18 AM, Matus UHLAR - fantomas wrote:
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.
On 20.09.18 07:58, Kevin A. McGrail wrote:
Dave, is secnap one of the mirrors using a CDN?
unfortunately, secnap is not the only mirror with which the problem occurs.
Sep 20 07:25:34.589 [30532] dbg: http: url:
http://www.sa-update.pccc.com/1841300.tar.gz.asc
Sep 20 07:25:34.589 [30532] dbg: http: downloading to:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/1841300.tar.gz.asc, new
Sep 20 07:25:34.589 [30532] dbg: util: executable for curl was found at
/usr/bin/curl
Sep 20 07:25:34.589 [30532] dbg: http: /usr/bin/curl -s -L -O --remote-time -g
--max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1841300.tar.gz.asc
-- http://www.sa-update.pccc.com/1841300.tar.gz.asc
Sep 20 07:25:34.823 [30532] dbg: http: process [30569], exit status: 0
Sep 20 07:25:34.824 [30532] dbg: sha1: verification wanted:
37342f104bce02b8ede7a769b3c23ddc0b02dc3d
Sep 20 07:25:34.824 [30532] dbg: sha1: verification result:
7a65e9db86acc2901a90be825d1efc0990f8c020
channel: SHA1 verification failed, channel failed
it also is not the only one roblem that occurs, the
"channel: could not find working mirror, channel failed"
happens quite often too.
I have tried to remove the "--fail" option so maybe the output will help me
a bit. Otoh, my questions still apply:
- is this possible problem with mirrors?
- when do mirrors update?
- do mirrors updates propagate atomically?
perhaps the sa-update could be changed to try with more mirrors?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"To Boot or not to Boot, that's the question." [WD1270 Caviar]
