Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31206

SystemD services depending on mongod will be started before mongo is ready to take connections

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Packaging
    • Environment:
      Centos 7
    • ALL
    • Hide

      Make a systemD script that is set to start after mongod.
      When the service is started, mongo won't be ready yet to take connections, causing the service to fail if it depends on that.

      Show
      Make a systemD script that is set to start after mongod. When the service is started, mongo won't be ready yet to take connections, causing the service to fail if it depends on that.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      I have the following systemD script for my software:

      [Unit]
Description=LynxChan
After=mongod.service
Wants=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.

            Assignee:
            mark.agarunov Mark Agarunov (Inactive)
            Reporter:
            stephenlynx Stephen Lynx
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: