Re: [lftp] misbehaving HTTP server makes lftp retry forever
A that makes sense, and that'll work, thanks! On Thu, Apr 14, 2016 at 5:36 AM, Alexander V. Lukyanovwrote: > On Thu, Apr 14, 2016 at 01:50:35AM -0500, Nate Sutton wrote: > > I tried it and setting it to a low timeout setting (10) made it fail > with a > > timeout, so it does work for the purpose, but if possible I'd like to > just > > limit the number of retries. Is there a setting I'm missing, maybe? > > It should not be set to a low value, the default is one day. The timer is > reset every time when the transfer goes over "high watermark". So when the > transfer starts over and does not reach the high watermark for the > specified in xfer:timeout time, the transfer times out and fails. > > -- >Alexander. > > > On Wed, Apr 13, 2016 at 8:46 PM, Nate Sutton > > wrote: > > > > > What should I be setting this to? I don't quite understand how setting > a > > > timeout will fix this issue, could you explain? lftp isn't stalling for > > > very long while downloading and intermittent stalls in transfers ought > to > > > be tolerated, so I wouldn't want to set it too low. And besides, the > error > > > message "recv: SSL_read: error::lib(0):func(0):reason(0)" > implies > > > that the peer shut down the connection, right? It seems in this case > that > > > limiting the number of retries when the peer terminates the connection > > > would be better, since otherwise it gets that error message and > retries the > > > transfer again and again forever. > > > > > > Thoughts? > > > > > > On Wed, Apr 13, 2016 at 5:00 AM, Alexander V. Lukyanov > > > wrote: > > > > > >> On Tue, Mar 29, 2016 at 07:37:06PM -0500, Nate Sutton wrote: > > >> > I'm downloading from an HTTP server where it stops sending the file > at > > >> > about 40 MB and then stops sending data. lftp doesn't seem to handle > > >> this > > >> > very well and retries the transfer over and over and over, > indefinitely. > > >> > > > >> > https://gist.github.com/nate/e7e47d3a86118439c36a1877847d8b01 > > >> > > > >> > This happens with pget -n 5, pget -n 1, and get. > > >> > > > >> > Is this expected behavior? Is there a way to disable it? Or set a > max > > >> > number of retries? net:max-retries is already set to 3... > > >> > > >> Please test > > >> > > >> > https://github.com/lavv17/lftp/commit/989b10e928d73136ef2460572350f14a6a6d14c7 > > >> or http://lftp.yar.ru/ftp/devel/lftp-4.7.1.8-a7ceb-dirty.tar.gz > > >> which introduces new xfer:timeout setting. > > >> > > >> -- > > >>Alexander. > > >> > > > > > > > > > ___ > > lftp mailing list > > lftp@uniyar.ac.ru > > http://univ.uniyar.ac.ru/mailman/listinfo/lftp > ___ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp
Re: [lftp] misbehaving HTTP server makes lftp retry forever
On Thu, Apr 14, 2016 at 01:50:35AM -0500, Nate Sutton wrote: > I tried it and setting it to a low timeout setting (10) made it fail with a > timeout, so it does work for the purpose, but if possible I'd like to just > limit the number of retries. Is there a setting I'm missing, maybe? It should not be set to a low value, the default is one day. The timer is reset every time when the transfer goes over "high watermark". So when the transfer starts over and does not reach the high watermark for the specified in xfer:timeout time, the transfer times out and fails. -- Alexander. > On Wed, Apr 13, 2016 at 8:46 PM, Nate Sutton> wrote: > > > What should I be setting this to? I don't quite understand how setting a > > timeout will fix this issue, could you explain? lftp isn't stalling for > > very long while downloading and intermittent stalls in transfers ought to > > be tolerated, so I wouldn't want to set it too low. And besides, the error > > message "recv: SSL_read: error::lib(0):func(0):reason(0)" implies > > that the peer shut down the connection, right? It seems in this case that > > limiting the number of retries when the peer terminates the connection > > would be better, since otherwise it gets that error message and retries the > > transfer again and again forever. > > > > Thoughts? > > > > On Wed, Apr 13, 2016 at 5:00 AM, Alexander V. Lukyanov > > wrote: > > > >> On Tue, Mar 29, 2016 at 07:37:06PM -0500, Nate Sutton wrote: > >> > I'm downloading from an HTTP server where it stops sending the file at > >> > about 40 MB and then stops sending data. lftp doesn't seem to handle > >> this > >> > very well and retries the transfer over and over and over, indefinitely. > >> > > >> > https://gist.github.com/nate/e7e47d3a86118439c36a1877847d8b01 > >> > > >> > This happens with pget -n 5, pget -n 1, and get. > >> > > >> > Is this expected behavior? Is there a way to disable it? Or set a max > >> > number of retries? net:max-retries is already set to 3... > >> > >> Please test > >> > >> https://github.com/lavv17/lftp/commit/989b10e928d73136ef2460572350f14a6a6d14c7 > >> or http://lftp.yar.ru/ftp/devel/lftp-4.7.1.8-a7ceb-dirty.tar.gz > >> which introduces new xfer:timeout setting. > >> > >> -- > >>Alexander. > >> > > > > > ___ > lftp mailing list > lftp@uniyar.ac.ru > http://univ.uniyar.ac.ru/mailman/listinfo/lftp ___ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp
Re: [lftp] misbehaving HTTP server makes lftp retry forever
What should I be setting this to? I don't quite understand how setting a timeout will fix this issue, could you explain? lftp isn't stalling for very long while downloading and intermittent stalls in transfers ought to be tolerated, so I wouldn't want to set it too low. And besides, the error message "recv: SSL_read: error::lib(0):func(0):reason(0)" implies that the peer shut down the connection, right? It seems in this case that limiting the number of retries when the peer terminates the connection would be better, since otherwise it gets that error message and retries the transfer again and again forever. Thoughts? On Wed, Apr 13, 2016 at 5:00 AM, Alexander V. Lukyanovwrote: > On Tue, Mar 29, 2016 at 07:37:06PM -0500, Nate Sutton wrote: > > I'm downloading from an HTTP server where it stops sending the file at > > about 40 MB and then stops sending data. lftp doesn't seem to handle this > > very well and retries the transfer over and over and over, indefinitely. > > > > https://gist.github.com/nate/e7e47d3a86118439c36a1877847d8b01 > > > > This happens with pget -n 5, pget -n 1, and get. > > > > Is this expected behavior? Is there a way to disable it? Or set a max > > number of retries? net:max-retries is already set to 3... > > Please test > > https://github.com/lavv17/lftp/commit/989b10e928d73136ef2460572350f14a6a6d14c7 > or http://lftp.yar.ru/ftp/devel/lftp-4.7.1.8-a7ceb-dirty.tar.gz > which introduces new xfer:timeout setting. > > -- >Alexander. > ___ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp
Re: [lftp] misbehaving HTTP server makes lftp retry forever
I tried it and setting it to a low timeout setting (10) made it fail with a timeout, so it does work for the purpose, but if possible I'd like to just limit the number of retries. Is there a setting I'm missing, maybe? On Wed, Apr 13, 2016 at 8:46 PM, Nate Suttonwrote: > What should I be setting this to? I don't quite understand how setting a > timeout will fix this issue, could you explain? lftp isn't stalling for > very long while downloading and intermittent stalls in transfers ought to > be tolerated, so I wouldn't want to set it too low. And besides, the error > message "recv: SSL_read: error::lib(0):func(0):reason(0)" implies > that the peer shut down the connection, right? It seems in this case that > limiting the number of retries when the peer terminates the connection > would be better, since otherwise it gets that error message and retries the > transfer again and again forever. > > Thoughts? > > On Wed, Apr 13, 2016 at 5:00 AM, Alexander V. Lukyanov > wrote: > >> On Tue, Mar 29, 2016 at 07:37:06PM -0500, Nate Sutton wrote: >> > I'm downloading from an HTTP server where it stops sending the file at >> > about 40 MB and then stops sending data. lftp doesn't seem to handle >> this >> > very well and retries the transfer over and over and over, indefinitely. >> > >> > https://gist.github.com/nate/e7e47d3a86118439c36a1877847d8b01 >> > >> > This happens with pget -n 5, pget -n 1, and get. >> > >> > Is this expected behavior? Is there a way to disable it? Or set a max >> > number of retries? net:max-retries is already set to 3... >> >> Please test >> >> https://github.com/lavv17/lftp/commit/989b10e928d73136ef2460572350f14a6a6d14c7 >> or http://lftp.yar.ru/ftp/devel/lftp-4.7.1.8-a7ceb-dirty.tar.gz >> which introduces new xfer:timeout setting. >> >> -- >>Alexander. >> > > ___ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp