[SERVER-18085] Database doesnt start if you change init config to YAML Created: 16/Apr/15 Updated: 30/Apr/15 Resolved: 30/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | 3.0.0, 3.0.1, 3.0.2 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Mall Johnson | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian Wheezy (up to date), |
||
| Attachments: |
|
| Participants: |
| Description |
|
Hello, in the /etc/init.d/mongod script under Debian is a "CONF" variable which points to the "/etc/mongod.conf" standard config. If you change the path to your own YAML config, so your config is used at every startup, MongoDB is not able to start. It breaks simply with "mongod failed!", no error is logged. This is very annoying because when you want to use wiredTiger it is only possible when you use the YAML format. When you start the database with "mongd --config /path/toyour/YAMLconfig" it runs smoothly but not if you change the CONF variable in the Debian init script. I add my YAML config as Attachment. Thanks for your attention |
| Comments |
| Comment by Ramon Fernandez Marina [ 30/Apr/15 ] |
|
No worries tigereye88, glad to hear your problem is solved. Thanks for using MongoDB. Regards, |
| Comment by Mall Johnson [ 30/Apr/15 ] |
|
Hello Mr. Kleinman and thank you for your time and Help, i have made a very big mistake, the permissions of my created wiredtiger database folder was wrong, thanks to your comment i detected the error. The YAML config works perfectly now. I want to apologize for stealing your time and made a wrong issue. Maybe you can delete this Issue now?!. Thank you and sorry for the mistake |
| Comment by Sam Kleinman (Inactive) [ 29/Apr/15 ] |
|
Hello, It's possible, even preferable, to replace the legacy content of /etc/mongod.conf with the new YAML content. As part of I attempted to reproduce this using 3.0.2 and the new default config above using your method of editing the /etc/init.d/mongod script, and mongod used the alternate config. If you're still experiencing this problem, could you:
Cheers, |