search

tableflip / guvnor

A node process manager that isn't spanners all the way down
MIT License
430 stars 37 forks source link

Picking up wrong node version with node manager "n" #29

Closed jzumbrun closed 9 years ago

jzumbrun commented 9 years ago

I have the node manager "n" to switch to 0.10.36 and boss still throws and error. I console logged the version boss is seeing around line: https://github.com/tableflip/boss/blob/b41d5d53b3f5e97f16a21b9f9f15700ef9bb8af7/lib/local/LocalDaemon.js#L28

and this is the output I get:

[vagrant@localhost raventracking]$ sudo bs start -n raven -a '-s raven' tracking/index.js 
0.10.22 ### this is from the console.log() I added
error: Failed to start /opt/raventracking/tracking/index.js
error:  message=Script tracking/index.js does not exist, code=INVALID ## Also this is not correct. The file is there. I tabbed to get to it so bash definitely sees it.
[vagrant@localhost raventracking]$ node -v
v0.10.36 ## node -v is saying it higher than the required 0.10.29

Any thoughts?

achingbrain commented 9 years ago

What happens if you run:

$ sudo env node -v
jzumbrun commented 9 years ago

Guess my sudo env is on a different version:

[vagrant@localhost raventracking]$ sudo env node -v
v0.10.22
[vagrant@localhost raventracking]$ node -v
v0.10.36
achingbrain commented 9 years ago

Try becoming root and use n to set the node version available for root or failing that, upgrade the system version to something above 0.10.29.

jzumbrun commented 9 years ago

I got it to work outside of vagrant. Vagrant was just giving me issues.