npm publish - ERROR 503 backend read error ???

gistfile1.txt

For me the weakest part of using node.js is the npm publish command

what gives ???




stens@kamchatka ~/Dropbox/Documents/code/github/websockets-streaming-audio $ npm publish --ddd
npm info it worked if it ends with ok
npm verb cli [ '/home/stens/bin_0_10_32/nodejs/bin/node',
npm verb cli   '/home/stens/bin_0_10_32/nodejs/bin/npm',
npm verb cli   'publish',
npm verb cli   '--ddd' ]
npm info using npm@1.4.28
npm info using node@v0.10.32
npm verb publish [ '.' ]
npm verb cache add [ '.', null ]
npm verb cache add name=undefined spec="." args=[".",null]
npm verb parsed url { protocol: null,
npm verb parsed url   slashes: null,
npm verb parsed url   auth: null,
npm verb parsed url   host: null,
npm verb parsed url   port: null,
npm verb parsed url   hostname: null,
npm verb parsed url   hash: null,
npm verb parsed url   search: null,
npm verb parsed url   query: null,
npm verb parsed url   pathname: '.',
npm verb parsed url   path: '.',
npm verb parsed url   href: '.' }
npm sill lockFile 3a52ce78- .
npm verb lock . /home/stens/.npm/3a52ce78-.lock
npm verb tar pack [ '/home/stens/.npm/websockets-streaming-audio/0.8.14/package.tgz',
npm verb tar pack   '.' ]
npm verb tarball /home/stens/.npm/websockets-streaming-audio/0.8.14/package.tgz
npm verb folder .
npm info prepublish websockets-streaming-audio@0.8.14
npm sill lockFile 1f1177db-tar tar://.
npm verb lock tar://. /home/stens/.npm/1f1177db-tar.lock
npm sill lockFile 0a92d9a9-reaming-audio-0-8-14-package-tgz tar:///home/stens/.npm/websockets-streaming-audio/0.8.14/package.tgz
npm verb lock tar:///home/stens/.npm/websockets-streaming-audio/0.8.14/package.tgz /home/stens/.npm/0a92d9a9-reaming-audio-0-8-14-package-tgz.lock
|
\
/
npm sill lockFile 1f1177db-tar tar://.
npm sill lockFile 1f1177db-tar tar://.
npm sill lockFile 0a92d9a9-reaming-audio-0-8-14-package-tgz tar:///home/stens/.npm/websockets-streaming-audio/0.8.14/package.tgz
npm sill lockFile 0a92d9a9-reaming-audio-0-8-14-package-tgz tar:///home/stens/.npm/websockets-streaming-audio/0.8.14/package.tgz
npm sill lockFile a793c1c7-s-streaming-audio-0-8-14-package /home/stens/.npm/websockets-streaming-audio/0.8.14/package
npm verb lock /home/stens/.npm/websockets-streaming-audio/0.8.14/package /home/stens/.npm/a793c1c7-s-streaming-audio-0-8-14-package.lock
npm sill lockFile a793c1c7-s-streaming-audio-0-8-14-package /home/stens/.npm/websockets-streaming-audio/0.8.14/package
npm sill lockFile a793c1c7-s-streaming-audio-0-8-14-package /home/stens/.npm/websockets-streaming-audio/0.8.14/package
npm sill lockFile 3a52ce78- .
npm sill lockFile 3a52ce78- .
npm sill publish { author: 
npm sill publish    { name: 'Scott Stensland',
npm sill publish      email: 'scottstensland@gmail.com',
npm sill publish      url: 'http://catfoodnation.com/' },
npm sill publish   bugs: { url: 'https://github.com/scottstensland/websockets-streaming-audio/issues' },
npm sill publish   dependencies: 
npm sill publish    { ws: '0.4.x',
npm sill publish      express: '^4.4.5',
npm sill publish      'audio-utils': '1.0.x',
npm sill publish      'shared-utils': '0.1.8' },
npm sill publish   description: 'Click a browser button to launch a node.js process on the server side which streams audio using web sockets back to the browser which is then rendered using web audio API   My plan is to make this modular enough to get added to your process as simple API calls',
npm sill publish   engines: { node: '0.10.x' },
npm sill publish   homepage: 'https://github.com/scottstensland',
npm sill publish   keywords: [ 'websockets', 'webaudio', 'audio', 'streaming', 'binary' ],
npm sill publish   license: 'ISC',
npm sill publish   main: 'src/app.js',
npm sill publish   name: 'websockets-streaming-audio',
npm sill publish   repository: 
npm sill publish    { type: 'git',
npm sill publish      url: 'https://github.com/scottstensland/websockets-streaming-audio.git' },
npm sill publish   scripts: { start: 'node src/app.js', test: 'make' },
npm sill publish   subdomain: 'websockets-streaming-audio',
npm sill publish   version: '0.8.14',
npm sill publish   readme: 'websockets-streaming-audio\n==========================\n\nClick a browser button to launch a node.js process on the server side which streams audio using web sockets back to the browser which is then rendered using web audio API\n\nMy plan is to make this modular enough to get added to your process as simple API calls\n\n[![NPM](https://nodei.co/npm/websockets-streaming-audio.png?downloads=true&downloadRank=true&stars=true)](https://nodei.co/npm/websockets-streaming-audio/)\n\n# Installation\n\nvisit [nodejs.org](http://nodejs.org) and install node.js\n\nsee project npm site at \n\n[https://www.npmjs.org/package/websockets-streaming-audio](https://www.npmjs.org/package/websockets-streaming-audio)\n\n\n\n\nClone this repository to your local machine:\n\n```bash\nnpm install websockets-streaming-audio\n```\nChange directory into the project folder websockets-streaming-audio\n\nThen install the dependent modules:\n\n```bash\nnpm install\n```\n\n\nLaunch the nodejs app:\n\n```bash\nnpm start\n```\n\n\nUsing a WebGL savvy browser, point it at URL :\n\n```bash\n\t\t http://localhost:8888 \n```\n\nnow in your browser (firefox/chrome) click stream_audio\n\nor ignore above and just see this WebGL app deployed live on heroku :\n\n[http://websockets-streaming-audio.herokuapp.com](http://websockets-streaming-audio.herokuapp.com)\n\n\nFeel free to contact me on twitter if you have any questions! :) [@scottstensland](http://twitter.com/scottstensland)\n\n\n',
npm sill publish   readmeFilename: 'README.md',
npm sill publish   gitHead: 'aa5efee73017bfc44fb5377df2ff08e3c2a31018',
npm sill publish   _id: 'websockets-streaming-audio@0.8.14',
npm sill publish   _shasum: 'ca94ae12bb9e23b5fa7cd32afa22d15fd9848450',
npm sill publish   _from: '.' }
npm verb request where is /websockets-streaming-audio
npm verb request registry https://registry.npmjs.org/
npm verb request id f4897ad56ed643f0
npm verb url raw /websockets-streaming-audio
npm verb url resolving [ 'https://registry.npmjs.org/',
npm verb url resolving   './websockets-streaming-audio' ]
npm verb url resolved https://registry.npmjs.org/websockets-streaming-audio
npm verb request where is https://registry.npmjs.org/websockets-streaming-audio
npm info trying registry request attempt 1 at 20:52:19
npm http PUT https://registry.npmjs.org/websockets-streaming-audio




