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

After an upgrade mongod will not start on reboot

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Upgrade/Downgrade
    • Labels:
      None
    • ALL
    • Hide

      on Ubunt 18.04
      upgrade to new mongo packages.
      reboot, mongod will not have started.

      change file: /lib/systemd/system/mongod.server
      After=network.target

      to
      After=netword.target multi-user.target

      Reboot, mongod now starts.

      Show
      on Ubunt 18.04 upgrade to new mongo packages. reboot, mongod will not have started. change file: /lib/systemd/system/mongod.server After=network.target to After=netword.target multi-user.target Reboot, mongod now starts.
    • Dev Platform 2020-01-13, Dev Platform 2020-01-27

      After a mongodb package update mongod fails to start on system reboot. After a reboot mongod tries to start then bails out with and error "code 48". See attached log file excerpt.

      I should note this only happens on update on 18.04. I have no similar issue on 16.04.

      The problem seems to be with the systemd config. If I add the additional target"multi-user.target" to the "After=network.target" mongod starts on reboot.

      I have looked at other incidents similar and the all relate to WiredTiger IIRC.

      It's a minor but annoying problem, especially if I forget to modify the service file after and upgrade.

      Mongodb version: 4.2.2
      Distro: Ubuntu 18.04
      CPU: AMD Ryzen6
      RAM: 32Gb

        1. mongod-log.txt
          2 kB

            Assignee:
            mathew.robinson@mongodb.com Mathew Robinson (Inactive)
            Reporter:
            marsh.giguere@gmail.com Marshall Giguere
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: