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

Systemd startup should not always be "forking".

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • 3.4.11, 3.4.12, 3.4.13
    • None
    • Packaging
    • None
    • ALL
    • Hide

      Install an affected version of mongo. Set "fork: false" in your mongod.conf and start mongo with systemd. Wait a few minutes and systemd will kill it.

      Show
      Install an affected version of mongo. Set "fork: false" in your mongod.conf and start mongo with systemd. Wait a few minutes and systemd will kill it.
    • Build 2018-03-12, Build 2018-03-26

    Description

      In ticket SERVER-31225 it is suggested that mongo should be set to "type=forking" and this has been applied globally to all mongo deployments. However, it is not impossible that in your /etc/mongod.conf you can have :

      processManagement:
        fork: false
      

      And then your server starts and after a while systemd notices it hasn't forked and kills it.
      I think startup=simple (or leave it to default) should be the default in the release and if people want to customise their own startup type, the RPM package should not overwrite customised systemd scripts.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: