Skip to content
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

registry.yarnpg.com is down, but status.yarnpkg.com is green #5932

Closed
georgesequeira opened this issue Jun 5, 2018 · 45 comments
Closed

registry.yarnpg.com is down, but status.yarnpkg.com is green #5932

georgesequeira opened this issue Jun 5, 2018 · 45 comments
Assignees

Comments

@georgesequeira
Copy link

@georgesequeira georgesequeira commented Jun 5, 2018

At 2018-06-05 17:19 UTC

Running

while curl -I https://registry.yarnpkg.com/ ; do :; done

Shows intermittent 503s:

HTTP/2 200
date: Tue, 05 Jun 2018 17:13:51 GMT
content-type: text/plain
content-length: 4
set-cookie: __cfduid=dc18ec800fc64ed09ef1d844d6946fee61528218830; expires=Wed, 05-Jun-19 17:13:50 GMT; path=/; domain=.registry.yarnpkg.com; HttpOnly
cache-control: must-revalidate
cf-ray: 426445abfe7c2180-EWR
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare


HTTP/2 503
date: Tue, 05 Jun 2018 17:14:04 GMT
content-type: text/plain;charset=UTF-8
content-length: 28
set-cookie: __cfduid=d1ef1d891ac86c43ea1d759b1891cf9801528218831; expires=Wed, 05-Jun-19 17:13:51 GMT; path=/; domain=.registry.yarnpkg.com; HttpOnly
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 426445b129e421ce-EWR
...
....

But status.yarnpkg.com lists the registry as operational.

Currently https://status.npmjs.org/ shows a healthy status.

@ghost ghost assigned BYK Jun 5, 2018
@ghost ghost added the triaged label Jun 5, 2018
@stringbeans

This comment has been minimized.

Copy link

@stringbeans stringbeans commented Jun 5, 2018

i am also running into 503 errors occassionally when installing packages... for example:

[2/4] Fetching packages...
info If you think this is a bug, please open a bug report with the information provided in "/usr/src/app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error An unexpected error occurred: "https://registry.yarnpkg.com/node-pre-gyp/-/node-pre-gyp-0.6.36.tgz: Request failed \"503 Service Unavailable\"".
@BYK

This comment has been minimized.

Copy link
Member

@BYK BYK commented Jun 5, 2018

Works for me here from London. CloudFlare shows some reroutes but says things are fine in general: https://www.cloudflarestatus.com/

Don't really know what might be happening.

@stringbeans

This comment has been minimized.

Copy link

@stringbeans stringbeans commented Jun 5, 2018

