Install fails on Linux (v8tools or node/npm versions possibly)

[jamiefolsom]

Courtesy of @rsimon:

gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:784:12)
gyp ERR! System Linux 3.2.0-40-generic
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/v8tools
gyp ERR! node -v v0.10.4
gyp ERR! node-gyp -v v0.9.5
gyp ERR! not ok 
npm ERR! v8tools@0.2.1 install: `node-gyp rebuild`
npm ERR! `sh "-c" "node-gyp rebuild"` failed with 1
npm ERR! 
npm ERR! Failed at the v8tools@0.2.1 install script.
npm ERR! This is most likely a problem with the v8tools package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls v8tools
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.2.0-40-generic
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store
npm ERR! node -v v0.10.4
npm ERR! npm -v 1.2.18
npm ERR! code ELIFECYCLE

[jamiefolsom]

@rsimon I am going to do a fresh install to be sure this works on my system; meantime, have a look at https://github.com/hyperstudio/MIT-Annotation-Data-Store/blob/master/package.json, which indicates versions of all dependencies; NPM should handle resolution of these things for you, but I do see different versions indicated in your log output.

[rsimon]

Thx! On my end, I'll try stepping back to node 0.8.19 & npm 1.2.10 (as listed in package.json) and see how it goes.

Cheers,
Rainer

[rsimon]

Ok, now at verssion 0.8.19/1.2.10 and I seem to get one step further. npm install completes properly as far as I can tell with my next-to-zero node.js knowledge. Console output ends with this:

 less-middleware@0.1.6 node_modules/less-middleware
 ├── mkdirp@0.3.5
 └── less@1.3.3 (ycssmin@1.0.1)

 express@3.1.0 node_modules/express
 ├── methods@0.0.1
 ├── fresh@0.1.0
 ├── range-parser@0.0.4
 ├── cookie-signature@0.0.1
 ├── buffer-crc32@0.1.1
 ├── cookie@0.0.5
 ├── debug@0.7.2
 ├── commander@0.6.1
 ├── mkdirp@0.3.3
 ├── send@0.1.0 (mime@1.2.6)
 └── connect@2.7.2 (pause@0.0.1, bytes@0.1.0, formidable@1.0.11, qs@0.5.1)

 v8tools@0.2.1 node_modules/v8tools
 └── bindings@1.1.0

 mongoose@3.5.7 node_modules/mongoose
 ├── sliced@0.0.3
 ├── muri@0.3.1
 ├── hooks@0.2.1
 ├── ms@0.1.0
 └── mongodb@1.2.13 (bson@0.1.8)

 timekit@0.1.9 node_modules/timekit
 └── bindings@1.1.0

 nodetime@0.8.10 node_modules/nodetime
 ├── request@2.12.0
 └── nodetime-native@0.1.0 (bindings@1.1.0)

But then foreman start terminates with an exception:

 09:20:31 web.1  | /home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schema/string.js:198
 09:20:31 web.1  |   throw new CastError('string', value, this.path);
 09:20:31 web.1  |         ^
 09:20:31 web.1  | CastError: Cast to string failed for value "undefined" at path "annotator_schema_version"
 09:20:31 web.1  |     at SchemaString.cast (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schema/string.js:198:9)
 09:20:31 web.1  |     at SchemaString.SchemaType.default (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schematype.js:87:14)
 09:20:31 web.1  |     at SchemaString.SchemaType (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schematype.js:36:13)
 09:20:31 web.1  |     at new SchemaString (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schema/string.js:21:14)
 09:20:31 web.1  |     at Function.Schema.interpretAsType (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schema.js:351:10)
 09:20:31 web.1  |     at Schema.path (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schema.js:289:29)
 09:20:31 web.1  |     at Schema.add (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schema.js:204:12)
 09:20:31 web.1  |     at new Schema (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/node_modules/mongoose/lib/schema.js:70:10)
 09:20:31 web.1  |     at Object.<anonymous> (/home/simonr/Workspaces/hyperstudio/MIT-Annotation-Data-Store/web.js:44:18)
 09:20:31 web.1  |     at Module._compile (module.js:449:26)
 09:20:31 web.1  | exited with code 1
 09:20:31 system | sending SIGTERM to all processes

PS: I'm on Ubuntu 12.04 OS, BTW.

[jamiefolsom]

OK, great to hear it now installs properly. So what's odd about this is that I would expect NPM to install the versions you need based on the package.json. Clearly that didn't happen. You had to install them manually, correct?

As for the issue you're now seeing, that's due to an omission on my part: you need to have a .env configuration file in the root, which is excluded from source control because it contains specific information for your system.

I will add a sample to the repo, which you can customize for your purposes.

Actually, that raises another omission -- you have to have mongodb installed and running (and your config set to connect to an existing database). Here's a link to the relevant instructions, which I will also add to my docs:

http://docs.mongodb.org/manual/installation/

Thanks for being the guinea pig!

[rsimon]

I needed to install the exact correct version of Node (not the most recent one). The rest seemed to go just fine (npm version, plus the version of build dependencies).

Ok cool, so the .env file is likely the last remaining hurdle; MongoDB is running on my system already.

 <Thanks for being the guinea pig!>

The pleasure is all mine ;-)

[jamiefolsom]

Hi @rsimon check out this sample.env (copy to .env, and update with your specifics): https://github.com/hyperstudio/MIT-Annotation-Data-Store/blob/master/sample.env

[rsimon]

Woohoo! Works like a charm! I'll need to dig out that old dummy login portal/token generator app I wrote a while ago & then I should be ready to go. I'll keep you posted! Thx a lot!

[jamiefolsom]

Great! Yes, I suspect that JWT business will trip folks up who aren't familiar with it, or the SOA architecture the Annotator uses. Actually, if your dummy app is public, I would point to it from my docs to help explain. And/or, we have a token generator in our Annotation Studio as well of course if you want to be a guinea pig on that too ;-) Ruby/Rails/PostgreSQL, etc... Thanks so much for working through this! I will have more to report on the Annotorious OKFN plugin soon too.

[jamiefolsom]

Closing, thanks to @rsimon for identifying holes in the docs, and a missing .env file required by foreman.

[mwidner]

I had to update package.json to use v8tools v0.2.2 (instead of v0.2.1), then install worked. This is on Ubuntu server 13.04

[jamiefolsom]

Noted!

On Monday, July 1, 2013, Michael Widner wrote:

I had to update package.json to use v8tools v0.2.2 (instead of v0.2.1),
then install worked. This is on Ubuntu server 13.04

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-20301686
.