Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
3.4.2
-
Centos 7.
-
ALL
-
Description
I have the following systemD script for my software:
[Unit]
|
Description=LynxChan
|
After=mongod.service
|
|
|
[Service]
|
ExecStart=/usr/bin/lynxchan
|
User=node
|
StandardOutput=syslog
|
Restart=on-abort
|
|
|
[Install]
|
WantedBy=multi-user.target
|
See "After=mongod.service". Because of that, my software expects mongo to be ready to take connections when it is booted by this init script.
However, for 3.4, mongo is not ready yet to take connections when my software runs.
I just tested with 3.2 and everything works as expected, my service is always able to connect to mongo when the system boots.
Attachments
Issue Links
- is related to
-
SERVER-31206 SystemD services depending on mongod will be started before mongo is ready to take connections
-
- Closed
-