Re: OT: diagnosing download problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 15Jun2021 09:12, Geoffrey Leach <geoff@xxxxxxxxxx> wrote:
>Configuration: Fedora 32 with Netgear Nighthawk R7000 router talking to
>Hughes satellite.
>
>Problem: Connecting (only) to Amazon, (any) page hangs attempting to
>download (apparently) an image from images-na.ssl-images-amazon.com.
>Download succeeds for a dozen or so jpegs, then it hangs. Problem
>appears to be independent of browser (chrome, firefox) and OS (happens
>on (gasp) Windows 7 also).
>
>Traceroute images-na.ssl-images-amazon.com shows the round trip time to
>suddenlink.net around 2000 ms.

That seems large. Is it always around 2000ms or particularly when this 
fails?

I've a satellite connection to a geosynchronous service (Australian NBN 
SkyMuster) and ping times are generally in the 600ms-700ms range unless 
things are very bad.

>So why am I bothering the list? It's Amazon's problem, after all.
>
>Question: are there any settings on my end that might be tweaked to get
>around the problem? Is there any way to diagnose the problem on my end?

I'd start with trying to separate things out a bit. Do you have a log of 
the image URLs? Is this tied to a specific URL?

Do you run a web proxy? Bypass it.

If you have a list of the URLs (up to and including the stall) you could 
run a series of _distinct_ wget or curl commands to fetch the images, 
and see how they behave. This bypasses persistent connections which 
might be maintained by a web browser (or a batch fetch of many URLs from 
a single wget/curl command). Thinking about a persistent connection 
going sour here.

The problem with a persistent connection is that it only takes a single 
intermediate stateful router to decide to drop the connection state on 
the floor for things to go bad. Usually you should get a failure and the 
browser should retry though.

Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux