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
Deployd doesn't work with NodeJS v0.12 #529
Comments
Any stack trace after Make sure 'mongod' is in your $PATH ? |
Nope, no stacktrace after Make sure 'mongod' is in your $PATH I did dig around a bit -- as I said I ran mongod from terminal pointing to deployd db folders and mongodb started up ok. e.g. the following worked OK and mongodb fired up.
Just deployd wouldn't start. |
title is misleading, could You change it please? |
How is it misleading? Deployd does not work since it can't make requests from mongodb. If you want a new title, please suggest. Thx |
Isn't DPD mongo portable instance jest not working? I mean that saying: "Airconditioning is broken, so car doesn't work" is not actually a truth. |
Do you use DPD without a DB? Personally I do not. No saves or reads from DB. To use your analogy, a part of the engine is broken so the car won't drive. |
I tought that DPD commandline mongo doesnt work |
Actually, as I know, deployd unit test fail in node v0.12 and iojs. But I am running my production deployd server with iojs. I have a server.js instead of "dpd -d" Actually, I think dpd -d is not a good for long running. I suggest everyone should have their server.js and treat deployd as an library. |
I use openshift hosting so im also using server.js. Also a side note: I tried benchmarking deployd api with Apache Benchmark and dpd -d fails/crashes because of too big overload. Normal instance of DB + server.js runs fine. |
You saw this error string with server.js ?? |
#577 fixes unit tests on node 0.12 |
fixed with #577 |
Hi,
Just got a new macbook and thought I would upgrade my Node version in the process.
Using Node v0.12, when I start deployd I get the infamous mongod error e.g. Make sure 'mongod' is in your $PATH
However, mongod is def in $PATH as I can >mongod in terminal successfully, and even start the mongod instance passing data folder as argument.
Downgrading node to v0.10.32 (which is what I was running initially) fixed the issue.
The text was updated successfully, but these errors were encountered: