Keystone-classic: Failed to load c++ bson extension

Created on 28 Jan 2015 · 23Comments · Source: keystonejs/keystone-classic

tried following a yo generator install of keystone but getting this error

$ node keystone
{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version

I only get the server running when I stop and restart the terminal - any thoughts on removing the error

Source

sononix

Most helpful comment

Just upgraded to the master branch, the error is gone.

In package.json:

"keystone": "https://github.com/keystonejs/keystone.git",

Then

rm -rf node_modules
npm install

fridays on 2 Dec 2015

👍4

All 23 comments

@sononix, can you provide additional specifics:

OS (I ask because I've encountered this issue on OSX when command developer tools are no available)
Keystone version
Node.js version
Anything else you think might be relevant

estilles on 28 Jan 2015

OS 10.10.1
keystone 0.2.42

Developer tools are installed
Mongodb - v2.6.7
GNU Make 3.81
gcc version 4.9.2 (Homebrew gcc 4.9.2_1)

mongodb installed using brew - I think only way I could get it to work
node was using version v0.10.32 - updated to v0.10.36 using nvm for management

that about it that I can think of

sononix on 29 Jan 2015

I haven't been able to replicate your issue, so unfortunately I don't have a definitive solution for you. However, I have encountered this issue in the past on more than one occasion. One time was related to the lack of developer tools on OS X (clearly not your case). Another time it was caused by some dependencies not properly installed (probably due to install errors I didn't notice). Something you can try is to reinstall all the app's dependencies. I'm not sure if you've tried this already, but it worked for me (at least once) the past.

cd /path/to/your/app
npm cache clean
rm -rf node_modules
npm install

NOTE: You may need to use sudo to run the above commands.

estilles on 30 Jan 2015

I have this issue too.

OS: Window 8.1
MongoDB: 3.0.1
Keystone: 0.3.2
Nodejs: 0.12.0

SLyHuy on 21 Mar 2015

When remove node_modules and install again. I have some alert:

npm ERR! git clone git://github.com/michaelficarra/cscodegen.git undefined
npm ERR! git clone git://github.com/michaelficarra/cscodegen.git undefined
npm WARN optional dep failed, continuing cscodegen@git://github.com/michaelficar

npm WARN `git config --get remote.origin.url` returned wrong result (git://githu
b.com/michaelficarra/cscodegen.git) undefined
npm WARN `git config --get remote.origin.url` returned wrong result (git://githu
b.com/michaelficarra/cscodegen.git) undefined
npm ERR! git clone git://github.com/michaelficarra/cscodegen.git undefined
npm ERR! git clone git://github.com/michaelficarra/cscodegen.git undefined
npm WARN optional dep failed, continuing cscodegen@git://github.com/michaelficar
ra/cscodegen.git#73fd7202ac086c26f18c9d56f025b18b3c6f5383
\

And this issue still happen.

SLyHuy on 21 Mar 2015

I m having the same issue.

$ node keystone
{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version

This is always there before server starts.

naeemshaikh27 on 23 Apr 2015

issue exists even after

cd /path/to/your/app
npm cache clean
rm -rf node_modules
npm install

And the OS is windows-7,8

naeemshaikh27 on 23 Apr 2015

I think because Window OS dont have js-bson then they run pure JS. It is not big problem, because everything is fine. After I publish the code to online server using CentOS, this Error will no longer.

SLyHuy on 23 Apr 2015

OK.. Thanks for reply. But there is another window 7 on which the code runs fine without the warning..

naeemshaikh27 on 23 Apr 2015

I have the same issue both in Windows 7 and CentOS 7. This started happening in one of the 3.x versions as I had not seen it before. In CentOS 7 I get:

processing: /src/keystone.js

2015-04-24 00:29:57,526 INFO success: node entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-04-24 00:29:57,881 DEBG 'node' stdout output:
{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }

2015-04-24 00:29:57,881 DEBG 'node' stderr output:
js-bson: Failed to load c++ bson extension, using pure JS version

Now this CentOS is a VM running in a windows host; not sure if windows' still the culprit as @SLyHuy doesn't see it in his CentOS deployment.

webteckie on 24 Apr 2015

This error originates from your MongoDB installation. This SO answer should help:
http://stackoverflow.com/a/22054632

snowkeeper on 24 Apr 2015

I had the same problem, it was because of the python version, i had to specify the version:

npm cache clean
rm -rf node_modules
export PYTHON=python2.7
npm install --python=python2.7

rafaelndev on 24 Apr 2015

Same problem here, the SO answer did not help

OSX 10.11.1
Mongo 3.0.7
Node 5.0.0

It seems that the error comes some keystone (sub?)dependencies relying on outdated libraries. I only got here so far and it is quite annoying as it works great on Ubuntu 14.04 with a similar setup

kartsims on 20 Nov 2015

Same problem here
OSX 10.11.1
Mongo 3.0.7
Node 4.2.1

Kimpo79 on 25 Nov 2015

Same here

OSX 10.11.1
Mongo 3.0.7
Node 5.0.0

fridays on 1 Dec 2015

Just because it hasn't already been mentioned here - this is a warning, not an error. I've just been ignoring it.

udp on 1 Dec 2015

And it happens on Ubuntu 14.04 LTS too

ignlg on 1 Dec 2015

Just upgraded to the master branch, the error is gone.

In package.json:

"keystone": "https://github.com/keystonejs/keystone.git",

Then

rm -rf node_modules
npm install

fridays on 2 Dec 2015

👍4

As @snowkeeper alluded, for Node 4 at least, this error is entirely upstream. It originates in the bson package itself, which the mongodb package depends on, which mongoose depends on. The error was corrected right around [email protected].

@fridays's suggestion to use the unstable Keystone 0.4.x alpha branch from master eliminates the error as the mongoose dependency was updated, resulting in a bson 4 dependency.

If Keystone 0.3.x is to be maintained, the solution is to bump the mongoose dependency from ~3.8.35 to ^4.1.3. There are backwards incompatible changes between Mongoose 3 and 4 - so Keystone updates might have to be backported from 0.4.x, or applied separately if 0.4.x is largely incompatible.

All of that said, since a pure JS fallback is available for bson and this error does not impede execution, I can't imagine that this issue should take much priority!