Closed jimbair closed 4 years ago
Oops I completely missed this, sorry. Already 5 months passed. :-( Okay I take a look - I just use the defaults, so I am not sure how much can be done to mitigate this on the client side.
If you try to run curl say on that dir what happens or how long does it take? Is it on some slow net storage or something?
To troubleshoot, I ran wget/cURL with various timeouts to confirm - it is in fact a slow HTTP response causing the issue (I believe I set the timeout in wget to 30 to replicate). Once I re-ran the wget after the 30s timeout, usually the next one worked. I'm not sure what was slowing down the web server, but my guess was back-end storage.
The current work-around is to run the test twice, but an adjustable timeout would solve the problem for us. =)
Okay, I try to see if I can add an option for that, thanks
Okay so the http-client library defaults to 30s timeout - okay it should be easy to add an option to change that.
Okay I have added --timeout
for version 0.4, which I plan to release soon.
I think this can be closed now, but do let me know how it works for you.
While running this on the OSCI side of the house, one of our VMs is taking longer to respond on occasion. I am trying to troubleshoot on my side, but it would be helpful if maybe we could allow this to run for longer than 30 seconds?
I'm doing what I can on my side to reproduce the issue to find the root cause of the hiccup; ironically, second runs diff without any issues. :) I assume it's the server caching something (or getting NFS to wake up).
Any help/insight is appreciated!