Troubles running and/or installing on Mac OSX 10.9

[owntheweb-archive]

Hello,
Pardon my node.js newbness in advance, but as I dive in, this project has me very excited (and puzzled at the moment). I'm running into errors when attempting to run monitor-dashboard. So far all is fine when running the monitor part.

Mac OSX 10.9

Quick guesses:
[ ] Is my node.js too new? v0.10.22
[ ] Do I need to run at a higher admin level? "Please try running this command again as root/Administrator."

Warning when installing (Is my node.js too new?):
sudo npm install -g monitor-dashboard

npm http GET https://registry.npmjs.org/monitor-dashboard
npm http 304 https://registry.npmjs.org/monitor-dashboard
npm http GET https://registry.npmjs.org/config
npm http GET https://registry.npmjs.org/backbone-callbacks
npm http GET https://registry.npmjs.org/connect
npm http GET https://registry.npmjs.org/monitor
npm http GET https://registry.npmjs.org/core-monitor
npm http 304 https://registry.npmjs.org/config
npm http 304 https://registry.npmjs.org/backbone-callbacks
npm http 304 https://registry.npmjs.org/core-monitor
npm http 304 https://registry.npmjs.org/monitor
npm http 304 https://registry.npmjs.org/connect
npm WARN engine connect@1.7.3: wanted: {"node":">= 0.4.1 < 0.7.0"} (current: {"node":"v0.10.22","npm":"1.3.14"})
npm http GET https://registry.npmjs.org/underscore
npm http GET https://registry.npmjs.org/backbone
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/qs
npm http 304 https://registry.npmjs.org/backbone
npm http 304 https://registry.npmjs.org/underscore
npm http 304 https://registry.npmjs.org/mime
npm http 304 https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/cron
npm http GET https://registry.npmjs.org/backbone/0.9.9
npm http GET https://registry.npmjs.org/socket.io-client
npm http GET https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/cron
npm http 304 https://registry.npmjs.org/backbone/0.9.9
npm http 304 https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/socket.io-client
npm http GET https://registry.npmjs.org/nodeunit/0.5.2
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/base64id/0.1.0
npm http GET https://registry.npmjs.org/redis/0.7.3
npm http 304 https://registry.npmjs.org/nodeunit/0.5.2
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/base64id/0.1.0
npm http 304 https://registry.npmjs.org/redis/0.7.3
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/nan
npm http GET https://registry.npmjs.org/tinycolor
npm http GET https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/nan
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/tinycolor

> ws@0.4.31 install /usr/local/lib/node_modules/monitor-dashboard/node_modules/monitor/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

monitor-dashboard@0.6.1 /usr/local/lib/node_modules/monitor-dashboard
├── config@0.4.33
├── core-monitor@0.6.1
├── backbone-callbacks@0.1.5 (backbone@0.9.10, underscore@1.4.4)
├── connect@1.7.3 (qs@0.6.5, mime@1.2.11)
└── monitor@0.6.2 (backbone@0.9.9, underscore@1.4.4, cron@0.1.3, socket.io@0.9.16, socket.io-client@0.9.16)

Errors after running npm start monitor-dashboard:

npm ERR! Error: ENOENT, open '/Users/owntheweb/Desktop/node/node_modules/monitor-dashboard/package.json'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Darwin 13.0.0
npm ERR! command "node" "/usr/local/bin/npm" "start" "monitor-dashboard"
npm ERR! cwd /Users/owntheweb/Desktop/node
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! path /Users/owntheweb/Desktop/node/node_modules/monitor-dashboard/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! Error: EACCES, open 'npm-debug.log'
npm ERR!  { [Error: EACCES, open 'npm-debug.log'] errno: 3, code: 'EACCES', path: 'npm-debug.log' }
npm ERR! 
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Darwin 13.0.0
npm ERR! command "node" "/usr/local/bin/npm" "start" "monitor-dashboard"
npm ERR! cwd /Users/owntheweb/Desktop/node
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! path npm-debug.log
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, open 'npm-debug.log'
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/owntheweb/Desktop/node/npm-debug.log
npm ERR! not ok code 0

Log File:

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'start', 'monitor-dashboard' ]
2 info using npm@1.3.14
3 info using node@v0.10.22
4 error Error: ENOENT, open '/Users/owntheweb/Desktop/node/node_modules/moni$
5 error If you need help, you may report this log at:
5 error     <http://github.com/isaacs/npm/issues>
5 error or email it to:
5 error     <npm-@googlegroups.com>
6 error System Darwin 13.0.0
7 error command "node" "/usr/local/bin/npm" "start" "monitor-dashboard"
8 error cwd /Users/owntheweb/Desktop/node
9 error node -v v0.10.22
10 error npm -v 1.3.14
11 error path /Users/owntheweb/Desktop/node/node_modules/monitor-dashboard/p$
12 error code ENOENT
13 error errno 34
14 verbose exit [ 34, true ]

I look forward to any feedback. Thanks for taking a look.

[lorenwest]

There is a fairly well known problem with OSX when installing packages globally. You may be able to get the packages installed globally (using sudo), but if any packages need to write to the filesystem (like monitor-dashboard), they won't have the authority (unless you sudo npm start monitor-dashboard).

Running everything under sudo isn't ideal, so my recommendation is to create a clean directory somewhere, cd to that directory, and install monitor and monitor-dashboard in that directory, using the same steps in the documentation, only omitting the '-g' flag to npm install.

In fact, I think I'll change the documentation to reflect that. There isn't any real reason to install globally other than a little convenience, and if everyone can't do it, it's not that convenient :)

[owntheweb-archive]

How cool is that?! It works!!

Thanks for your lightning fast and detailed response. I was looking for a a great node.js example (and a server monitor for that matter).

I can't wait to dig and learn from your excellent work.