PS: I did do a couple of meteor reset and meteor update and npm install to make all this go away , but i think finally it was the meteor + mongodb combination that worked and guess i will live with it for the time being till i can figure out a way to combine the two automatically. Some have suggested a restart will help iron out this issue. Will try that too and post back.
I’m getting the same issue from time to time and have been employing the same workaround. Hope it doesn’t happen in production because I’m not sure meteor reset is something I can or want to be doing on a production server.
@rafialikhan Thank you so much, this helped me to run meteor projects again. But I still can’t understand what or how did I cause this. Before I faced this issue I have made three small projects. Now when I want to run them, I have to manually start mongo db in one console, and run meteor in another. But if I create new project, I don’t have to run db myself, everything goes as before the issue. What do you think can cause this?
Thanks again for this post!!
@brascene, @ermiasseife52 : if you have installed MongoDB separately from Meteor and/or set the MONGO_URL environment variable, you are telling Meteor to use the MongoDB instance you have installed. Meteor does not try to start this because it’s assumed to have been started beforehand (in Windows this would typically be an automatically started service) . Note the point about Meteor assuming a running MongoDB instance: if you don’t have that, your application will start, but will fail the first time the app tries to use the database.
If you don’t specify a MONGO_URL, Meteor tries to run a local (to this project) instance of MongoDB for you. This runs on your Meteor port + 1 (so frequently on port 3001) to avoid conflict with any other MongoDB instance available to you.
same here >> i will try the mongodb solution as described above and tell the forum what happened.
none of my app is working even new test app with meteor create test_app
All sticking at STARTING YOUR APP.
Hum, I had this issue with Meteor 1.5. Worked again after meteor update:
First failed:
$ meteor --settings settings.json
[[[[[ ~/Documents/repos/app ]]]]]
=> Started proxy.
[HMR] Dev server listening on port 3003
^C
Then update:
$ meteor update
This project is already at Meteor 1.5, the latest release.
Changes to your project's package version selections from updating package versions:
babel-compiler upgraded from 6.19.1 to 6.19.2
dynamic-import upgraded from 0.1.0 to 0.1.1
ecmascript-runtime-client upgraded from 0.4.1 to 0.4.2
email upgraded from 1.2.1 to 1.2.3
minimongo upgraded from 1.2.0 to 1.2.1
modules upgraded from 0.9.0 to 0.9.1
Started working:
$ meteor --settings settings.json
[[[[[ ~/Documents/repos/app ]]]]]
=> Started proxy.
=> Started MongoDB.
[HMR] Dev server listening on port 3003
=> Started your app.
=> App running at: http://localhost:3000/
Its interesting it didn’t seem to start mongo before I updated.