-
-
Notifications
You must be signed in to change notification settings - Fork 982
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
Seeing 'Bugsnag: Error: spawn ENOENT' #23
Comments
Oh and also, this is against Node v0.10.36 on CentOS 6.6 |
Have you got ansible installed? |
actually resolved it...turns out git wasn't installed on system and this error was due to that...this link helped a lot to resolve: http://stackoverflow.com/questions/27688804/how-do-i-debug-error-spawn-enoent-on-node-js To fully resolve this, I'd still recommend adding a 'Requirements' section to README.md that includes git, mongodb, redis, etc, but it's up to you :) Cheers! |
Ok On Tue, May 26, 2015 at 8:23 am, Vivek Ayer notifications@github.com wrote: To fully resolve this, I'd still recommend adding a 'Requirements' section to Cheers! — |
At version e8ce2a7, seeing the following error after starting semaphore as 'nodemon bin/semaphore'
app.js:110 Semaphore listening on port 50000
../node_modules/bugsnag/lib/logger.js:29 Bugsnag: Error: spawn ENOENT
at errnoException (child_process.js:1011:11)
at Process.ChildProcess._handle.onexit (child_process.js:802:34)
This is probably not an issue, but need help debugging this. I don't know where to start.
The text was updated successfully, but these errors were encountered: