[SERVER-2776] Duplicate (but identical) option in config file causes server to fail to start with no clue as to why Created: 17/Mar/11 Updated: 30/Jun/17 Resolved: 30/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 1.8.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Roger Binns | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 10.10 AMD64 10gen stable build |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Due to a bug in a shell script that tries to ensure journalling is on (I wish you had made that the default for the packaged builds) I ended up with the option twice. Ie my /etc/mongodb.conf ended with journal = true If you try to start the server "service mongodb start" then it will say started successfully and give a pid. However a ps will show no process. There is also absolutely nothing in /var/log/mongodb/mongodb.log or in any other logfile in /var/log. Trying to find out why the server didn't start was rather difficult. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 30/Jun/17 ] |
|
Fixed since we improved server fork startup such that errors on startup are propagated back. |