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

Changes to systemd script but no reload of unit files

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 3.4.11, 3.4.12, 3.4.13
    • Fix Version/s: 3.7.4
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      Linux
    • Backport Requested:
      v3.6
    • Steps To Reproduce:
      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.
    • Case:

      Description

      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.
      

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: