When starting mongod as a systemd service, the process forks before mongod has opened the socket and starts listening for connections. This can cause dependent services to fail to start, as systemd considers mongod started once the process has forked.
- causes
-
SERVER-33319 Systemd startup should not always be "forking".
- Closed
- is duplicated by
-
SERVER-31206 SystemD services depending on mongod will be started before mongo is ready to take connections
- Closed
- is related to
-
SERVER-16292 mongod isn't ready for connections when it finishes a fork
- Closed