bug-wget
[Top][All Lists]
Advanced

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

Re: [Bug-wget] wget2 hanging, possible I/O issue


From: Jeffrey Fetterman
Subject: Re: [Bug-wget] wget2 hanging, possible I/O issue
Date: Wed, 4 Apr 2018 06:32:53 -0500

How well does TeamViewer work on Linux? My laptop has been collecting dust,
I can just leave it running for a couple days with a fresh install of
Windows and a fresh install of WSL Debian (with apt-get update and upgrade
already ran)

On Wed, Apr 4, 2018 at 3:22 AM, Tim Rühsen <address@hidden> wrote:

> Hi Jeffrey,
>
> possibly I can get my hands on a fast Win10 desktop the coming
> weekend... no promise but I'll try.
>
>
> With Best Regards, Tim
>
>
>
> On 04/04/2018 09:54 AM, Tim Rühsen wrote:
> > Hi Jeffrey,
> >
> > I can't tell you. Basically because the only WSL I can get my hands on
> > is on my wife's laptop which is *very* slow. And it needs some analysis
> > on that side, maybe with patches for gnulib. Send me a fast Win10
> > machine and I analyse+fix the problem ;-)
> >
> >
> > BTW, we are also not using SO_REUSEPORT. The links you provided assume
> > that it's a problem in that area. All I can say is that Wget2 was
> > definitely working on WSL just a few weeks ago.
> >
> >
> > Another option for you is to install Debian/Ubuntu in a VM. Until the
> > hickups with WSL have been solved one or another way.
> >
> >
> > With Best Regards, Tim
> >
> >
> > On 04/04/2018 09:01 AM, Jeffrey Fetterman wrote:
> >> Tim, do you know when you'll be able to examine and come up with a
> >> workaround for the issue? There are alternatives to wget2 but either
> >> they're not high performance or they're not really cut out for site
> >> scraping.
> >>
> >> On Mon, Apr 2, 2018 at 12:30 PM, Jeffrey Fetterman <
> address@hidden>
> >> wrote:
> >>
> >>> I can tell you the exact steps I took from nothing to a fresh install,
> I
> >>> have the commands copied.
> >>>
> >>> install Debian from Windows Store, set up username/password
> >>>
> >>> $ sudo sh -c "echo kernel.yama.ptrace_scope = 0 >>
> >>> /etc/sysctl.d/10-ptrace.conf; sysctl --system -a -p | grep yama"
> >>> (this is a workaround for Valgrind and anything else that relies
> >>> on prctl(PR_SET_PTRACER) and the wget2 problem will occur either way)
> >>>
> >>> $ sudo apt-get update
> >>> $ sudo apt-get upgrade
> >>> $ sudo apt-get install autoconf autogen automake autopoint doxygen flex
> >>> gettext git gperf lcov libtool lzip make pandoc python3.5 pkg-config
> >>> texinfo valgrind libbz2-dev libgnutls28-dev libgpgme11-dev
> >>> libiconv-hook-dev libidn2-0-dev liblzma-dev libnghttp2-dev
> >>> libmicrohttpd-dev libpcre3-dev libpsl-dev libunistring-dev zlib1g-dev
> >>> $ sudo update-alternatives --install /usr/bin/python python
> >>> /usr/bin/python3.5 1
> >>>
> >>> then the commands outlined as per the documentation. config.log
> attached.
> >>>
> >>> On Mon, Apr 2, 2018 at 11:53 AM, Tim Rühsen <address@hidden>
> wrote:
> >>>
> >>>> Hi Jeffrey,
> >>>>
> >>>>
> >>>> basically wget2 should work on WSL, I just tested it scarcely two
> weeks
> >>>> ago without issues.
> >>>>
> >>>>
> >>>> I suspect it might have to do with your dependencies (e.g. did you
> >>>> install libnghttp2-dev ?).
> >>>>
> >>>> To find out, please send your config.log. That allows me to see your
> >>>> compiler, CFLAGS and the detected dependencies etc..
> >>>>
> >>>> I will try to reproduce the issue then.
> >>>>
> >>>>
> >>>> Regards, Tim
> >>>>
> >>>>
> >>>> On 02.04.2018 17:42, Jeffrey Fetterman wrote:
> >>>>>  wget2 will not download any files, and I think there's some sort of
> >>>> disk
> >>>>> access issue.
> >>>>>
> >>>>> this is on Windows Subsystem for Linux Debian 9.3 Stretch. (Ubuntu
> 16.04
> >>>>> LTS had the same issue.)
> >>>>>
> >>>>> Here's the output of strace -o strace.txt -ff wget2
> >>>> https://www.google.com
> >>>>>
> >>>>> https://pastebin.com/4MEL88qs
> >>>>>
> >>>>> wget2 -d https://www.google.com just hangs after the line
> >>>> '02.103350.008
> >>>>> ALPN offering http/1.1'
> >>>>>
> >>>>> ultimately I might have to submit a bug to WSL but I wouldn't know
> what
> >>>> to
> >>>>> report, I don't know what's wrong. And it'd be great if there was a
> >>>>> workaround
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >
>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]