-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: Downloading artifacts from coordinator... error #1864
Comments
We've been starting to see this error too: Gitlab 11.7.5 with Runner 11.2 |
Please help. Solution/workaround/debug method needed!
GitLab Community Edition 12.3.5 |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
We recently encountered an intermittent issue when running the pipeline. We've recently upgraded to latest GitLab 11.7.5 and GitLab Runner 11.7.0, reverse proxy to Nginx 1.14.0 on Ubuntu 18.04. The following errors occurs intermittently, however the build/stage passes after a retry. We didn't have issues like this when we were in version 8.16.6 and Gitlab CI multi runner 1.x.
Downloading artifacts for build (53092)... ERROR: Downloading artifacts from coordinator... error error=read tcp 172.17.0.3:59476->xx.xxx.59.37:443: read: connection reset by peer id=53092 responseStatus=200 OK token=GrTYH7v2 WARNING: Retrying... ERROR: Downloading artifacts from coordinator... error error=read tcp 172.17.0.3:59478->xx.xxx.59.37:443: read: connection reset by peer id=53092 responseStatus=200 OK token=GrTYH7v2 WARNING: Retrying... ERROR: Downloading artifacts from coordinator... error error=read tcp 172.17.0.3:59480->xx.xxx.59.37:443: read: connection reset by peer id=53092 responseStatus=200 OK token=GrTYH7v2 FATAL: invalid argument ERROR: Job failed: exit code 1
The text was updated successfully, but these errors were encountered: