Open pg1671 opened 10 years ago
this sounds quite a bit like my experience with the cluster that is #262. @pg1671 could you check that and let me know if you're seeing similar symptoms? It's a serious bug on multiple levels, and if this is the same issue it'll double my priority for fixing it.
I am running the following on a vagrant box running ubuntu 12.04 and when i change to 0.16.1 from 0.16.0 the mongodb service is "stopped/waiting" when the provision is finished. Under 0.16.0 it is running. There are no other changes other than changing the recipe to 0.16.1.
The major difference is the mongodb version changes from 2.4.10 to 2.6.1 due to the new repo.
I have also found there is a running mongod service when I use 0.16.1 but this does exist when I use 0.16.0.
The recipe is simply:
It is also running the apt recipe before in the run_list.
I know I can change the repo in 0.16.1 to mongodb_org_repo and I have tried that (and it makes no difference).
The logs in /var/log/mongodb show it starting an instance .. but not using the directory path I told it to .. seems to be defaults. Cannot see any separate logs for the mongodb upstart service.