[SERVER-25748] mongod fails to start with the default systemd service file Created: 23/Aug/16 Updated: 28/Sep/16 Resolved: 28/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Emil Burzo | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | 1. install mongod 3.2 on ubuntu xenial (16.04) |
||||||||
| Participants: | |||||||||
| Description |
|
Using the default systemd service file, either from the deb package or from the documentation[1] results in a fatal assertion (attached log). However, adding the following in the systemd service file, under [Service]: Type=forking makes it start up without any issues. I'm guessing it should be added by default? [1] - https://docs.mongodb.com/master/tutorial/install-mongodb-on-ubuntu/ |
| Comments |
| Comment by Kelsey Schubert [ 28/Sep/16 ] | |||||||||
|
Hi emilburzo, Unfortunately, there isn't a good way to log this mismatch. However, on startup we do display the options:
Additionally, there is a docs ticket that was recently opened, Kind regards, | |||||||||
| Comment by Emil Burzo [ 15/Sep/16 ] | |||||||||
|
Good catch, I had the following left over in the config file from previous versions:
Is there any way to signal this to the user in the log file? | |||||||||
| Comment by Kelsey Schubert [ 14/Sep/16 ] | |||||||||
|
Hi emilburzo, Unfortunately, I haven't been able to reproduce the issue that you describe. So we can continue to investigate, would you please provide your MongoDB configuration file? Thank you, | |||||||||
| Comment by Drew Burden [ 31/Aug/16 ] | |||||||||
|
I realize this is specifically for 3.2, but I would just like to mention that we are running MongoDB 3.0.5 via systemd without the Type line, and we have not experienced this issue. |