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 #5846

Open
OlafMerkert opened this issue May 22, 2018 · 12 comments
Open

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

OlafMerkert opened this issue May 22, 2018 · 12 comments
Assignees
Labels

Comments

@OlafMerkert
Copy link

@OlafMerkert OlafMerkert commented May 22, 2018

At 2018-05-22 09:22:01+02:00,

registry.yarnpg.com returns the following error message:

Error 503 No healthy backends
No healthy backends

Guru Mediation:
Details: cache-fra19124-FRA 1526973594 170258232

Varnish cache server

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

@ghost ghost assigned arcanis May 22, 2018
@ghost ghost added the triaged label May 22, 2018
@CzarScar

This comment has been minimized.

Copy link

@CzarScar CzarScar commented May 22, 2018

I also struggled with this error. Please help us?

@neilstudd

This comment has been minimized.

Copy link

@neilstudd neilstudd commented May 22, 2018

Looks to be due to degraded performance on NPM's side: https://status.npmjs.org/

Edit: NPM fix implemented and Yarn has returned to normal for me

image

@OlafMerkert

This comment has been minimized.

Copy link
Author

@OlafMerkert OlafMerkert commented May 22, 2018

But there also seems to be an issue with the status page? It should show the correct status of the registry when it is not reachable?

@neilstudd

This comment has been minimized.

Copy link

@neilstudd neilstudd commented May 22, 2018

Agreed - although this particular incident is resolved, it should have been showing problems on the Yarn status page even if the problem originated upstream.

@hielfx

This comment has been minimized.

Copy link

@hielfx hielfx commented May 23, 2018

I still got this problem; yarn add fails but npm install works fine. The yarn registry site still shows a 503 with guru meditation

@zacblazic

This comment has been minimized.

Copy link

@zacblazic zacblazic commented May 23, 2018

Looks down again, possibly due to NPM:

image

@pariola

This comment has been minimized.

Copy link

@pariola pariola commented Sep 2, 2018

Seems down!

@arcanis

This comment has been minimized.

Copy link
Member

@arcanis arcanis commented Sep 2, 2018

https://twitter.com/yarnpkg/status/1035896058616991744

We're aware of connectivity issues when accessing the registry. We believe they are caused by a dns resolution problem that affected npm - it should resolve once the various dns caches get cleared. More info at https://status.npmjs.org/

More generally speaking, if you see the registry going down, it's highly unlikely the problem comes from us, and even more unlikely we can do anything about it, since we don't maintain an full mirror.

@pariola

This comment has been minimized.

Copy link

@pariola pariola commented Sep 2, 2018

Oh, thanks!

@zhuangya

This comment has been minimized.

Copy link

@zhuangya zhuangya commented Jan 24, 2019

sorry to bring this up, but:

error An unexpected error occurred: "https://registry.yarnpkg.com/@fortawesome/free-solid-svg-icons/-/free-solid-svg-icons-5.6.0.tgz: Request failed \"500 Internal Server Error\"".

anything wrong with yarnpkg now?

@arcanis

This comment has been minimized.

Copy link
Member

@arcanis arcanis commented Jan 24, 2019

More generally speaking, if you see the registry going down, it's highly unlikely the problem comes from us, and even more unlikely we can do anything about it, since we don't maintain an full mirror.

@OlafMerkert

This comment has been minimized.

Copy link
Author

@OlafMerkert OlafMerkert commented Jan 25, 2019

To clarify: this issue is not about the yarn registry being down because the npm registry is down. Obviously, if the yarn registry is just a mirror, then not much can be done about this.

My suggestion is however to make this more transparent on http://status.yarnpkg.com. The fact that the yarn registry is a mirror may not be obvious to every user. I noticed that there is currently a tooltip on the status page, but perhaps something even more prominent would be helpful?

Or even better, the status page could link to npmjs status page?

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