-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.11, 3.4.12, 3.4.13
-
Component/s: Packaging
-
None
-
ALL
-
-
Build 2018-03-12, Build 2018-03-26
In ticket SERVER-31225 it is suggested that mongo should be set to "type=forking" and this has been applied globally to all mongo deployments. However, it is not impossible that in your /etc/mongod.conf you can have :
processManagement:
fork: false
And then your server starts and after a while systemd notices it hasn't forked and kills it.
I think startup=simple (or leave it to default) should be the default in the release and if people want to customise their own startup type, the RPM package should not overwrite customised systemd scripts.
- is caused by
-
SERVER-31225 The mongod process forks before listening for connections
- Closed
- related to
-
SERVER-33320 Changes to systemd script but no reload of unit files
- Closed