| Main Archive Page > Month Archives > spamassassin-dev archives |
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
From: <bugzilla-daemon_at_nospam>Date: Tue Feb 21 2012 - 18:08:26 GMT
To: dev@spamassassin.apache.org
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
--- Comment #3 from Kevin A. McGrail <kmcgrail@pccc.com> 2012-02-21 18:08:26 UTC ---
(In reply to comment #2)
> Kevin, thanks for the insights. I'm not so sure this should be set as RESOLVED
> FIXED however, as it obviously isn't fixed:
>
> Date: Tue, 21 Feb 2012 00:43:06 -0800 (PST)
> http: GET http://daryl.dostech.ca/sa-update/asf/1291150.tar.gz request failed:
> 500 Can't connect to daryl.dostech.ca:80 (timeout):
> Can't connect to daryl.dostech.ca:80 (timeout) LWP::Protocol::http::Socket:
> connect: timeout at
> /usr/local/lib/perl5/site_perl/5.12.4/LWP/Protocol/http.pm line 51.
>
> Possibly RESOLVED WONTFIX would be more appropriate?
Agreed.
> Also: do you know if this issue is specific to certain times of the day (e.g.
> should I change my cronjob to run sa-update at a different time)?
I don't, sorry.
> How do I
> squelch the LWP error output (sa-update has no --quiet equivalent) aside from
> piping it to the equivalent of grep -v?
sa-update 2>&1 > /dev/null would work.
> If this kind of transient error is considered acceptable, then I would advocate
> that sa-update should trap the LWP error condition either through
> $ref->is_error() verification or using eval {}; (if needed) and not complain on
> these types of errors (but make sure to complain in the case that all mirrors
> fail, of course!).
I agree. I run sa-update -D and didn't care about the copious information. Are
you running sa-update more than once a day? If so, that's largely unnecessary.
Low priority but this would be good polish.
-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.