<div class="gmail_quote">On Sun, Jun 27, 2010 at 8:44 PM, Gavin Hurlbut <span dir="ltr"><<a href="mailto:gjhurlbu@gmail.com">gjhurlbu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><div class="gmail_quote">On Sun, Jun 27, 2010 at 8:12 PM, Gavin Hurlbut <span dir="ltr"><<a href="mailto:gjhurlbu@gmail.com" target="_blank">gjhurlbu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div><div class="gmail_quote">On Sun, Jun 27, 2010 at 11:48 AM, James Orr <span dir="ltr"><<a href="mailto:james.orr7@gmail.com" target="_blank">james.orr7@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I try to download channel icons via mythtv-setup I am getting the following errors ...<div><br></div><div><div>2010-06-27 14:38:07.482 HttpComms::Timeout for url: <a href="http://lyngsat-logo.com/logo/tv/aa/ae_us.jpg" target="_blank">http://lyngsat-logo.com/logo/tv/aa/ae_us.jpg</a></div>
<div>2010-06-27 14:38:07.501 Server returned an error status code 0 for url: <a href="http://lyngsat-logo.com/logo/tv/aa/ae_us.jpg" target="_blank">http://lyngsat-logo.com/logo/tv/aa/ae_us.jpg</a></div></div><div><br></div>
<div>Navigating to the link in a browser works fine.</div>
</blockquote></div></div></div></blockquote></div></div></div></blockquote></div><br><div>OK, here's the scoop. It seems that the URLs we fetch from return a 301 (Permanent Redirect). This means we hit the server twice. That's normally OK, *BUT* mythtv-setup doesn't cache DNS lookups, so it is hitting your DNS resolver (as setup by /etc/resolv.conf) repeatedly. IF your DNS lookups are slow, it takes forever, and the logo download will exceed the 10s which seems to be the default timeout in the code.</div>
<div><br></div><div>So... I am considering changing the timeout to 20s, but additionally, use faster DNS servers. If you are up for running your own caching server, that will likely be the best over-all, but otherwise, you are likely best off pointing /etc/resolv.conf to google's public DNS caches (8.8.8.8 and 8.8.4.4).</div>