There is so much crap in stdin that the text file for the debug output is so big I can't even open it. It only occurs on occasion, I can't replicate it reliably.
On Tue, Apr 10, 2018 at 3:27 PM, Tim Rühsen <tim.rueh...@gmx.de> wrote: > > > On 10.04.2018 20:37, Jeffrey Fetterman wrote: > > with --tries=5 set, Failed to connect (111) will still instantly abort > the > > operation. > > As I wrote, not reproducible here (see my debug output). Please append > your debug output. > > Regards, Tim > > > On Tue, Apr 10, 2018 at 2:45 AM, Tim Rühsen <tim.rueh...@gmx.de> wrote: > > > >> On 04/10/2018 03:12 AM, Jeffrey Fetterman wrote: > >>> --retry_connrefused is mentioned in the documentation but it doesn't > seem > >>> to be an option anymore. I can't find a replacement for it, either. My > >> VPN > >>> is being a bit fussy today and I keep having to restart my script > because > >>> of 111 errors. > >>> > >> I assume wget2... use --tries. That value is currently also used for > >> connection failures. > >> > >> ... > >> [0] Downloading 'http://localhost' ... > >> 10.073423.223 cookie_create_request_header for host=localhost > path=(null) > >> Failed to write 207 bytes (111: Connection refused) > >> 10.073423.223 host_increase_failure: localhost failures=1 > >> ... > >> > >> Regards, Tim > >> > >> > > >