Still getting lots of DtraceProviderBindings errors on OS X #216
Comments
|
Can you gist a full 'npm install' run? Do you get that error when just doing |
|
I was getting this error too and it turned out to be a configuration issue after updating to OS X Yosemite. I installed the Xcode command line tools but never accepted the user agreement in Xcode. Argh :) If you are getting this error you may see the following when running "npm install bunyan": Setting the "V" environment variable will give you more info as to why npm failed to install bunyan: After opening Xcode on my mac and accepting the user agreement it fixed my problem. I can now successfully use bunyan on OS X Yosemite. |
|
interestingly enough, I don't seem to be getting any build errors. Here's my verbose output: |
|
Problem occurs when we use iojs. |
|
@neoziro there is a known issue with the dtrace-provider with io.js that is reported in issue #212. @howarddierking I'm not sure about the error you're getting. Do you have the latest version of xcode installed? I have bunyan working on my mac with OS X Yosemite: Xcode version 6.1.1 (6A2008a) |
|
@gregjopa ok, will use node for now |
|
Using node 0.11 it show this. Same issue? |
|
@neoziro The issue with io.js is fixed with latest. The fix was to update to dtrace-provider 0.4.0. |
|
@kievechua With the latest bunyan (using dtrace-provider 0.4.0) you shouldn't be getting that. I'd need more details (bunyan version, node version, your platform details, etc.) to confirm. |
|
@howarddierking Can you first try with bunyan 1.3.3 that updates to dtrace-provider 0.4.0? Then, does this work: |
|
Still getting the error, but investigating to see if there may be something else going on, because I'm not seeing it in a different project. Will update as I discover more, but here's my verbose output. |
|
ok - found that the issue in my case was related to using https://github.com/felixge/node-sandboxed-module. When you use sandboxed-module to require a module that has a downstream dependency on Bunyan, sandboxed-module tries to recursively create fakes for all of the descendent modules - and whatever it happens to create for Bunyan doesn't have the proper Dtrace binding dependency. At any rate, I've corrected the issue by switching my approach for plugging in the fakes. |
|
@howarddierking Thanks for getting back on this! AFAIK the issue here is fixed. Happy for new issues or re-opening if someone has repro details for a failure case. |
|
This is still an issue if you have certain characters in your path on OSX: |
|
I'm on Mac OSX 10.9.5, XCode 6.2, NodeJS 4.1.2 and I get this: (user name and project names changed - everything else is the same) |
|
$ npm install hexo --no-optional ChenJohns-MacBook-Air:hexo JohnChen$ hexo --version |
|
My error seems to be related to dtrace compiling and node-gyp.js dtrace-provider@0.6.0 install /Users/Ben/caredox/caredox_util/node_modules/bunyan/node_modules/dtrace-provider
LD_LIBRARY_PATH=/Users/Ben/caredox/caredox_util/node_modules/bunyan/node_modules/dtrace-provider/build/Release/lib.host:/Users/Ben/caredox/caredox_util/node_modules/bunyan/node_modules/dtrace-provider/build/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../.; sh libusdt-build.sh |
|
My issue was not properly installed |
|
For me this was fixed by upgrading my npm. I'm on OS X EL Capitan and went from npm version 1.4.28 to 3.4.0 and the problem went away. (Node.JS version 5.0.0) |
|
rm the node-modules dir and npm install |
|
Same issue here. OS X El Capitan |
|
Same as @andyburke, bunyan fails if you have parens in the path you attempt to run npm install from. In my case it was /Dropbox (Personal)/. I moved it to a root dir, re-ran install and it worked fine. |
|
I'm having a similar problem, although I don't get compiler errors I do get some warnings: OS X El Capitan (10.11.2) I see this when installing bunyan: |
|
It is Feb 2016, is this still the same? I am getting the same error. |
|
Same error here with npm 3.5.3 and node 5.5.0 |
|
Same error with node 4.3.0 and npm 3.7.1... |
|
fwiw, pino, a bunyan-inspired alternative, does not have this issue. Pino facts:
If you need the Dtrace fanciness, then def. stick with bunyan. If you're running into this issue over and over, and don't need the Dtrace fanciness, then it might be that bunyan isn't the best logger for your use case. |
|
What @melloc said in #216 (comment) about likely being the result of a failure to build the binary part of dtrace-provider when that module was installed. Then when bunyan.js does However, that doesn't quite match up with the quoted errors from this comment: #216 (comment) where we see: I.e. we see warnings from the "Release", then "default", then "Release", then "default". Given the code has: It feels like we are succeeding to import a debug build at "./build/Debug/DTraceProviderBindings" and also that we are requiring dtrace-provider from two different places. Some thoughts:
|
|
In my case, the problem was python 3.5. Using the --python option to point to python 2.7 solves the issue. |
|
One more case of Python 3.5 on macOS Sierra. Required python version is 2.7 solved my issue |
|
OP doesn't care so I'm unsubscribing |
|
I still have the terrible error. |
|
What ended up working for me was:
Not sure why I had to do this though. |
|
Getting a similar issue here and adding @protomock your work around doesn't work for me. 😞 Error logLooks like yarn doesn't work with |
|
I'm getting this same issue with node@8.0.0 and yarn@0.24.6. I tried to remove my |
|
+1 $python --version
Python 2.7.10
GNWRALA2063193:demo 430014695
$node -v
v6.11.0
GNWRALA2063193:demo 430014695
$npm -v
3.10.10 |
|
|
I know this is an old issue but I wanted to comment on it in case anyone else has the same issue I had. My issue was caused by having parentheses in my path. Moving the project to a path without the parens worked for me. |
|
@karlgroves That's a bug in |
|
I was able to resolve this by downloading python 2.7.12 with pyenv by running
and then |
|
What worked for me was to re-install Then these |
|
My solution was |
|
amazing！:sunglasses: rm -rf node_modules/ && npm install --no-optional works for me！ cool! |
|
Hi, I think this is the version of node js that causes this issue. I met this issue after I updated my node from Here is my solution in my Firstly I'm using nvm to manage the version of node.js. Under the version Then I took the solution of @felipekm ,
|
|
As of There is a list of common failure reasons in dtrace-provider's README. Please take a look there, throughout this ticket, and at #525 first before opening any bugs. |
This worked for me. |
and others
I know that this issue has been discussed at great length in the past, and I revisited some of those issues/discussions before posting this. I'm not sure if I'm just not reading the previous resolutions correctly or if something else is going on, but I'm still getting a bunch of this error when running mocha tests for my code that's using buyan:
I'm running OS X Yosemite.
Any ideas on getting rid of this message? It's not the end of the world, but it's pretty annoying and, more importantly, it's slowing down my test runs.
thanks,
_howard
The text was updated successfully, but these errors were encountered: