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

Restify not working with nodejs v4.0.0 in mac os x #897

Closed
joaosousafranco opened this issue Sep 9, 2015 · 23 comments
Closed

Restify not working with nodejs v4.0.0 in mac os x #897

joaosousafranco opened this issue Sep 9, 2015 · 23 comments

Comments

@joaosousafranco
Copy link

Hello,

i was trying my application that is using restify with nodejs v4.0.0, and it is not working. Once the require to restify is made the process just dies without giving any exception or error.

Thank you,
Joao Franco

@micahr
Copy link
Member

micahr commented Sep 9, 2015

@MrShogun can you provide an example script that exhibits the problem? Anything we can go off of to help assist you?

@pete-a
Copy link

pete-a commented Sep 9, 2015

I am also experiencing this, restify will not install. Looks to be an issue with DTrace 0.5:
OS X 10.10.5
Node v4.0.0

Installing restify

$ npm install restify --save
> dtrace-provider@0.5.0 install     
/Users/.../node_modules/restify/node_modules/dtrace-provider
> node scripts/install.js

---------------
Building dtrace-provider failed with exit code 1 and signal 0
re-run install with environment variable V set to see the build output
---------------
...

Basic script

/* index.js */
var restify = require('restify')
var server = restify.createServer()
server.get('/hello_wold', (request, response, next) => {
  response.send('Hello World')
  next() 
}) 
server.listen(8080)

Output

$ node index.js 
{ [Error: Cannot find module './build/Release/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }
{ [Error: Cannot find module './build/default/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }
{ [Error: Cannot find module './build/Debug/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }

@micahr
Copy link
Member

micahr commented Sep 9, 2015

Dtrace 0.5 won't work with Node 4. Node 4 was just released today, and we haven't had a chance to validate what is necessary to get it working with Restify.

@thomashilzendegen
Copy link

dtrace 0.6 has node v4 support, maybe updating is enough?

@thomashilzendegen
Copy link

@MrShogun just run in the node_modules/restify directory the following to test if 0.6 is a possible fix:

npm i dtrace-provider@0.6.0

@19h
Copy link

19h commented Sep 9, 2015

@thomashilzendegen It is indeed a fix.

@joaosousafranco
Copy link
Author

Ill try that asap, in the mean time do you have an ETA for the fix in restify? Im using the latest version and i dont have any problem with updating, so once you will release a fix ill update on my side.

Thank you

@micahr
Copy link
Member

micahr commented Sep 9, 2015

4.0.1 is out, upgrade and let us know if that fixes your issue.

@pete-a
Copy link

pete-a commented Sep 10, 2015

4.0.1 now installs successfully with Node 4.0.0 for me 👍

@micahr micahr closed this as completed Sep 10, 2015
@lvegerano
Copy link

This issue still happening. I'm using restify v4.0.3 using either node 0.10.40 or 4.2.2.

{ [Error: Cannot find module './build/Release/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }
{ [Error: Cannot find module './build/default/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }
{ [Error: Cannot find module './build/Debug/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }

@cprwhite
Copy link

cprwhite commented Dec 5, 2015

I'm have this problem too using testify v4.0.3 and node 4.2.3

{ [Error: Cannot find module './build/Release/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }
{ [Error: Cannot find module './build/default/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }
{ [Error: Cannot find module './build/Debug/DTraceProviderBindings'] code: 'MODULE_NOT_FOUND' }

@willkramer
Copy link

@cprwhite @lvegerano have you tried uninstalling the restify module and re-installing it?

I had the same error this morning after upgrading to node v4.2.3 on my Mac and running a npm update doesn't seem to fix the issue.

The commands I ran were:

npm uninstall restify
npm install restify

@lvegerano
Copy link

@willkramer I did not spend much time on it. I was on a mission to create a microservice so I just switched to using HapiJS. Also there is memory leak noted in the issues with some of the middleware that also pushed me away.

@micahr
Copy link
Member

micahr commented Dec 16, 2015

@lvegerano - Do you mind pointing me towards the issues with memory leaks?

It makes sense that after upgrading Node you'd have to uninstall and reinstall a module with a dependency on a native module (Bunyan / dtrace-provider) as it needs to be recompiled with the newer version of node-gyp.

@lvegerano
Copy link

@micahr I did not find this leak. I was making reference to #431 While it may not be an issue at the moment, the inconclusiveness of the issue deterred me from using restify.

@DonutEspresso
Copy link
Member

The error is from bunyan, and is non-fatal. You may want to check out this thread for some of the proposed solutions.

@markmcdermid
Copy link

I came across this issue too but a simple reinstall fixed it, cheers.

@u84six
Copy link

u84six commented Nov 14, 2017

This seems to be happening again with Restify 6.3.2 and Node 9.0.0. Is this because you haven't had a chance to update?

@retrohacker
Copy link
Member

Hey @u84six,

Thanks for letting us know. Is this specifically DTrace?

@retrohacker retrohacker reopened this Nov 14, 2017
@u84six
Copy link

u84six commented Nov 14, 2017

Yes, specifically DTrace. I confirmed it was restify installation by uninstalling, deleting node_modules dir and then running npm install. No problem without restify.

@retrohacker
Copy link
Member

DTrace uses native bindings, it must not be updated for Node v9. Not sure what work goes into that. Marking this as help wanted for now.

Worst case scenario we could pull out dtrace, I'm not sure how much it is used (queue incoming flood of use cases)

@stale
Copy link

stale bot commented Apr 10, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Apr 10, 2018
@stale
Copy link

stale bot commented Apr 24, 2018

This issue has been automatically closed as stale because it has not had recent activity.

@stale stale bot closed this as completed Apr 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests