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

Changes to systemd script but no reload of unit files

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 3.7.4
    • Affects Version/s: 3.4.11, 3.4.12, 3.4.13
    • Component/s: None
    • None
    • Fully Compatible
    • Linux
    • v3.6
    • Hide

      Install a version of mongo before 3.4.11.
      Use yum/rpm to upgrade to 3.4.11/12/13.
      Use systemctl to stop/start mongo and it will not do so until you do the daemon-reload.
      Which is fine for humans, but when your mongo installation is controlled by scripts, they get very confused that the start/stop script no longer does what it should.

      Show
      Install a version of mongo before 3.4.11. Use yum/rpm to upgrade to 3.4.11/12/13. Use systemctl to stop/start mongo and it will not do so until you do the daemon-reload. Which is fine for humans, but when your mongo installation is controlled by scripts, they get very confused that the start/stop script no longer does what it should.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-31225 the systemd script was changed. But the RPM package did not get updated to add a daemon-reload

      # systemctl start mongod
Warning: mongod.service changed on disk. Run 'systemctl daemon-reload' to reload units.

            Assignee:
            mathew.robinson@mongodb.com Mathew Robinson (Inactive)
            Reporter:
            maxallan Max Allan
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: