Open sleungcy opened 1 year ago
One quick way to fix this is to use --retry-all-errors instead of --retry https://stackoverflow.com/questions/10285700/curl-error-recv-failure-connection-reset-by-peer-php-curl#:~:text=One%20way%20we%20can%20avoid,number%20of%20worker_connections%20in%20nginx.
Note that --retry-all-errors
only exists since curl v7.71.0 changelog. Therefore, it cannot be used in cflinuxfs3, but it should be available in cflinuxfs4.
A fix that would address this behaviour for cflinuxfs4 stack is proposed: PR Add option --retry-all-errors when downloading go version
@ivanovac implemented a small go server, which simulates the "connection reset by peer" by sending RST to the client. With this we were able to confirm, that those types of transient TCP issues are ignored by the curl --retry
mechanism and can be handled only by --retry-all-errors
.
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version
?What version of the buildpack you are using?
If you were attempting to accomplish a task, what was it you were attempting to do?
What did you expect to happen?
What was the actual behavior?
Sample log output from running the same curl command
To reproduce, create a sample app(doesn't matter what app), then create a run-task that perpetually download the go binary
Can you provide a sample app?
Please confirm where necessary: