Error 28: Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds

[paul.d...@nbacc.dhs.gov]

I am seeing this over and over on the downloads listed below.  If I run a plain "curl -o URL", the files download fine at over 1Mbps.  Same for wget on that box, and on a windows box using the same proxy Firefox and IE..  Reposado runs curl with the following parameters and gets the associated errors over and over.

eb 02 10:37:01 279 products found in http://swscan.apple.com/content/catalogs/index.sucatalog
Feb 02 10:37:31 Could not replicate http://swcdn.apple.com/content/downloads/01/50/061-2015/P7CqWdfQZPJ28P8fj9v3DSPRPpg8jKY7Rk/WebObjects5.3.1ServerUpdate.tar: Error 28: Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds
Feb 02 10:38:01 Could not replicate http://swcdn.apple.com/content/downloads/46/63/061-2071/3bW2nCmk6h4ckp5WstM2Qbw5pZKW56j7hG/Java131and142Release2.tar: Error 28: Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds
Feb 02 10:38:31 Could not replicate http://swcdn.apple.com/content/downloads/06/24/061-2242/TLFnnWPZmjbXBjsx5zSPdRxxqH869Nfchv/J2SE50Release4.tar: Error 28: Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds
Feb 02 10:39:01 Could not replicate http://swcdn.apple.com/content/downloads/60/03/061-2330/X3Kb6dKSJbnGK3nR7KnM8VLfzYJPKCGsFZ/J2SE50Release4.tar: Error 28: Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds
Feb 02 10:39:32 Could not replicate http://swcdn.apple.com/content/downloads/39/32/061-3124/Rk9jGtk4Lvmr52Rdt7ztzW3dHrvp4vMVdW/WebObjects5.3.3Update.tar: Error 28: Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds



cat /tmp/tmpmu60Gd/curl_temp
silent
show-error
no-buffer
fail
dump-header -
speed-time = 30
tlsv1
url = "http://swcdn.apple.com/content/downloads/06/24/061-2242/TLFnnWPZmjbXBjsx5zSPdRxxqH869Nfchv/J2SE50Release4.tar"
proxy = "PROXYINFOHERE"

[Greg Neagle]

Looks to me like you have all the info you need to do additional troubleshooting:

1) A curl command that works as you expect

2) A curl command that times out.

You should now experiment with the parameters to curl to determine what is triggering the undesired behavior in your environment.

-Greg

--
You received this message because you are subscribed to the Google Groups "reposado" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reposado+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[paul.d...@nbacc.dhs.gov]

Trying that now but its not providing consistent results which is causing me some head scratching because when repo_sync does it, it consistently times out.  Will keep trying to find something conclusive. 

[paul.d...@nbacc.dhs.gov]

OK.  If I use the repo_sync curl config file, removing silent and setting the timeout to 60 seconds, sometimes it will start at around 45 seconds, and sometimes it still times out.  If download the file directly with "-O", it starts within 5 seconds.  If I use the repo_sync config file with only silent removed, and specify "-O", the download starts within 5 seconds.  I've repeated this three times using each scenario. I'm going to try to modify the repo_sync script to include that unless there is a way to pass additional parameters to curl via the repo_sync syntax.

[Gregory Neagle]

AdditionalCurlOptions as described here https://github.com/wdas/reposado/blob/master/docs/reposado_preferences.md#optional-keys might be useful.

I can't imagine how the -O option would have any affect on download speeds as it merely controls the output filename.

Keep digging, and good luck.

-Greg

[paul.d...@nbacc.dhs.gov]

"I can't imagine how the -O option would have any affect on download speeds as it merely controls the output filename."

Yeah, I'm finding that out.  I think me exporting http_proxy and https_proxy in the bash profile is confusing the issue.  removing that and trying some things.

[paul.d...@nbacc.dhs.gov]

Sorry for the wasted time.  This must be an issue with the proxy and my re-produced results coincidental.  I unset both the http_proxy and https_proxy variables, removed the proxy specification from the config, and manually specified "curl -x PROXY:PORT".  Sometimes it started right away, sometimes it timed out at 30 seconds.  When I upped the timeout to 60 seconds sometimes it didn't start again until 45 seconds,and sometimes it timed out.  I've changed the timeout 120 and thus far it works as often as it fails, which is better than never working I suppose.  I re-synced the entire repo over the last 24 hours and oddly only these five files have been problematic.  Anyway, thanks for your time.