strangely enough we are not experiencing the issues locally (we're in Vancouver Canada) but in our circleCI builds we're run into the 503 errors about 50% of the time

@Dog

This comment has been minimized.

Copy link

@Dog Dog commented Jun 5, 2018

I'm having the same experience in Seattle.

@brianleach

This comment has been minimized.

Copy link

@brianleach brianleach commented Jun 5, 2018

Getting 503 service unavailable on CircleCI.

#!/bin/bash -eo pipefail
cd www && yarn install
yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/spdy/-/spdy-3.4.7.tgz: Request failed \"503 Service Unavailable\"".
@anthonyroach

This comment has been minimized.

Copy link

@anthonyroach anthonyroach commented Jun 5, 2018

I'm seeing the same problem on a Jenkins slave running in us-east-1 of AWS (Virginia). Interestingly, I do not see it when running locally from Indianapolis, IN:

yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/regl-error2d/-/regl-error2d-2.0.4.tgz: Request failed \"503 Service
@arist0tl3

This comment has been minimized.

Copy link

@arist0tl3 arist0tl3 commented Jun 5, 2018

Confirmed on our CircleCI. Seems random, though I haven't seen the same package fail twice. Here are the latest three:

yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/babel-plugin-syntax-exponentiation-operator/-/babel-plugin-syntax-exponentiation-operator-6.13.0.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/circleci/repo/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1

yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/pinkie-promise/-/pinkie-promise-2.0.1.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/circleci/repo/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1

yarn install v0.24.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/map-keys-deep-lodash/-/map-keys-deep-lodash-1.2.0.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/circleci/repo/server/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
Exited with code 1
@ahunter-tehama

This comment has been minimized.

Copy link

@ahunter-tehama ahunter-tehama commented Jun 5, 2018

Same issue here:

yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/debug/-/debug-2.6.1.tgz: Request failed \"503 Service Unavailable\"".
yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
merror An unexpected error occurred: "https://registry.yarnpkg.com/raw-body/-/raw-body-2.2.0.tgz: Request failed \"503 Service Unavailable\"".

and so on intermittently

@BYK

This comment has been minimized.

Copy link
Member

@BYK BYK commented Jun 5, 2018

Reached out to CloudFlare, awaiting a response.

@bluepichu

This comment has been minimized.

Copy link

@bluepichu bluepichu commented Jun 5, 2018

I've been having a similar issue in a BitBucket Pipeline, but interestingly, with the --verbose flag set yarn install always succeeds. It seems like the added delay from all of the printing is preventing whatever the issue is from occurring.

@anthonyroach

This comment has been minimized.

Copy link

@anthonyroach anthonyroach commented Jun 5, 2018

I was able to work around the problem and get rid of the 503s by changing https://registry.yarnpkg.com to https://registry.npmjs.org/ in yarn.lock. This suggests that the problem is not the npmjs registry, but rather the yarnpkg registry.

@BYK

This comment has been minimized.

Copy link
Member

@BYK BYK commented Jun 5, 2018

I was able to work around the problem and get rid of the 503s by changing https://registry.yarnpkg.com to https://registry.npmjs.org/ in yarn.lock. This suggests that the problem is not the npmjs registry, but rather the yarnpkg registry.

@anthonyroach that is very unlikely since they are both behind CloudFlare and point to the same servers. I'd say this is just coincidence.

@Dog

This comment has been minimized.

Copy link

@Dog Dog commented Jun 5, 2018

I'm starting to see the failed builds resolving.

@DanielJoyce

This comment has been minimized.

Copy link

@DanielJoyce DanielJoyce commented Jun 5, 2018

We currently have codeship builds failing due to this

2018-06-05 21:06:23
yarn install v1.5.1
2018-06-05 21:06:23
[1/4] Resolving packages...
2018-06-05 21:06:23
[2/4] Fetching packages...
2018-06-05 21:06:38
error An unexpected error occurred: "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.0.tgz: Request failed \"503 Service Unavailable\"".
@Dog

This comment has been minimized.

Copy link

@Dog Dog commented Jun 5, 2018

FWIW I am no longer experiencing this.

All failed builds have passed, and no new failed builds yet.

@Gianfranco97

This comment has been minimized.

Copy link

@Gianfranco97 Gianfranco97 commented Jun 5, 2018

I also have the same problem in my CircleCI integration, everything worked yesterday but today I let it work.

captura de pantalla 2018-06-05 a la s 6 17 30 p m

[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@sonarwhal/rule-http-compression/-/rule-http-compression-4.0.2.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/root/repo/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1
@benjyblack

This comment has been minimized.

Copy link

@benjyblack benjyblack commented Jun 6, 2018

We are experiencing this still from our CircleCI builds. --verbose does not help. It's happening 95% of the time.

error An unexpected error occurred: "https://registry.yarnpkg.com/pug-lexer/-/pug-lexer-4.0.0.tgz: Request failed \"503 Service Unavailable\"".
@luislezcair

This comment has been minimized.

Copy link

@luislezcair luislezcair commented Jun 6, 2018

I'm experiencing the same problem when deploying to Heroku. It fails with random packages. It works fine locally.

Also, the registry status says it was last updated on May 25th: https://status.yarnpkg.com/

@geropl

This comment has been minimized.

Copy link

@geropl geropl commented Jun 6, 2018

We experience the same issue every other day, always around 3-5pm CET, in our own Jenkins-on-Docker build pipeline.
Any robust work around?

@wichert

This comment has been minimized.

Copy link

@wichert wichert commented Jun 6, 2018

We're seeing this happen 100% of the time as of today with requests coming from CircleCI.

@zwade

This comment has been minimized.

Copy link

@zwade zwade commented Jun 6, 2018

Following up on this, we've been having the same issue running both locally (under Docker) and on Bitbucket's pipelines. Solving the local issue, we found that the error only occurred when performing multiple parallel installs and that building them in sequence was sufficient to prevent 503's. I'm not sure this helps, but it backs up what @bluepichu was saying about needing to slow the install down.

@lookapanda

This comment has been minimized.

Copy link

@lookapanda lookapanda commented Jun 6, 2018

Same issue, our GitLab runner runs on AWS.

@ganglio

This comment has been minimized.

Copy link

@ganglio ganglio commented Jun 6, 2018

I'm experiencing the same issue in London. Building from the Docker container fails while building locally works.

@WebMex

This comment has been minimized.

Copy link

@WebMex WebMex commented Jun 6, 2018

The same issue for our Gitlab runner in Frankfurt. Verbose didn't help

@yv3s

This comment has been minimized.

Copy link

@yv3s yv3s commented Jun 6, 2018

Having the same issue in Paris

[2/4] Fetching packages... remote: error An unexpected error occurred: "https://registry.yarnpkg.com/uglifyjs-webpack-plugin/-/uglifyjs-webpack-plugin-1.2.3.tgz: Request failed \"503 Service Unavailable\"". remote: info If you think this is a bug, please open a bug report with the information provided in "/tmp/build_3466b5d056c6bb38c5e354a0a5942555/yarn-error.log". remote: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

@tjbrez

This comment has been minimized.

Copy link

@tjbrez tjbrez commented Jun 6, 2018

Seeing the same issue in Cleveland. Works locally, but CircleCI fails 90% of the time.

image

@HoughIO

This comment has been minimized.

Copy link

@HoughIO HoughIO commented Jun 6, 2018

An unexpected error occurred: \"https://registry.yarnpkg.com/css-select/-/css-select-1.2.0.tgz: Request failed \\\"503 Service Unavailable

As of 11:00AM EST 6/6/2018

Various packages fail in no particular order.

@rvirani1

This comment has been minimized.

Copy link

@rvirani1 rvirani1 commented Jun 6, 2018

We're getting this same error most of the time running in Amazon CodeBuild in us-east-1

@DanielJoyce

This comment has been minimized.

Copy link

@DanielJoyce DanielJoyce commented Jun 6, 2018

Outage resolved for us for now.

@jayschwa

This comment has been minimized.

Copy link

@jayschwa jayschwa commented Jun 6, 2018

We're still getting this error in Amazon's us-west-2.

@yv3s

This comment has been minimized.

Copy link

@yv3s yv3s commented Jun 6, 2018

@StasDachinsky

This comment has been minimized.

Copy link

@StasDachinsky StasDachinsky commented Jun 6, 2018

The same with circleCi :(

@efournival

This comment has been minimized.

Copy link

@efournival efournival commented Jun 6, 2018

Still not resolved under CircleCI:

yarn install v1.5.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/chalk/-/chalk-2.4.1.tgz: Request failed \"503 Service Unavailable\"".
info If you think this is a bug, please open a bug report with the information provided in "/root/moonapp/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Exited with code 1
@rufushonour

This comment has been minimized.

Copy link

@rufushonour rufushonour commented Jun 6, 2018

npm are now publicly acknowledging the issue: https://status.npmjs.org/incidents/qxj3kdzw4jrg

@draconteus

This comment has been minimized.

Copy link

@draconteus draconteus commented Jun 6, 2018

Temporarily changing to NPM and https://registry.npmjs.org/ can solve the problem.

@wcmonty

This comment has been minimized.

Copy link

@wcmonty wcmonty commented Jun 6, 2018

We added some retry logic in our build processes:

for i in {1..4}; do yarn install && break; done && yarn install

We try to install up to 4 times, then install a final time to make sure that we return the right status code.

@leff

This comment has been minimized.

Copy link

@leff leff commented Jun 6, 2018

NPM says they fixed it but we're still seeing 503 errors from registry.yarnpkg.com

@rvirani1

This comment has been minimized.

Copy link

@rvirani1 rvirani1 commented Jun 6, 2018

We're still seeing issues as well.

@leff

This comment has been minimized.

Copy link

@leff leff commented Jun 6, 2018

I tried replacing registry.yarnpkg.com with registry.npmjs.org in my yarn.lock file. The build has gotten past the yarn install step. I suspect registry.yarnpkg.com is caching the error responses.

@hemp

This comment has been minimized.

Copy link

@hemp hemp commented Jun 6, 2018

npmjs incident has been updated to resolved: https://status.npmjs.org/incidents/qxj3kdzw4jrg

@BYK BYK closed this Jun 12, 2018
@BYK BYK removed the needs-confirmation label Jun 12, 2018
@edarblanco

This comment has been minimized.

Copy link

@edarblanco edarblanco commented Jul 20, 2018

Oh why does this happen? again this is happening, error 503, don't install packages

@synalysis

This comment has been minimized.

Copy link

@synalysis synalysis commented Sep 1, 2018

I was able to resolve the issue locally by leaving the VPN connection (IPVanish).

But when deploying to zeit.co I had it again. Annoying.

@johnnyreilly

This comment has been minimized.

Copy link

@johnnyreilly johnnyreilly commented Sep 1, 2018

I'm completely out of action due to this. So frustrating.

[Edit]: for clarity; I'm in London. I'm under the impression all's good in the US now; but maybe not further afield

@andrjuha01

This comment has been minimized.

Copy link

@andrjuha01 andrjuha01 commented Sep 2, 2018

Same in Ukraine right now.

@jimitpatel

This comment has been minimized.

Copy link

@jimitpatel jimitpatel commented Sep 27, 2018

I was able to work around the problem and get rid of the 503s by changing https://registry.yarnpkg.com to https://registry.npmjs.org/ in yarn.lock. This suggests that the problem is not the npmjs registry, but rather the yarnpkg registry.

Worked for me like a charm... I am behind proxy. I replaced those link with proxy links... I had to change it eventhough I have changed it via npm config set registry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.