I think the Coral CDN isn't working out as a way to distribute sa-update files.
Timeouts have been pretty common, but today, I got this: [7788] dbg: channel: selected mirror http://buildbot.spamassassin.org.nyud.net:8090/updatestage [7788] dbg: http: GET request, http://buildbot.spamassassin.org.nyud.net:8090/updatestage/419191.tar.gz [7788] dbg: http: request failed, retrying: 500 Server closed connection without sending any data back: 500 Server closed connection without sending any data back [7788] dbg: http: GET request, http://buildbot.spamassassin.org.nyud.net:8090/updatestage/419191.tar.gz [7788] dbg: http: GET request, http://buildbot.spamassassin.org.nyud.net:8090/updatestage/419191.tar.gz.sha1 [7788] dbg: http: request failed, retrying: 500 read timeout: 500 read timeout [7788] dbg: http: GET request, http://buildbot.spamassassin.org.nyud.net:8090/updatestage/419191.tar.gz.sha1 [7788] dbg: http: request failed, retrying: 500 read timeout: 500 read timeout [7788] dbg: http: GET request, http://buildbot.spamassassin.org.nyud.net:8090/updatestage/419191.tar.gz.sha1 [7788] dbg: http: GET request, http://buildbot.spamassassin.org.nyud.net:8090/updatestage/419191.tar.gz.asc [7788] dbg: http: IMS GET request, http://buildbot.spamassassin.org.nyud.net:8090/updatestage/MIRRORED.BY, Mon, 23 Jan 2006 21:41:42 GMT [7788] dbg: sha1: verification expected: a91e971400d632310a02425429580ee12afe47cb [7788] dbg: sha1: verification got : d519c8f9d5e985fc0345c37ec8849a8daf5265d7 in other words, somehow the downloaded file didn't match hashes! That's not good at all. (I don't suspect foul play, since obv it won't be used anyway due to the hash-verification failure -- just brokenness.) I've switched the default MIRRORED.BY location from the Coral CDN to a plain old vhost on the zone instead, for now. Question: should we change this to use the ASF mirror infrastructure at www.apache.org/dist/ ? *Can* we? Is it ok to do so? (I seem to recall possible issues.) --j.
