Skip to content
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.

503 No healthy backends #141

Closed
hugodes opened this issue Mar 15, 2017 · 2 comments
Closed

503 No healthy backends #141

hugodes opened this issue Mar 15, 2017 · 2 comments

Comments

@hugodes
Copy link

hugodes commented Mar 15, 2017

I've been getting this error for the past hour:

npm http 503 https://registry.npmjs.org/@types%2fexpress
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token < in JSON at position 1
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry <title>503 No healthy backends</title>
npm info retry
npm info retry
npm info retry

Error 503 No healthy backends


npm info retry

No healthy backends


npm info retry

Guru Mediation:


npm info retry

Details: cache-lhr6342-LHR 1489592768 3606632311


npm info retry

npm info retry

Varnish cache server


npm info retry
npm info retry
npm info retry
npm http 503 https://registry.npmjs.org/@types%2fbluebird
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token < in JSON at position 1
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry <title>503 No healthy backends</title>
npm info retry
npm info retry
npm info retry

Error 503 No healthy backends


npm info retry

No healthy backends


npm info retry

Guru Mediation:


npm info retry

Details: cache-lhr6342-LHR 1489592768 3606632317


npm info retry

npm info retry

Varnish cache server


npm info retry
npm info retry
npm info retry
npm http 200 https://registry.npmjs.org/validator
npm info retry fetch attempt 1 at 3:46:08 PM
npm info attempt registry request try #1 at 3:46:08 PM
npm http fetch GET https://registry.npmjs.org/validator/-/validator-6.2.1.tgz
npm http fetch 200 https://registry.npmjs.org/validator/-/validator-6.2.1.tgz
npm info attempt registry request try #2 at 3:46:18 PM
npm http request GET https://registry.npmjs.org/@types%2fexpress
npm info attempt registry request try #2 at 3:46:18 PM
npm http request GET https://registry.npmjs.org/@types%2fbluebird
npm http 503 https://registry.npmjs.org/@types%2fexpress
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token < in JSON at position 1
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry <title>503 No healthy backends</title>
npm info retry
npm info retry
npm info retry

Error 503 No healthy backends


npm info retry

No healthy backends


npm info retry

Guru Mediation:


npm info retry

Details: cache-lcy1142-LCY 1489592778 1226956056


npm info retry

npm info retry

Varnish cache server


npm info retry
npm info retry
npm info retry
npm http 503 https://registry.npmjs.org/@types%2fbluebird
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token < in JSON at position 1
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry
npm info retry <title>503 No healthy backends</title>
npm info retry
npm info retry
npm info retry

Error 503 No healthy backends


npm info retry

No healthy backends


npm info retry

Guru Mediation:


npm info retry

Details: cache-lhr6341-LHR 1489592778 1961767458


npm info retry

npm info retry

Varnish cache server


npm info retry
npm info retry
npm info retry

@ashleygwilliams
Copy link
Contributor

ashleygwilliams commented Mar 15, 2017

hi @hugodes ! so sorry you ran into this error. we actually had a minor service issue due to some 🔥 nasty bot 🤖 behavior (in the future checkout our status page here: http://status.npmjs.org/incidents/5mbr4c40fx0t). everything should be working now! please file again if you continue to have trouble. and sorry again :(

@hugodes
Copy link
Author

hugodes commented Mar 16, 2017

@ashleygwilliams Thanks for you're response, the thing though, is I checked the status page, and it said "All systems operational", even though I was getting these errors.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants