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

Error installing Kudu Sync #30

Closed
ollieglass opened this issue Jul 1, 2014 · 3 comments
Closed

Error installing Kudu Sync #30

ollieglass opened this issue Jul 1, 2014 · 3 comments

Comments

@ollieglass
Copy link
Contributor

Hi, I get this error running the deploy script

Installing Kudu Sync

An error has occurred during web site deployment.
npm failed

Running npm install kudusync -g on the terminal (the command in deploy.sh that fails), I get this:

npm http GET https://registry.npmjs.org/kudusync

npm ERR! Error: failed to fetch from registry: kudusync
npm ERR!     at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12
npm ERR!     at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9)
npm ERR!     at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18)
npm ERR!     at Request.callback (/usr/lib/nodejs/request/main.js:119:22)
npm ERR!     at Request.<anonymous> (/usr/lib/nodejs/request/main.js:212:58)
npm ERR!     at Request.emit (events.js:88:20)
npm ERR!     at ClientRequest.<anonymous> (/usr/lib/nodejs/request/main.js:412:12)
npm ERR!     at ClientRequest.emit (events.js:67:17)
npm ERR!     at HTTPParser.onIncoming (http.js:1261:11)
npm ERR!     at HTTPParser.onHeadersComplete (http.js:102:31)
npm ERR! You may report this log at:
npm ERR!     <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR!     reportbug --attach /vagrant/npm-debug.log npm
npm ERR! 
npm ERR! System Linux 3.2.0-23-generic
npm ERR! command "node" "/usr/bin/npm" "install" "kudusync" "-g"
npm ERR! cwd /vagrant
npm ERR! node -v v0.6.12
npm ERR! npm -v 1.1.4
npm ERR! message failed to fetch from registry: kudusync
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /vagrant/npm-debug.log
npm not ok

Here's a /vagrant/npm-debug.log:

vagrant@precise64:/vagrant$ cat npm-debug.log 
info it worked if it ends with ok
verbose cli [ 'node', '/usr/bin/npm', 'install', 'kudusync', '-g' ]
info using npm@1.1.4
info using node@v0.6.12
verbose config file /home/vagrant/.npmrc
verbose config file /usr/etc/npmrc
verbose config file /usr/share/npm/npmrc
verbose cache add [ 'kudusync', null ]
silly cache add: name, spec, args [ undefined, 'kudusync', [ 'kudusync', null ] ]
verbose parsed url { pathname: 'kudusync', path: 'kudusync', href: 'kudusync' }
verbose addNamed [ 'kudusync', '' ]
verbose addNamed [ null, '' ]
silly name, range, hasData [ 'kudusync', '', false ]
verbose raw, before any munging kudusync
verbose url resolving [ 'https://registry.npmjs.org/', './kudusync' ]
verbose url resolved https://registry.npmjs.org/kudusync
http GET https://registry.npmjs.org/kudusync
ERR! Error: failed to fetch from registry: kudusync
ERR!     at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12
ERR!     at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9)
ERR!     at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18)
ERR!     at Request.callback (/usr/lib/nodejs/request/main.js:119:22)
ERR!     at Request.<anonymous> (/usr/lib/nodejs/request/main.js:212:58)
ERR!     at Request.emit (events.js:88:20)
ERR!     at ClientRequest.<anonymous> (/usr/lib/nodejs/request/main.js:412:12)
ERR!     at ClientRequest.emit (events.js:67:17)
ERR!     at HTTPParser.onIncoming (http.js:1261:11)
ERR!     at HTTPParser.onHeadersComplete (http.js:102:31)
ERR! You may report this log at:
ERR!     <http://bugs.debian.org/npm>
ERR! or use
ERR!     reportbug --attach /vagrant/npm-debug.log npm
ERR! 
ERR! System Linux 3.2.0-23-generic
ERR! command "node" "/usr/bin/npm" "install" "kudusync" "-g"
ERR! cwd /vagrant
ERR! node -v v0.6.12
ERR! npm -v 1.1.4
ERR! message failed to fetch from registry: kudusync
verbose exit [ 1, true ]

Any idea what's wrong? I'm not familiar with node / npm.

@ollieglass
Copy link
Contributor Author

Related to pull request #31

@bewest
Copy link
Member

bewest commented Jul 1, 2014

Kudu is only used in Azure by MS. Users never run that.

Users just run npm install.

On Tue, Jul 1, 2014 at 5:01 AM, Ollie Glass notifications@github.com
wrote:

Related to pull request #31
#31


Reply to this email directly or view it on GitHub
#30 (comment)
.

@bewest
Copy link
Member

bewest commented Jul 6, 2014

Looks like you figured things out, closing this for now.

@bewest bewest closed this as completed Jul 6, 2014
freddyyi pushed a commit to freddyyi/cgm-remote-monitor that referenced this issue Apr 22, 2022
tzachi-dar referenced this issue in tzachi-dar/nightscout-vps Nov 15, 2022
Read /etc/nsconfig every time that the node server is restarted.
justinthomas pushed a commit to justinthomas/cgm-remote-monitor that referenced this issue Nov 29, 2022
Fix a bug where our freedns name was having a capital name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants