Wget read error connection reset by peer

I am using the following code to download a list of pdf files:

wget -i list.txt -A .pdf

Some pdf files are downloaded properly. However, some pdf files are not downloaded properly. When I check the log, I see the following report:

--2013-04-09 11:25:42--  http://amazon.com/111.pdf
Reusing existing connection to amazon.com:80.
HTTP request sent, awaiting response... 200 No headers, assuming HTTP/0.9
Length: unspecified
Saving to: `111.pdf'


    [                                         <=>       ] 1,045       --.-K/s   in 2m 9s


2013-04-09 11:27:51 (8.11 B/s) - Read error at byte 1045 (Connection reset by peer).Retrying.


--2013-04-09 11:27:52--  (try: 2)  http://amazon.com/111.pdf
Connecting to amazon.com (amazon.com)|00.00.55.888|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2680728 (2.6M) [application/pdf]
Saving to: `111.pdf'


61% [==============================>                    ] 1,649,221   10.0K/s   in 2m 41s


2013-04-09 11:30:41 (10.0 KB/s) - Read error at byte 1649221/2680728 (Connection reset by peer). Retrying.


--2013-04-09 11:30:43--  (try: 3)  http://amazon.com/111.pdf
Connecting to amazon.com (amazon.com)|00.00.55.888|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2680728 (2.6M) [application/pdf]
Saving to: `111.pdf'


100%[==================================================>] 2,680,728   10.1K/s   in 4m 22s


2013-04-09 11:35:11 (10.0 KB/s) - `111.pdf' saved [2680728/2680728]

I wonder why I can not open the pdf file 111.pdf? The above report says that it is 100% downloaded. Is it because of the connection reset by the peer?

I wonder if it is possible to put the wget in a loop for every file, in such a way that it does not exit the loop, until the download is done with no error?
I found the following loop, however, it gives an error. The code and the error is shown below:

Code:

while read -r link
do
        wget -A .pdf
        until [ $? = 0 ]
        do
            wget -A .pdf
        done
done < ./list.txt

Error:

Try `wget --help' for more options.
wget: missing URL
Usage: wget [OPTION]... [URL]...

I am using Cygwin on Windows.

Please let me know if you have other suggestions as well.

Thank you for your help.

alpine:3.6 is unable to wget http://google.com #344

However, alpine:3.5 is fine.
Docker version 17.04.0-ce, build 78d1802
Bare metal host: openSUSE Leap 42.3 with 4.4.87-25-default kernel.

ping -c1 google.com works even on alpine:3.6 .

The text was updated successfully, but these errors were encountered:

I can’t reproduce: 😕

@tianon On what operating system did you tried it?

I cannot reproduce either (on my linux desktop):

Same on my macbook.

Do you use http proxy?

@ncopa Nope, no HTTP proxy is involved. Tried wget 127.0.0.1 as well, but no luck.

My test was also on a Linux desktop, but I’ve also just verified on http://play-with-docker.com/ for good measure (and it works fine there as well, so this is very likely something broken in your local environment).

Have you tried pulling the latest alpine:3.6 image ( docker pull alpine:3.6 )? Do you have any kind of firewall in place, including/especially one you don’t control, such as are common in many corporate and educational environments?

Yes, I tried alpine:3.6 as well:

There is probably some kind of firewall included, I am on closed corporate network (inbound-wise), but I don’t know anything about it. What I do see is that alpine:3.5 is fine and alpine:3.6 fails to connect. Still for sure it could be something in the network or in the underlying operating system.

If you know how could one debug it (e.g. from network perspective), I might give it a try.

@mnowaksuse: Alpine 3.6 packages Busybox 1.26.2, which is what provides wget in the default build, but it has a bug connecting to some servers or middleboxes: I’ve hit this when connecting to Nginx acting as a TCP proxy that would forward requests to a HTTP server.

The fix here might be to install the wget package, which provides the actual wget binary, as opposed to using Busybox for wget .

Alternatively, I believe the next Alpine version will include Busybox 1.27, where this issue is fixed. Can you try using alpine:edge here: docker run —rm alpine:edge wget http://google.com ?

Thanks @krallin! That’s probably it. apline:edge works just fine. That might explain why others who connected from different places with the same OS as me were able to use alpine:3.6 .

Источник

wget installation does not work on Alpine #73

Steps to reproduce

Expected result

dumb-init is installed, as it happens when using the ubuntu container, e.g..

Actual result

An error message is returned by wget:

Connecting to github.com (192.30.252.120:443)
wget: can’t execute ‘ssl_helper’: No such file or directory
wget: error getting response: Connection reset by peer

Any thoughts on this?

The text was updated successfully, but these errors were encountered:

Okay, forget it … it was a problem with the CA certificates on Alpine Linux. You need to run

before running wget , then it works 🙂

FYI for others coming across this, adding the above commands to my Dockerfile did not work, I needed to specifically add the ca-certificates to wget like this:

that worked perfectly and my image built with no problems.

openssl package may be required too:

apk update && apk add ca-certificates && update-ca-certificates && apk add openssl

How difficult would it be to make an apk package for dumb-init? We’re experienced in debian packaging but unfamiliar with alpine’s ecosystem and would love help if it’s possible

For those who arrive here, another solution is simply to use curl instead, if your idea is to run install scripts. It sounds even simpler, with less options to deal with — the default is to send to stdin for instance.

Источник

[BUG] docker images not support right version of wget #421

Describe the bug
wget download speedtest cli tool fail
command wget https://bintray.com/ookla/download/download_file?file_path=ookla-speedtest-1.0.0-x86_64-linux.tgz -O speedtest.tgz

To Reproduce
create a new docker container.
You will see the fail log

Expected behavior
Wget download success then execute the nginx

Screenshots

Context

• OS: docker
• Speedtest-Tracker Version: 1.10.0

Additional context
We may need to add the following package into the docker image or docker file.

or rebuild the docker images self

The text was updated successfully, but these errors were encountered:

Hi i installed synology docker and always restart docker here is log:

Why not install this? If i try login ip no webpage.

I don’t think that is a Synology problem. I use other devices and have the same result.
I believe some upstream package has been changed.

possible relate to #208

I’ve just run this command in a new container and it downloads fine. This line seems to me like it’s a network issue you are having:

Umm. I don’t think that is a network issue. I login to the docker container and run the wget and resulting in the same thing. However, I install the wget and ca-certificate the issue solved

how can install wget? if i write terminal container speedtest say no url

@felho001, You need to attache your docker container via docker exec -it default docker_name is speedtest

Источник

Comments

Previously, it occassionally happened (EBI cluster, PHIPO vagrant server) that wget failed with a (connection reset by peer) error, see Yelp/dumb-init#73.

The problem is solved by re-installing openssl and wget.

`wget` doesn't work on Alpine when making a request via an HTTPS
proxy. See Yelp/dumb-init#73 but the
workarounds there don't work either.

`wget` doesn't work on Alpine when making a request via an HTTPS
proxy. See Yelp/dumb-init#73 but the
workarounds there don't work either.