npm http 503 https://registry.npmjs.org/websockets-streaming-audio
npm verb bad json 
npm verb bad json <?xml version="1.0" encoding="utf-8"?>
npm verb bad json <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
npm verb bad json  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
npm verb bad json <html>
npm verb bad json   <head>
npm verb bad json     <title>503 backend read error</title>
npm verb bad json   </head>
npm verb bad json   <body>
npm verb bad json     <h1>Error 503 backend read error</h1>
npm verb bad json     <p>backend read error</p>
npm verb bad json     <h3>Guru Mediation:</h3>
npm verb bad json     <p>Details: cache-atl6221-ATL 1412385356 3499523329</p>
npm verb bad json     <hr>
npm verb bad json     <p>Varnish cache server</p>
npm verb bad json   </body>
npm verb bad json </html>
npm verb bad json 
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token <
npm info retry 
npm info retry <?xml version="1.0" encoding="utf-8"?>
npm info retry <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
npm info retry  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
npm info retry <html>
npm info retry   <head>
npm info retry     <title>503 backend read error</title>
npm info retry   </head>
npm info retry   <body>
npm info retry     <h1>Error 503 backend read error</h1>
npm info retry     <p>backend read error</p>
npm info retry     <h3>Guru Mediation:</h3>
npm info retry     <p>Details: cache-atl6221-ATL 1412385356 3499523329</p>
npm info retry     <hr>
npm info retry     <p>Varnish cache server</p>
npm info retry   </body>
npm info retry </html>
npm info retry