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 2012/02/20 10:03:09 UTC
[Bug 6761] New: Intermittent fetch failures from daryl.dostech.ca
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
Bug #: 6761
Summary: Intermittent fetch failures from daryl.dostech.ca
Product: Spamassassin
Version: 3.3.2
Platform: PC
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: P2
Component: sa-update
AssignedTo: dev@spamassassin.apache.org
ReportedBy: jdc@parodius.com
Classification: Unclassified
I thought I got done dealing with this type of problem back in Bug 6511, but
apparently something else is up/wonky now.
For the past week or so, we've been seeing intermittent failures of different
kinds when sa-update runs and tries to download content from
http://daryl.dostech.ca/sa-update/asf/
Below are the failures we've seen sa-update spit out, as well as the
dates/times when the failures occurred, and what the failure messages were per
perl LWP. Note that the failures are not all the same kind. We run sa-update
once a day.
Date: Tue, 14 Feb 2012 00:43:22 -0800 (PST)
http: GET http://daryl.dostech.ca/sa-update/asf/1243434.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.
Date: Wed, 15 Feb 2012 00:43:50 -0800 (PST)
http: GET http://daryl.dostech.ca/sa-update/asf/1243828.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.
Date: Mon, 20 Feb 2012 00:43:19 -0800 (PST)
http: GET http://daryl.dostech.ca/sa-update/asf/1290969.tar.gz request failed:
500 read timeout: read timeout at
/usr/local/lib/perl5/site_perl/5.12.4/LWP/Protocol/http.pm line 433.
sa-update supposedly worked despite these failures (exit code 0 was returned),
so I imagine one of the other mirrors was used, but they all have the same
weight so maybe this problem is intermittent in nature due to that?
# cat MIRRORED.BY
# test mirror: zone, cached via Coral
#http://buildbot.spamassassin.org.nyud.net:8090/updatestage/
http://daryl.dostech.ca/sa-update/asf/ weight=5
http://www.sa-update.pccc.com/ weight=5
http://sa-update.secnap.net/ weight=5
So in this case, Daryl C. W. O'Shea needs to look at his server and/or
surrounding network to see what is going on. I'm sorry that I don't have
traceroutes or anything else to go on -- I can set up periodic traceroutes to
daryl.dostech.ca if folks think its a network layer problem (I'm well aware
that the Internet is constantly broken :-) ). Or maybe it's box maintenance; I
don't know.
If you need any other information, let me know.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
Darxus <Da...@ChaosReigns.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Darxus@ChaosReigns.com
Resolution|WONTFIX |DUPLICATE
--- Comment #7 from Darxus <Da...@ChaosReigns.com> ---
Marking duplicate of bug 6838 since there is more discussion of the same issue
there, in case anybody comes across this one later.
*** This bug has been marked as a duplicate of bug 6838 ***
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
Kevin A. McGrail <km...@pccc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #6 from Kevin A. McGrail <km...@pccc.com> ---
The system is designed to automatically try other mirrors as the main
resiliency so as long as you are getting the update, that's the key concern.
However, you might try a later time in the day for your cron to run to help
alleviate the issue and I'll reach out to the mirror operator.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
--- Comment #3 from Kevin A. McGrail <km...@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.
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
Jeremy Chadwick <jd...@parodius.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |jdc@parodius.com
Resolution|FIXED |
--- Comment #2 from Jeremy Chadwick <jd...@parodius.com> 2012-02-21 09:46:48 UTC ---
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?
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)? How do I
squelch the LWP error output (sa-update has no --quiet equivalent) aside from
piping it to the equivalent of grep -v?
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!).
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
--- Comment #4 from Jeremy Chadwick <jd...@parodius.com> 2012-02-22 12:26:05 UTC ---
Keeping my reply simple: we run sa-update once a day, at 00:40 Pacific Time.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
Bernhard Schmidt <be...@birkenwald.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |berni@birkenwald.de
--- Comment #5 from Bernhard Schmidt <be...@birkenwald.de> ---
For a couple of days now, daryl.dostech.ca seems to be lagging behind in
updates. Almost every run I get a message like
http: GET http://daryl.dostech.ca/sa-update/asf/1387911.tar.gz request failed:
404 Not Found: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head>
<title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested
URL /sa-update/asf/1387911.tar.gz was not found on this server.</p> <hr>
<address>Apache/2.2.6 (Fedora) Server at daryl.dostech.ca Port 80</address>
</body></html>
not fatal, since sa-update tries the other mirrors too, but something one
should have a look at.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 6761] Intermittent fetch failures from daryl.dostech.ca
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6761
Kevin A. McGrail <km...@pccc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |kmcgrail@pccc.com
Resolution| |FIXED
--- Comment #1 from Kevin A. McGrail <km...@pccc.com> 2012-02-20 14:16:24 UTC ---
Thanks. We have scripts in place that notify us of the outages. So this is a
known issue but considered non-priority since sa-update will automatically use
one of the other update providers if a different one is down.
Regards,
KAM
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.